Introducing agent and attribution
Finseo MCP

Finseo MCP

Connect AI assistants to your Finseo data through the Model Context Protocol. Ask Claude, ChatGPT, or Cursor how your visibility in ChatGPT, Perplexity, Gemini, and Google AI Overviews changed, which competitors are ahead, and what to fix next.

Overview

What you get with the Finseo MCP integration

The Finseo MCP server exposes your tracking data as tools an AI assistant can call. Once connected, Claude, ChatGPT, or Cursor can run list_projects, get_visibility_metrics, get_visibility_timeseries, list_prompts, get_prompt_details, get_answer_content, get_competitor_ranking, get_competitor_gap_analysis, get_competitor_h2h, get_sentiment_overview, get_top_sources, get_tags, get_query_fanouts, list_tasks, and get_task_details. Every tool is read-only and returns the same values as the Finseo dashboard, including visibility rate, mention rate, citation rate, ordinal position, mention depth, Share of Voice, and sentiment. Analytics tools accept optional model filters (chatgpt, perplexity, ai_overview, copilot, gemini, grok) and tag filters, default to a 30-day window, and support absolute startDate and endDate ranges.

Use cases

What you can do with Finseo MCP and Finseo

Real ways Finseo MCP customers use Finseo to track and grow AI search revenue.

  1. 01

    Monthly visibility review in plain language

    Ask Claude how your brand visibility changed in the last 30 days versus the previous period. It calls get_visibility_metrics and get_visibility_timeseries and explains the trend, including how much comes from being named versus being cited.

  2. 02

    Competitor gap analysis on demand

    Ask ChatGPT to rank your competitors and run a gap analysis against the strongest one. The assistant chains get_competitor_ranking, get_competitor_gap_analysis, and get_competitor_h2h to show where competitors appear when you do not, and who gets named first.

  3. 03

    Read the actual AI answers

    Drill from list_prompts to get_prompt_details to get_answer_content and read what ChatGPT or Perplexity actually answered on a given day, including every brand named and every source cited, without opening the dashboard.

  4. 04

    Prioritized to-do list in your assistant

    Ask for your most important open optimization tasks. list_tasks returns the Finseo Tasks backlog sorted by priority score, and get_task_details delivers the step-by-step plan and the evidence that triggered it.

  5. 05

    AI visibility while coding in Cursor

    Developers working on a site can ask Cursor which sources AI models cite for tracked prompts or which fan-out queries appear most, then implement the fix in the same session using an API key with read scope.

Why it matters

Why Finseo MCP customers need AI visibility tracking

The Model Context Protocol has become the standard way to give AI assistants access to external data, and Claude, ChatGPT, and Cursor all support remote MCP servers. Teams already ask these assistants to summarize, compare, and plan; without a connector they have to paste screenshots or CSV exports of their AI visibility data. The Finseo MCP server removes that step. Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO) questions get answered from live tracking data with explicit metric definitions, so the assistant never confuses mention depth with a ranking position or visibility with mention rate.

Comparison

Finseo MCP alone vs Finseo MCP with Finseo

How using Finseo MCP on its own compares to pairing it with Finseo for AI visibility and attribution.

Getting data into an assistant

Finseo MCP alone

Screenshots and pasted CSV exports

With Finseo

15 native tools the assistant calls itself

Authentication

Finseo MCP alone

Copying keys into JSON config

With Finseo

OAuth sign-in for Claude and ChatGPT

Drill-down

Finseo MCP alone

Overview numbers only

With Finseo

From KPI to the exact AI answer and its sources

Metric accuracy

Finseo MCP alone

Assistant guesses what a metric means

With Finseo

Labeled fields identical to the dashboard

Safety

Finseo MCP alone

Risk of accidental changes

With Finseo

Read-only tools, project restrictions enforced

How to connect

How to connect Finseo MCP to Finseo

A few steps to wire up your Finseo MCP account with Finseo. No code required.

  1. 01

    Connect Claude

    In Claude, open Settings, Connectors, Add custom connector. Enter Finseo as the name and https://api.finseo.ai/v1/mcp as the Remote MCP Server URL, leave Client ID and Secret empty, click Add, then Connect, sign in with your Finseo account, and click Allow access.

  2. 02

    Connect ChatGPT

    Turn on Developer mode under Settings, Security and login. Open Settings, Plugins, click the plus button, enter Finseo and the MCP server URL https://api.finseo.ai/v1/mcp, click Create, complete the Finseo sign-in, and wait for the tool scan to finish.

  3. 03

    Connect Cursor or Claude Code

    Create an API key with read scope under Settings, API. In Cursor, add an MCP server with the URL and an Authorization: Bearer header. In Claude Code, run claude mcp add --transport http finseo https://api.finseo.ai/v1/mcp with or without the header.

  4. 04

    Ask your first question

    Try "How visible is my brand in AI search this month, and how did it change versus the previous period?" or "Rank my competitors by AI visibility and run a gap analysis against the strongest one".

  5. 05

    Drill down to the evidence

    Follow up with prompt-level questions. The assistant chains list_prompts, get_prompt_details, and get_answer_content to show the exact answer text, brands named, and sources cited for any tracked prompt and date.

FAQ

Frequently asked questions about Finseo MCP

Answers to the most common questions about the Finseo MCP integration.

A remote Model Context Protocol server at https://api.finseo.ai/v1/mcp that lets AI assistants such as Claude, ChatGPT, and Cursor query your Finseo AI visibility data directly. You ask natural-language questions, the assistant calls read-only tools, and the answer is based on the same numbers as your dashboard.

Via OAuth 2.1. You add the server URL as a custom connector or developer-mode app, get redirected to the Finseo sign-in, and click Allow access. The server supports Dynamic Client Registration and PKCE, so no Client ID, Client Secret, or API key is needed for Claude or ChatGPT.

Cursor and other headless clients authenticate with a Finseo API key. Create a key with read scope under Settings, API, then add an MCP server in Cursor with the URL https://api.finseo.ai/v1/mcp and a header Authorization: Bearer sk_live_YOUR_API_KEY. Claude Code accepts the same header or discovers OAuth automatically.

Fifteen read-only tools: list_projects, get_visibility_metrics, get_visibility_timeseries, list_prompts, get_prompt_details, get_answer_content, get_competitor_ranking, get_competitor_gap_analysis, get_competitor_h2h, get_sentiment_overview, get_top_sources, get_tags, get_query_fanouts, list_tasks, and get_task_details. Analytics tools accept optional model and tag filters, the same filters as the dashboard, and the assistant chains them from overview to a single AI answer.

No. Every MCP tool is read-only and only retrieves data. The server also enforces workspace project restrictions automatically, so an assistant only sees the projects the connected account or API key is allowed to access. You can revoke access at any time by disconnecting the connector.

You need a Finseo account on a paid plan with at least one tracking project. Claude custom connectors work on Free, Pro, Max, Team, and Enterprise plans. ChatGPT requires Pro, Plus, Business, or Enterprise/Edu with developer mode enabled. Cursor only needs an API key.

Every analytics tool defaults to a relative 30-day window ending yesterday via timeframeDays. For an exact period, pass startDate and endDate together in YYYY-MM-DD format; get_visibility_metrics then compares that range against the same number of days before it. get_visibility_timeseries supports a maximum of 90 days.

Unauthenticated requests receive a 401 with OAuth discovery metadata, so compliant clients start the sign-in flow automatically. If the assistant reports it cannot reach the server, check that the URL includes the full path /v1/mcp, and make sure you can sign in at app.finseo.ai in the same browser.

Talk to our team

Connect Finseo MCP and dominate AI search

Join hundreds of brands using Finseo to track and improve their visibility in ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews.