6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Search, create, update and delete item CRM records, plus a read-only assistant tool for multi-step questions.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The item MCP server connects the item CRM to Claude, ChatGPT and any remote-HTTP MCP client. It exposes 22 tools covering object search, schema inspection, saved views, lists, notes and tasks, plus a read-only assistant tool for multi-step questions. Sign-in is OAuth in a browser, and the connector inherits your own item account permissions.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
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.
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.
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.
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.
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.
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.
.md suffix form at https://docs.item.app/mcp-docs.md) · retrieved 2026-08-18initialize probe against https://mcp.item.app/mcp — 2026-08-18, HTTP 401 with an authentication challenge · retrieved 2026-08-18Connect item once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.