Sight AI: No MCP yet

No verified MCP server as of 2026-08-05. Sight AI relies on its dashboard UI for now.

NONE MCPPublic API

MCP status verified 2026-08-05Agent-readiness 3/10

Data from Buddy's database, auto-rechecked weekly

Does Sight AI have an MCP server?

Sight AI does not publish an MCP server. The direction is reversed: Sight AI is an MCP client. Its own docs describe connecting any remote MCP server over HTTPS so that server's tools become available to the Sight agent. Ahrefs is the worked example on its integrations page.

That means you cannot connect Sight AI to Claude, Cursor or ChatGPT and query your Sight data from there. What you can do is bring outside data into Sight's agent, which then writes and publishes articles and tracks AI-search visibility with that context loaded.

Sight describes these connectors as read-only context sources: they pull data and tools into the conversation, and do not publish content or modify data on their own. Publishing happens through Sight's own one-click integrations with WordPress, Webflow, Shopify and Framer, not through MCP.

For the rest of the picture see the Sight AI review or full pricing breakdown.

Where it works and what to build

The practical test is which side of the connection you are standing on. If you want your agent to read Sight AI data, there is nothing to connect, and no announced plan to change that. If you want Sight's agent to write with live data in hand, you point it at a remote MCP server over HTTPS and its tools land in the agent.

The Ahrefs connector is the case Sight documents, and it makes the value obvious: the agent drafts against live backlink and keyword data instead of whatever it inferred from the page it was given. The read-only framing is a deliberate safety boundary rather than a missing feature, because the agent already has its own publishing path and a Slack approval step in front of it.

Sight AI also publishes a REST API

Sight AI publishes an API, but per-tier gating wasn't extracted automatically.

API docs

—

Auth method

—

SDK languages

—

OpenAPI spec

—

Webhooks

—

Structured outputs

—

See Sight AI API page

Limits and gotchas

Fallback: the REST API works for any flow the MCP server doesn't cover.
No MCP available — until Sight AI ships one, use the REST API directly.

3/10

Agent-readiness verdict

Not an MCP server, and the distinction matters. If your requirement is querying Sight from your own agent, Sight cannot do it. If it is giving Sight's agent live SEO data, that is exactly what it is built for.

Scored by Joonas (TMB).

Sight AI MCP & API FAQ

Does Sight AI plan to add an MCP server?+

Not announced as of the last check. For now, no agent-friendly access is published.

Sources

Sight AI official site: https://www.trysight.ai/

Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.

Joonas RotkoAuthor & Founder of That Marketing Buddy

10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.

About me How I review

Sight AI

Try Sight AI

WEEKLY NEWSLETTER

The marketing tools worth your money, scored for AI agent readiness

Every week I score the tools for MCP, API, and agent-readiness, then email you the ones that actually deliver, what plugs into Claude and Cursor, the pricing changes, and what to skip. No fluff, no daily spam.

Join for free. One email a week, unsubscribe anytime.