6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Query transactions, budgets, forecasts and net worth in plain language.
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 PocketSmith Complete Access MCP server connects your personal finance account to Claude, ChatGPT and any MCP-compatible agent. It exposes 66 tools for searching transactions, reviewing budgets, forecasting cashflow and net worth, and syncing bank feeds. "Complete access" is literal: 19 tools change your records and 7 delete them.
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.
readOnlyHint or destructiveHint values. Every safety label here is documentation-derived./mcp-readonly while every other reference to that endpoint — including its own server URL table and its Codex line — ends in /mcp. Use the URL from the server table.Yes. PocketSmith documents a second endpoint at mcp-readonly.pocketsmith.com carrying 40 read-only tools instead of 66. Its documentation says to choose read-only if you only want to ask questions about your finances, and full access if you also want the assistant to make changes. The two endpoints are separate hosts with separate OAuth issuers.
Yes, at the Complete Access endpoint. Seven of the 66 tools delete records: accounts, institutions, transactions, categories, budget events, attachments and the forecast cache. PocketSmith's API reference states that deleting an institution or an account removes all data within it, and deleting a category removes every budget inside it. Use the read-only endpoint to remove this capability entirely.
No. PocketSmith's MCP documentation states that authentication runs through OAuth, that the AI assistant receives a token scoped to your chosen access mode, and that it never sees your PocketSmith password. The docs add that tokens are encrypted with AES-256-GCM and stateless, so nothing is stored on the MCP server itself.
Revoke the connection from PocketSmith's authorised applications page at my.pocketsmith.com/security/manage_apps. PocketSmith's MCP documentation names this page as the place to revoke access at any time. Revoking there ends the grant at PocketSmith rather than only removing the connector from your AI client, which would leave the token live.
Yes, on paid plans. PocketSmith's documentation says personal Plus and Pro accounts add it under Settings, Apps and Connectors, after enabling Developer mode in advanced settings. On Business, Enterprise and Edu workspaces a workspace admin adds the connector first, then each user connects and authorises their own PocketSmith account individually.
Yes. PocketSmith's documentation publishes command-line install lines for both, using HTTP transport against the endpoint for your chosen mode, and says each will prompt for OAuth authorisation on first use. The same documentation also covers claude.ai and Claude Desktop, where the connector is added as a custom connector by URL.
.md variant advertised in the host's own llms.txt; page last updated 2026-08-20). Tool tables, access modes, both endpoint URLs, OAuth and security statements, client setup steps and usage examples come from here. · retrieved 2026-09-08developers.pocketsmith.com/robots.txt (fetched 2026-09-08) — allows the docs paths used above, carries no Content-Signal line, and points at its own llms.txt. · retrieved 2026-09-08https://mcp.pocketsmith.com/mcp and https://mcp-readonly.pocketsmith.com/mcp — both returned an authentication challenge; both RFC 9728 protected-resource and OAuth authorization-server documents retrieved (2026-09-08). No tool was called and no credential was supplied. · retrieved 2026-09-08Connect PocketSmith Complete Access once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.