Which AI clients can use LLM Pulse MCP?
Not every AI assistant supports MCP natively. Per-client picture for LLM Pulse:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | Add the MCP server URL and authenticate via OAuth; no API key needed. |
| Claude Code | Native MCP | Connects to the hosted MCP server over OAuth; full read/write tool access. |
| ChatGPT | Native MCP | Supported as an MCP client per LLM Pulse docs; OAuth sign-in. |
| Cursor | Native MCP | Native MCP support; add the server and sign in once. |
| Windsurf | Native MCP | Listed as a supported MCP client. |
| Gemini | Native MCP | Listed as a supported client; OAuth-based MCP connection. |
| n8n | API-only (custom code) | No native node; integrate via the REST API (Scale tier) with Bearer auth. |
Does LLM Pulse MCP cost extra?
The LLM Pulse MCP server is community-built — free to run, but you still pay for your LLM Pulse subscription.
- Community MCPs are normally self-hosted from a GitHub repo. There's no extra license fee.
- Your LLM Pulse 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 LLM Pulse changes their UI or API.
LLM Pulse also publishes a REST API
LLM Pulse publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with LLM Pulse 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 LLM Pulse 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 LLM Pulse account
- Multi-account workflows without context-switching the LLM Pulse UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage LLM Pulse data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production LLM Pulse safe
Limits and gotchas
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Rate limits: MCP calls count against your underlying LLM Pulse API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
A genuinely strong, native MCP server: OAuth 2.1 with no API key, 45+ read and write tools, included on every plan, and broad client support. This is the reason LLM Pulse is one of the most agent-ready tools in the GEO category. A clear 8 out of 10.
Scored by Joonas (TMB).
LLM Pulse MCP & API FAQ
Is the LLM Pulse MCP server official?+
Can I use the LLM Pulse MCP with Cursor or Codex?+
Sources
- LLM Pulse official site: https://llmpulse.ai
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.

