Skip to main content

MCP Connector

Ask any MCP-capable AI tool, such as Claude, about your Fond brand-visibility data in plain language, with no dashboard digging:

  • "Why did my ChatGPT visibility drop this week?"
  • "Which listicles cite my competitor but not me?"
  • "Where am I losing share of voice, and to whom?"

A connected tool can read your analytics but can't change anything in your account — unless you granted it a write permission when you connected it. There are two: one for brand context, and one for saved keywords and rank tracking. Each is off unless Fond has enabled it for your account, and neither is ever added to a connection you have already approved: you would have seen it on the approval screen, and turning one on later requires reconnecting. If you don't remember approving it, you don't have it.

Set it up in Claude

The steps below are for Claude Desktop and claude.ai. Using a different MCP client? See Other MCP clients. Either way you'll need a Fond account on an active plan, and the connector reads the same brands your dashboard shows.

  1. In Claude, go to Settings → Connectors → Add custom connector.
  2. Enter:
    • Name: Fond
    • MCP server URL: https://app.tryfond.co/api/mcp/mcp
    • Leave everything under Advanced settings blank. The OAuth Client ID and OAuth Client Secret fields are optional, and Fond doesn't need them — Claude and Fond work the connection details out between themselves.
  3. Click Add, then Connect, and log into Fond to grant read access.

The "Add custom connector" dialog in Claude, with Name set to "Fond", the MCP server URL filled in, and the optional OAuth Client ID and Secret fields under Advanced settings left empty.

Some versions of Claude also offer a choice of OAuth client. Either option connects to Fond. Prefer the one marked Recommended, Anthropic's hosted client metadata: Fond supports it, and it means Claude proves which application is asking for your data rather than simply claiming it. No client ID — register one automatically also works, and is the route other MCP tools take.

Before you approve, check the Check where this goes line on the Fond consent screen. It names the site your access is handed back to, which is claude.ai when you connect from Claude, or localhost with a port number for a tool running on your own machine. Anyone can build a connector and name it "Fond", so if that destination isn't one you recognize, choose Deny.

You'll see that screen every time you connect, including when you reconnect an existing connector — that's where you choose which of your organizations Claude can read, so it's the one place you can change that choice later.

Now reference Fond in any conversation. For example: "Using Fond, summarize my AI visibility for the last run."

Other MCP clients

The connector is a standard remote MCP server (Streamable HTTP + OAuth 2.1), so it isn't tied to Claude Desktop or claude.ai. Any MCP client that supports remote servers with OAuth can connect to the same URL, https://app.tryfond.co/api/mcp/mcp:

  • Claude Code: run claude mcp add --transport http fond https://app.tryfond.co/api/mcp/mcp, then invoke a Fond tool and complete the login when prompted.
  • Other clients: point them at the URL above and finish the Fond login. OAuth is discovered automatically, so there's no client ID or secret to enter.

Clients that only support local (stdio) servers, or that can't complete an OAuth login, aren't supported.

What you can ask

Claude starts by listing the brands your account can access, then answers about the one you name:

Ask about…What you get
VisibilityCounts from your latest run — answers, mentions, where in the answer your brand appeared, sentiment — plus feed quality and a 30-day mention trend.
Share of voiceShare of voice vs. competitors by intent depth, plus the "vacuum zones" nobody owns.
Citation gapsCited domains grouped as yours / a competitor's / neutral, showing who's referenced instead of you.
Competitor movementHow the competitive leaderboard shifted from the previous run to the latest.
Recommended actionsFixable AI-visibility gaps, ranked, with the evidence behind each.
Brand contextThe profile Fond holds for the brand, who last wrote each field, and the log of research already run.
Search ConsoleClicks, impressions, CTR and average position from your connected Google Search Console property, plus Google's live index status for individual URLs.
Keywords, rankings and backlinksKeyword research and metrics, SERP results, domain overviews, ranked keywords and domain competitors, backlink profiles, your saved keywords, and your rank trackers.

The last two rows appear only where Fond has enabled SEO for your account. Within them, the tools that buy fresh data from Fond's SEO data provider need a paid plan: keyword research, keyword metrics, SERP results, domain overviews, ranked keywords and domain competitors, the paid backlinks tabs, and creating a tracker, adding keywords to one, or running one off-schedule. Removing a tracker's keywords is free. On a free plan those say so rather than silently returning nothing. Your saved keywords, your trackers' existing results, and the backlinks overview cost nothing and stay available. Saving keywords, and creating, archiving and running rank trackers and adding or removing their keywords, are writes, so they appear only if you granted the saved-keywords and rank-tracking permission when you connected. Running a tracker is both: it needs the paid plan and that permission, and without the permission the tool is filtered out of the list rather than refusing when called.

Once connected, these tools appear under the Fond connector in Claude's settings, where you can set how Claude is allowed to use each one:

Per-tool permission controls for the Fond connector in Claude's settings. The tool list shown is from an earlier release and is not the current set.

Every analytics answer — visibility, share of voice, citation gaps, competitor movement, recommended actions — is stamped with the run it was computed from, so any figure can be traced back to the data behind it. The numbers Fond returns are measured from that run, never projected. The exceptions are brand context — the profile and research log Fond holds for the brand — and the search, keyword and ranking answers. None of those measures a run, so none carries a run stamp.

Troubleshooting

  • Access denied when connecting: the connector isn't enabled for your Fond account. Open AI Connector in the dashboard to check, or contact support.
  • Connecting fails right away: check the MCP server URL character for character — it has to be https://app.tryfond.co/api/mcp/mcp, including the /api/mcp/mcp on the end. Then open Advanced settings and make sure the OAuth Client ID and Client Secret boxes are empty; if an earlier version of these instructions had you fill them in, clear them and connect again. Both OAuth client options work with Fond, so that setting isn't the cause.
  • Claude asks you to sign in on every call: disconnect and reconnect the connector in Claude's settings.
  • "Website not found or not accessible": the brand isn't one your account can access, or its setup isn't finished.
  • "No data yet": the brand hasn't completed a query run; data appears once the first run finishes.