Mencoro

Mencoro MCP server

Ask an AI assistant how your brand is doing in AI answers — rank, mentions, sentiment and Share of Voice — and have it set up and tune your monitoring, in plain language.

Mencoro tracks how brands surface in AI answer engines — ChatGPT, Perplexity, Google AI Overview and AI Mode — and in Google Search and Shopping. The MCP server exposes that data to any MCP client, and lets it manage projects, tracked queries, clusters and organizations, as 67 tools (31 that read, 36 that change something) and 20 prompts. One of them, get_mencoro_guide, answers questions about Mencoro itself and works without signing in.

The server is hosted. Most clients should connect to it directly:

https://api.mencoro.com/mcp

This repository holds the public metadata for that server plus a small stdio bridge (@mencoro/mcp) for hosts that can only launch a local process. It does not contain the Mencoro application source.

Connect

Clients that speak remote MCP (recommended)

No install, no local process. Sign in with OAuth, or paste a personal access token as a header.

Clients that can only spawn a local process

Claude Desktop's manual configuration, and older stdio-only hosts, need a bridge. That is what this package is:

npx -y @mencoro/mcp

// claude_desktop_config.json

{ "mcpServers": { "mencoro": { "command": "npx", "args": ["-y", "@mencoro/mcp"], "env": { "MENCORO_API_KEY": "mcp_pat_your_token" } } } }

The token goes through the environment rather than an argument, so it does not appear in ps output and does not have to survive the host's argument splitting.

Authentication

Two ways in. Both carry the same three permissions, and neither can ever do more than your own role in an organization allows:

OAuth 2.1 — the one-click path. Supported by Claude, ChatGPT, Claude Code and any client that implements the MCP authorization spec. Nothing to copy or paste; revoke it from the app. The consent screen pre-selects the scopes the client asked for (all three when it asked for none), and you can untick any but read. The server advertises PKCE (S256), Client ID Metadata Documents, Dynamic Client Registration and RFC 9728 resource metadata, so clients discover everything they need from https://api.mencoro.com/.well-known/oauth-protected-resource/mcp. Calling a tool the connection lacks the scope for answers 403 insufficient_scope naming the scopes to request, so a client that supports step-up authorization asks you to reconnect with the extra permission.

Personal access token — for CLI clients, config files, and this bridge. Create one at tool.mencoro.com/me/mcp-server; it is shown once, starts with mcp_pat_, carries the permissions you tick (all three by default), and can be pinned to a single organization and given an expiry. Send it as Authorization: Bearer mcp_pat_…. A call the token lacks the permission for fails with a tool error naming it; a token cannot be upgraded, so create a new one to add a permission.

Connections and tokens created before write access existed have read and write but not organization:manage.

ChatGPT cannot send a custom Authorization header to a remote connector — use OAuth there.

Client configuration

Cursor — ~/.cursor/mcp.json

{

"mcpServers": { "mencoro": { "url": "https://api.mencoro.com/mcp", "headers": { "Authorization": "Bearer mcp_pat_your_token" } } } }

</details>

VS Code — .vscode/mcp.json

{

"servers": { "mencoro": { "type": "http", "url": "https://api.mencoro.com/mcp", "headers": { "Authorization": "Bearer mcp_pat_your_token" } } } }

</details>

OpenAI Codex — ~/.codex/config.toml

[mcp_servers.mencoro]

url = "https://api.mencoro.com/mcp" http_headers = { "Authorization" = "Bearer mcp_pat_your_token" }

</details>

Gemini CLI — ~/.gemini/settings.json

{

"mcpServers": { "mencoro": { "httpUrl": "https://api.mencoro.com/mcp", "headers": { "Authorization": "Bearer mcp_pat_your_token" } } } }

</details>

OpenCode — opencode.json

{

"$schema": "https://opencode.ai/config.json", "mcp": { "mencoro": { "type": "remote", "url": "https://api.mencoro.com/mcp", "enabled": true, "headers": { "Authorization": "Bearer mcp_pat_your_token" }, "oauth": false } } }

oauth: false stops OpenCode negotiating OAuth against an endpoint that also advertises it, which would otherwise override the token you just configured.

Google Antigravity

{

"mcpServers": { "mencoro": { "serverUrl": "https://api.mencoro.com/mcp", "headers": { "Authorization": "Bearer mcp_pat_your_token" } } } }

</details>

Claude Code — project scope, committed to a repository

{

"mcpServers": { "mencoro": { "type": "http", "url": "https://api.mencoro.com/mcp", "headers": { "Authorization": "Bearer ${MENCORO_API_KEY}" } } } }

</details>

Tools

31 tools read and 35 change something. Every tool declares all four MCP annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) explicitly, so a client can decide what to ask you before calling it.

Reading

Every read tool needs only the read scope.

| get_mencoro_guide | The public Mencoro guide: how checks, mentions and every metric work, plans, reliability, this server, analysis advice, pairing with Ahrefs, Semrush, Search Console or Googl