Access, auth, and limits
Two auth paths, and you pick based on what your client supports. OAuth 2.0 is the default: the first connection opens a browser, you authorize, and the client reuses the credentials afterwards. The alternative is a personal access token generated under API Keys in app.peec.ai, sent as an Authorization: Bearer header on the MCP connection. That second path is what makes Peec usable from headless runners, CI jobs and any client without an interactive browser.
One gap to plan around: Peec does not state on either its MCP page or its pricing page which plans include MCP access. Everything else here is documented and verifiable, but tier gating is not, so confirm it against your own account before you commit a workflow to it.
Where it works and what to build
Peec publishes named setup guides for Claude, Cursor, VS Code and Windsurf, and says the server works with any MCP-capable client. Because it is remote streamable HTTP, adding it is a URL and an authorization step rather than a runtime and a config path.
The workflow that pays off is comparative rather than reportorial. Pull visibility by prompt across your brands, then read the actual chat responses and the sources cited in them, and you can see not just that a competitor outranks you in an AI answer but which page the model reached for. Asking a dashboard that question means clicking through prompt by prompt; asking an agent means one request across the whole set.
Which AI clients can use Peec AI MCP?
Not every AI assistant supports MCP natively. Per-client picture for Peec AI:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | — |
| Cursor | Native MCP | — |
| Windsurf | Native MCP | — |
How to connect Peec AI MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"peec-ai": {
"command": "npx",
"args": ["mcp-remote", "<YOUR_MCP_URL>"]
}
}
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://api.peec.ai/mcp
// Claude Code (one-liner): claude mcp add peec-ai <YOUR_MCP_URL> --transport httpSome MCP servers require an API key. Check the source page for setup: api.peec.ai/mcp.
Does Peec AI MCP cost extra?
Peec AI ships an official MCP server that uses your existing subscription credentials.
- No separate MCP licence to buy. You pay for your Peec AI plan, the MCP server queries that account.
- Whether it's gated to a specific tier wasn't extracted automatically — verify the access requirements on the MCP page or pricing docs.
Peec AI also publishes a REST API
Peec AI publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with Peec AI from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What keywords moved this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe Peec AI data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's Peec AI account
- Multi-account workflows without context-switching the Peec AI UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Peec AI data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Peec AI safe
Limits and gotchas
- Official MCP server — published by Peec AI themselves, so it should track product changes.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Rate limits: MCP calls count against your underlying Peec AI API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
A well-built remote server with the auth flexibility most GEO tools skip. Peec does not publish which plans include MCP, so confirm tier access before you build a workflow on it.
Strong agent fit for a young product. Peec ships an official MCP server at api.peec.ai/mcp on every paid plan from $95, not just Enterprise, so agents can connect from Claude, Cursor, or n8n without an enterprise contract. It is read-only at launch, so agents pull and reason over your AI-visibility data but cannot write back. The REST API for full programmatic access is reserved for Enterprise, which is the main gap.
Scored by Joonas (TMB).
Peec AI MCP & API FAQ
Is the Peec AI MCP server official?+
Can I use the Peec AI MCP with Cursor or Codex?+
Sources
- Peec AI official site: https://peec.ai
- MCP server page: https://api.peec.ai/mcp
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
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.