Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.item.app/llms.txt

Use this file to discover all available pages before exploring further.

Use the item MCP server to give AI clients access to your item workspace through the Model Context Protocol.

​
Server URL

Use this URL in MCP clients that support remote HTTP or Streamable HTTP servers: 
https://mcp.item.app/mcp
If a client asks for a transport, choose HTTP, Streamable HTTP, or Remote HTTP. Do not choose a local command or stdio server.

​
Authentication

The item MCP server uses OAuth. When you connect, your MCP client opens an item authorization page in your browser. Sign in with the item account you want the client to use, review the requested access, and allow access. The MCP endpoint is protected, so opening https://mcp.item.app/mcp directly in a browser may show a missing authorization error. That is expected. Connect through one of the MCP clients below instead.

​
ChatGPT

ChatGPT supports remote MCP servers through Developer mode.
  1. Open ChatGPT settings.
  2. Go to Apps.
  3. Open Advanced settings and enable Developer mode.
  4. In Apps settings, choose Create app.
  5. Use item as the app name.
  6. Use https://mcp.item.app/mcp as the remote MCP server URL.
  7. Complete the item OAuth flow when ChatGPT opens the authorization page.
  8. In a chat, open the tools or plus menu, choose Developer mode, and enable item for the conversation.
Some ChatGPT workspaces still show this under Connectors instead of Apps. In that UI, enable Developer mode under Settings > Connectors > Advanced, then add a custom remote MCP connector with the same server URL.

​
Claude

Claude supports custom connectors backed by remote MCP servers. For Pro or Max plans:
  1. Open Claude.
  2. Go to Customize > Connectors.
  3. Click + and choose Add custom connector.
  4. Enter item as the connector name.
  5. Enter https://mcp.item.app/mcp as the remote MCP server URL.
  6. Leave advanced OAuth client fields blank unless your workspace admin gave you specific values.
  7. Finish adding the connector, then click Connect and complete the item OAuth flow.
  8. In a conversation, open the connector menu and enable item.
For Team and Enterprise plans, an organization Owner may need to add the connector first from Organization settings > Connectors. After that, each user connects their own item account from Customize > Connectors.

​
Claude Code

Add item as a remote HTTP MCP server: 
claude mcp add --transport http item https://mcp.item.app/mcp
Then start Claude Code in the project where you want to use item and run: 
/mcp
Select item, follow the browser OAuth flow, and return to Claude Code. You can verify the server with: 
claude mcp list
To make item available in every Claude Code project on your machine, add it with user scope: 
claude mcp add --transport http --scope user item https://mcp.item.app/mcp

​
Codex

Add item with the Codex CLI: 
codex mcp add item --url https://mcp.item.app/mcp
Codex will detect OAuth support and open the item authorization flow. After you allow access, verify the server is configured: 
codex mcp list
The Codex CLI and Codex IDE extension share MCP configuration, so adding the server once makes it available in both.

​
Cursor

Cursor reads MCP server configuration from mcp.json. For a global setup, create or edit ~/.cursor/mcp.json: 
{
  "mcpServers": {
    "item": {
      "url": "https://mcp.item.app/mcp"
    }
  }
}
For a project-only setup, create or edit .cursor/mcp.json in your project with the same JSON. Restart Cursor after saving the file. Then open Settings > Tools & Integrations or Settings > MCP, find item, and connect. Cursor should open the item OAuth flow the first time it needs to authenticate.

​
Misc clients

Use item with any MCP client that supports remote HTTP MCP servers and OAuth. When configuring the client:
  1. Set the server name to item.
  2. Set the server URL to https://mcp.item.app/mcp.
  3. Choose HTTP, Streamable HTTP, or Remote HTTP if the client asks for a transport.
  4. Complete the browser OAuth flow when prompted.
Clients that only support local stdio MCP servers cannot connect directly to the hosted item MCP server. Those clients need a remote MCP bridge or proxy that can speak HTTP to item.

​
Troubleshooting

If the client does not open a browser, copy the authorization URL it prints and open it manually. If you connected with the wrong item account, remove or disconnect the MCP server in the client, then add it again and sign in with the correct account. If a client says the server is unauthorized before you have completed OAuth, retry the connection from the client UI or command. The first unauthenticated request is how MCP clients discover item’s OAuth configuration.