item
by item
Search, create, update and delete item CRM records from an AI assistant, plus a read-only assistant tool for multi-step questions. 22 tools, OAuth sign-in, no read/write scope split.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect item via MCP
https://mcp.item.app/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
item Tools & Capabilities (22)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Frequently asked questions
Why does opening the item MCP URL in a browser show an authorization error?
Because the endpoint is protected and a browser sends no token. item's documentation calls this expected behaviour and tells you to connect through an MCP client instead. We confirmed it: an unauthenticated request to the endpoint returns HTTP 401 reporting a missing Authorization header, alongside a `WWW-Authenticate` header pointing clients at item's OAuth descriptor.
What should I do if my MCP client says item is unauthorized before I have signed in?
Retry the connection from the client UI or command. item's troubleshooting notes explain that the first unauthenticated request is how MCP clients discover item's OAuth configuration, so a single unauthorized response early in the handshake is part of the normal flow rather than a failure. The browser sign-in prompt should follow.
What do I do if the item connector never opens a browser to sign in?
Copy the authorization URL your client printed and open it manually. item documents this as the fallback when a client fails to launch a browser itself, which happens most often with terminal clients and remote sessions. Complete the item sign-in in that browser tab, then return to the client and let it finish the token exchange.
How do I switch the item connector to a different item account?
Remove or disconnect the item MCP server in your client, then add it again and sign in with the correct account. item documents this as the fix for connecting with the wrong account. There is no in-place account switch, because the client holds a token issued to the account that completed the original browser sign-in.
Can I give the item connector read-only access to my CRM?
No. item's protected-resource descriptor advertises only the OpenID Connect identity scopes `openid`, `profile` and `email`, which say who you are and nothing about what the connector may touch. No CRM read or write scope exists to grant or decline. The connector instead inherits your own item account permissions, which the documentation says govern tool availability.
Which item plan do I need to use the MCP server?
item does not name a plan tier for MCP. Its documentation says your item account must have active app access under the same billing rules as the web app, which ties MCP access to whatever entitles you to sign in normally rather than to a separate add-on. Tool availability also depends on your account permissions and connected integrations.
Sources
- item MCP documentation — https://docs.item.app/mcp-docs (fetched 2026-08-18, via the
.mdsuffix form athttps://docs.item.app/mcp-docs.md) · retrieved 2026-08-18 - item API documentation index — https://docs.item.app/index.md (fetched 2026-08-18) · retrieved 2026-08-18
- item API reference, Delete an object — https://docs.item.app/api-reference/objects/delete-an-object.md (fetched 2026-08-18) · retrieved 2026-08-18
- item API reference, Execute a view — https://docs.item.app/api-reference/views/execute-a-view.md (fetched 2026-08-18) · retrieved 2026-08-18
- item API reference, List available views — https://docs.item.app/api-reference/views/list-available-views.md (fetched 2026-08-18) · retrieved 2026-08-18
- item machine-readable docs index — https://docs.item.app/llms.txt (fetched 2026-08-18) · retrieved 2026-08-18
- item privacy policy — https://www.item.app/privacy (fetched 2026-08-18) · retrieved 2026-08-18
- item RFC 9728 protected-resource descriptor — https://mcp.item.app/.well-known/oauth-protected-resource/mcp (fetched 2026-08-18) · retrieved 2026-08-18
- item RFC 8414 authorisation-server metadata — https://mcp.item.app/.well-known/oauth-authorization-server (fetched 2026-08-18) · retrieved 2026-08-18
- Unauthenticated
initializeprobe againsthttps://mcp.item.app/mcp— 2026-08-18, HTTP 401 with an authentication challenge · retrieved 2026-08-18 - Anthropic connector directory — https://claude.ai/directory/f3c7ae42-8124-4037-9937-838e6ce97081 (snapshot 2026-08-16) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- item
- Tools
- 22
- Domain
- mcp.item.app
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.