GetIntel MCP server
What GetIntel's MCP server is, what your coding agent can do with it, how access and brands work, and where to start.
GetIntel runs a remote MCP (Model Context Protocol) server. Connect it to Claude Code, Cursor, Codex CLI, Claude Desktop or any MCP client, and your agent can read everything GetIntel knows about your AI visibility, then act on it: in your task list, and in your real codebase.
Endpoint: https://app.getintel.ai/mcp
What your agent can do
Section titled “What your agent can do”- Read your data with 27 read tools: your overview, topics, AI answers, competitors, sources, pages, brand perception, Reddit, technical scan, AI traffic, Search Console and tasks.
- Act with 3 action tools: update tasks, plan the week, and re-run the technical scan. Action tools need a token with action access.
- Change your site. Coding agents like Claude Code, Cursor and Codex CLI combine GetIntel’s findings with your repository: read a task, edit the page, open a pull request.
How it works
Section titled “How it works”| Transport | Streamable HTTP, JSON-RPC 2.0 |
| Authentication | Sign-in over OAuth for clients that support it, or an Authorization: Bearer <token> header with a token created in GetIntel |
| Scope | Each token sees one brand: the brand selected when it was created |
| Permissions | Read-only by default; action access is opt-in per token |
| Time ranges | Last 7 days by default; up to 90 days where a tool supports periods |
| Limits | A monthly read quota per plan; see Usage and limits |
Start here
Section titled “Start here” Connect your agent Create a token and add GetIntel to your client.
Tool reference All 31 tools, their inputs and what they return.
Recipes Ready-made workflows: weekly brief, topic root cause, fix a task.
Example prompts What to ask, from checking your standing to shipping a fix.