Abency
Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.
Read accounts, contacts, opportunities and tasks, and create or update them.
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 Salesflare MCP server connects a Salesflare CRM account to Claude, ChatGPT and any MCP-compatible agent. An agent can list accounts, contacts, opportunities, tasks, pipelines, tags and users, read an account's activity feed — and create or update accounts, contacts, opportunities and tasks. Nothing in the tool set deletes. Sign-in is OAuth 2.0 with PKCE.
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.
openid and offline_access only. Per-tool control in the MCP client is the only enforcement point for the eight write tools.readOnlyHint or destructiveHint values could be confirmed. The verb census rests on the directory names cross-checked against the REST API, not on annotations.tools/list. Argument shapes, filter capabilities, pagination behaviour and result caps are all unknown to us.get_account_feed; we could not confirm the payload.prompt_names list and the gated endpoint prevented a prompts/list check.No. None of the 16 tools deletes anything — every one is a read, a create or an update. We checked this against Salesflare's own OpenAPI specification, which publishes 8 DELETE operations covering accounts, contacts, opportunities, tasks, tags, meetings, messages and custom fields. The connector exposes none of them, so the destructive quarter of the REST API is simply absent.
It writes. Eight of the 16 tools are writes: four create tools for accounts, contacts, opportunities and tasks, and four matching update tools. The other eight are reads. Anthropic's directory says the same in prose rather than a one-word label, and Salesflare's help centre advises starting with read-only questions before moving on to creating or updating data.
Salesflare states the connector follows the connected user's Salesflare permissions, but neither its help centre nor the directory documents how role and group scopes map onto individual tools. That gap matters because Salesflare shares everything with the team by default except My Contacts and account timelines, and the permissions feature that narrows this requires the Pro plan.
Two, and neither describes CRM access. Salesflare's protected-resource metadata advertises openid and offline_access — an identity scope and a refresh-token scope. There is no read scope and no write scope, so the grant cannot separate the eight read tools from the eight write tools. Approving the connector approves its whole surface at once.
Salesflare documents no plan requirement for the connector itself, and its help centre gates nothing behind a tier. The gate that matters is indirect: user permissions are a Pro plan feature at 49 dollars per user monthly billed annually. On the 29-dollar Growth plan there are no internal privacy settings, so a connected agent reaches shared team data.
Because Salesflare enriches records automatically from public sources. Salesflare documents that contacts linked to publicly available data may get profile pictures, social media links and previous positions filled in, and that email signatures can populate phone number, role and address. Accounts are enriched from the company website. An agent reading a contact reads that gathered data too.
Sixteen, and the number is trustworthy in a way many listings are not. Every entry in Anthropic's directory snapshot is a valid snake_case identifier, with no display names mixed in, and all 16 map onto operations in Salesflare's published REST API. The surface is narrower than the API behind it, which carries 71 operations across 46 paths.
.md suffix). Source of the endpoint confirmation, the connection steps, the enable-only-the-tools-you-need advice, the start-with-read-only guidance, and the workspace-administrator note. · retrieved 2026-08-19robots.txt first, then llms.txt, then the .md suffix, then sitemap. salesflare.com/robots.txt allows all crawlers and names ClaudeBot, Claude-User, GPTBot, PerplexityBot and others explicitly as allowed (fetched 2026-08-19). howto.salesflare.com/robots.txt disallows three paths and sets a 1-second crawl delay (fetched 2026-08-19). No Content-Signal axes are published on salesflare.com, howto.salesflare.com or app.salesflare.com — all three checked 2026-08-19. howto.salesflare.com/llms.txt exists and indexes the help centre with .md article links, which is how every article above was located; salesflare.com/llms.txt returns the site's HTML shell. No sub-URLs were guessed. · retrieved 2026-08-19initialize POST to https://mcp.salesflare.com/mcp returns HTTP 401 with a 12-byte text/plain body and a www-authenticate header naming realm="MCP" and the root-form resource_metadata URL. No authentication was attempted and no tool was called. · retrieved 2026-08-19text/plain 404 · retrieved 2026-08-19/.well-known/openid-configuration returns an identical document) · retrieved 2026-08-19permissions paragraph, the empty prompt_names, the partner tier, the four categories and the streamable-HTTP transport) · retrieved 2026-08-16Connect Salesflare once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.