The Mangools MCP server lets an AI assistant, such as Claude, ChatGPT or Cursor, use the Mangools tools for you: KWFinder, SERPChecker, SERPWatcher, LinkMiner, SiteProfiler and AI Search Watcher. You add one server address to your assistant, then sign in with your Mangools account. Most assistants need no token.

This is the server address for every assistant:

MCP stands for Model Context Protocol. It is an open standard that lets AI assistants connect to other services.

You need a Mangools account and an AI assistant that supports remote MCP servers. Every plan on the Mangools pricing pages lists "API & MCP included".

The steps below follow each assistant's own help pages. Your assistant's menus can change after this article was written. If a menu name does not match, look for "connectors", "MCP" or "tools" in its settings.

You can copy the server address from two places:

The API & MCP menu item in AI Search Watcher is unavailable while a monitor's data is processing. Wait until processing finishes, or use the KWFinder link.

In Claude, the Mangools server is a custom connector. It works on the web, on desktop and in the mobile apps, because connectors belong to your Claude account.

On a Claude Team or Enterprise plan, a workspace Owner adds the connector first, under Organization settings, then Connectors. The Owner selects Add, points to Custom and selects Web. Each member then opens Customize, then Connectors, selects Connect and signs in with their own Mangools account.

ChatGPT adds the Mangools server as a developer-mode app. Developer mode works in ChatGPT on the web.

The new Mangools app appears under Drafts in ChatGPT's apps settings.

Cursor reads MCP servers from a file called mcp.json. Use .cursor/mcp.json inside a project for that project only, or ~/.cursor/mcp.json for every project. Add this:

Then open Customize in Cursor's sidebar and find the Mangools server. If Cursor asks you to sign in, finish the sign-in in your browser.

Claude Code adds the Mangools server with one command in your terminal:

Then run /mcp inside Claude Code and choose Authenticate. Your browser opens the Mangools sign-in. You can also run claude mcp login mangools in your terminal instead.

In Copilot Studio, open your agent and go to Tools, Add a tool, New tool, then Model Context Protocol. Fill in the form:

Sign in with your Mangools account when you create the connection. Then publish the agent. The Mangools tools are available only after you publish.

In n8n, add an MCP Client Tool node to an AI agent workflow, or an MCP Client node to a normal workflow. Set:

OAuth2 sign-in needs n8n 1.119.0 or newer. The n8n page in the Mangools API documentation has ready-made workflows and an n8n troubleshooting table.

Open WebUI supports MCP from version 0.6.31. Only an Open WebUI administrator can add MCP servers. Go to Settings, then Admin, then Integrations. Under External Tool Servers, select + Add Connection and fill in:

Set WEBUI_SECRET_KEY on your Open WebUI instance. Without it, the sign-in is lost each time the container restarts.

Some assistants, and older versions of the ones above, cannot do the Mangools sign-in. They can connect with your API token instead. Send it as a header named x-access-token.

Your API token is on the API page of your Mangools dashboard (top menu API), where it is called Your API key. AI Search Watcher shows the same value on its API & MCP page, under Your API token, with a Copy token button.

On the API & MCP page, the Copilot Studio, n8n and Open WebUI tabs have a fallback section with the exact fields to fill in. For any other assistant, use the server address and the x-access-token header.

Treat the API token like a password. Anyone who has it can run searches on your account and spend your lookups.

An MCP tool that fetches new data uses lookups from your Mangools plan. That covers KWFinder, SERPChecker, LinkMiner and SiteProfiler, for example a keyword search, a SERP check, a backlink lookup or a site overview.

On a regular Mangools account, one MCP request uses 2 lookups, twice what the same search uses in the app. Requests through the Mangools API and through MCP count toward the same daily limit.

Reading your SERPWatcher trackings or your AI Search Watcher monitors uses no lookups. Adding trackings, tracked keywords, monitors or prompts through MCP uses your plan's allowances, as it does in the apps.

An assistant can also create, change and delete trackings, monitors, lists and reports through MCP. If you want to approve each action first, use an assistant that asks before it calls a tool.

To see what you have left, open the account menu from your avatar at the top right of KWFinder or any other Mangools SEO tool. How lookups and limits work, and when they reset explains each counter.

If it still fails, contact us through the live chat or at [email protected]. Tell us the assistant's name and version, how you connected (sign-in or API token), and the exact error message.

The MCP server is for AI assistants. For your own scripts and integrations, use the Mangools REST API with your API token. The Mangools API documentation covers it, including its rate limits. To compare what each plan includes, see Mangools plans compared: what each plan includes.