Access, auth, and limits
Two paths in: Peekaboo OAuth for clients that can run the browser handshake, or a project-scoped API key for those that cannot. The scoping deserves credit. Keys bind to a project rather than the whole account, and read plus write access follows the connection permissions, so a read key stays a read key. You generate a key with write access deliberately or you do not have it.
The gate is the real constraint. The hosted server is a limited beta for eligible accounts with an active subscription, tracking the same beta-access gate as the REST API. Peekaboo does not publish the endpoint, the tool list or which plans qualify, so eligibility is a conversation with the vendor rather than something you can check from the pricing page.
Which AI clients can use Peekaboo AI MCP?
Not every AI assistant supports MCP natively. Per-client picture for Peekaboo AI:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | — |
| Claude Code | Native MCP | — |
| Cursor | Native MCP | — |
| ChatGPT | Native MCP | — |
Does Peekaboo AI MCP cost extra?
The Peekaboo AI MCP server is community-built — free to run, but you still pay for your Peekaboo AI subscription.
- Community MCPs are normally self-hosted from a GitHub repo. There's no extra license fee.
- Your Peekaboo AI account still needs whatever plan is required to access the data the MCP server queries.
- Trade-off: zero MCP cost, but no guarantee it'll keep working when Peekaboo AI changes their UI or API.
What you can do with Peekaboo 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 changed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe Peekaboo 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 Peekaboo AI account
- Multi-account workflows without context-switching the Peekaboo AI UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Peekaboo AI data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Peekaboo AI safe
Limits and gotchas
- Official MCP server — published by Peekaboo AI themselves, so it should track product changes.
- Rate limits: MCP calls count against your underlying Peekaboo AI API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Promising shape, gated availability. The per-project scoping and explicit write opt-in are better than most shipped servers manage, but a limited beta is not something to plan a workflow around yet.
Scored by Joonas (TMB).
Peekaboo AI MCP & API FAQ
Is the Peekaboo AI MCP server official?+
Can I use the Peekaboo AI MCP with Cursor or Codex?+
Sources
- Peekaboo AI official site: https://www.aipeekaboo.com
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.