6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Ask Claude about pipeline risk, stakeholders and next steps from Backstory's captured emails, meetings and CRM records.
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 Backstory MCP server connects Backstory, the sales platform formerly called People.ai, to Claude. Its 17 tools find accounts and opportunities, summarise deal risk and momentum, list recent emails and meetings, and run Backstory's own sales AI over a deal. Every tool reads; none is documented as writing to your CRM.
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.
fetch_records, and a preview you confirm first.situation_search.Nothing in Backstory's documentation says it can. Backstory describes all 17 tools as finding, summarising or analysing accounts, opportunities and activity, and none is named for creating, updating or sending anything. Backstory does not state in so many words that the connector is read-only, so treat that as our reading of its tool list rather than a vendor guarantee, and ask Backstory if it matters.
No. Backstory says you sign in with your Backstory credentials and do not need a CRM license to authenticate. You do need an active Backstory account, and Backstory's Claude guide lists a Claude Pro, Team or Enterprise subscription. Organisations on Okta or Entra ID may be able to pass sign-in through the chat client by arranging it with Backstory.
Either your Claude plan does not include connectors or nobody has added Backstory for your organisation yet. Backstory's guide says MCP is not available on free Claude plans. On a paid plan, if Backstory is still missing, a Claude organisation administrator has to add it once, after which every user connects their own account by signing in.
Every few weeks, according to Backstory. Its Claude guide says OAuth tokens expire periodically for security, and Claude then prompts you to sign in again using the same flow you used at setup. Disconnecting from the Connectors tab removes the connection without changing your Backstory data, and you can reconnect at any time afterwards.
No. Backstory says its tools only work with records sourced from your connected CRM, matched with the email, meeting and call activity Backstory captures. If a record is missing, Backstory points you to your access in Engagement Dashboards or to your administrator, because the connector can only see what your own Backstory account can see.
https://help.backstory.ai/llms.txt (fetched 2026-11-18) · retrieved 2026-11-18https://www.backstory.ai/llms.txt (fetched 2026-11-18) · retrieved 2026-11-18initialize probe of https://mcp.backstory.ai/mcp — HTTP 401, "No bearer token or client credentials were provided", with resource_metadata at https://mcp.backstory.ai/.well-known/oauth-protected-resource/mcp, which lists one scope, claudeai (2026-11-18) · retrieved 2026-11-18anthropic-directory-2026-11-17.json) · retrieved 2026-11-17Connect Backstory once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.