How to connect Loops 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": {
"loops": {
"command": "npx",
"args": ["-y", "<server-package-name>"],
"env": {
"LOOPS_API_KEY": "your-api-key-here"
}
}
}
}
// Server source: https://github.com/H-mmer/pentest-agents
// Check the server's README for the exact "command" and required env vars.Some MCP servers require an API key. Check the source page for setup: github.com/H-mmer/pentest-agents.
Does Loops MCP cost extra?
The Loops MCP server is community-built — free to run, but you still pay for your Loops subscription.
- Community MCPs are normally self-hosted from a GitHub repo. There's no extra license fee.
- Your Loops 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 Loops changes their UI or API.
Loops subscription pricing
| Plan | Monthly | Annual / mo |
|---|---|---|
| Free | — | — |
| Early Stage Plan | Contact sales | — |
Source: loops.so/pricing. Verified 2026-06-07.
Loops also publishes a REST API
Loops publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with Loops 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 campaigns underperformed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe Loops 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 Loops account
- Multi-account workflows without context-switching the Loops UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Loops data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Loops safe
Limits and gotchas
- Community MCP — not maintained by Loops. Check the README and last-update date before depending on it.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Auth flow: MCP servers usually inherit the underlying API auth method (both). Expect to configure that on first install.
- OpenAPI spec is published — easy to validate which endpoints the MCP server actually exposes vs the full API surface.
- Rate limits: MCP calls count against your underlying Loops API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Strong agent-fit for SaaS workflows. Loops has a community MCP server, documented public API with OpenAPI spec, and SDKs across Node, Go, Ruby, and PHP, plus native Claude integration. The main limitation is lack of webhook support and structured JSON outputs, which narrows real-time automation possibilities.
Scored 2026-06-07 by Joonas (TMB).
Loops MCP & API FAQ
Is the Loops MCP server official?+
Can I use the Loops MCP with Cursor or Codex?+
Does Loops have a public API?+
Does Loops publish an OpenAPI / Swagger spec?+
Which LLMs does Loops integrate with directly?+
Sources
- Loops official site: https://loops.so
- MCP server page: https://github.com/H-mmer/pentest-agents
- API docs: https://loops.so/docs/api-reference/intro
- Pricing source: https://loops.so/pricing (verified 2026-06-07)
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.