Mangools API Documentation

n8n talks to the Mangools tools through the hosted Mangools MCP (Model Context Protocol) server at https://mcp.mangools.com/mcp. The server exposes KWFinder, SERPChecker, SERPWatcher, LinkMiner, SiteProfiler and AI Search Watcher as MCP tools, so an n8n workflow can call them without writing HTTP requests.

There are two ways to use it:

As tools of an AI Agent, with the MCP Client Tool node giving the agent a set of Mangools tools it can call while it answers.
As a normal step in a workflow, with the MCP Client node calling one specific tool on a schedule or after a trigger.

Both nodes are built into n8n, on n8n Cloud and on self-hosted instances.

Before you start

A Mangools account. For the API key option below you also need your API key from mangools.com/api-token.
n8n. This page and the ready-made workflows were tested on n8n 2.40.6. Older versions may not have the node versions the workflows use.

Connect

Add an MCP Client or MCP Client Tool node and set:

Endpoint (called MCP Endpoint URL on the MCP Client node): https://mcp.mangools.com/mcp
Server Transport: HTTP Streamable
Authentication: MCP OAuth2 or Header Auth, matching one of the credentials below.

OAuth

OAuth signs n8n in to your Mangools account without copying an API key.

Set Authentication to MCP OAuth2 and create a new credential of type MCP OAuth2 API.
Set Server URL to https://mcp.mangools.com/mcp. n8n finds the Mangools authorization server from that URL.
Leave Use Dynamic Client Registration on.
Click Connect, sign in to Mangools in the window that opens and approve the access.

n8n registers itself with Mangools and gives the OAuth Redirect URL shown in the credential as the address to return to. Mangools accepts that address over https, or over plain http only on localhost, 127.0.0.1 or [::1]. On a self-hosted instance n8n builds it from N8N_EDITOR_BASE_URL, so set that variable to the public https address of your instance, or the sign-in cannot return to n8n.

API key (Header Auth)

Set Authentication to Header Auth.
In Credential for Header Auth, create a new credential with Name x-access-token and Value your Mangools API key.

Ready-made workflows

Workflow	What it does
mangools-keyword-research.json	Finds keywords related to a seed keyword in KWFinder and returns the 20 with the highest search volume, one item per keyword, with search volume, CPC and keyword difficulty when KWFinder has it. Each run spends one paid lookup.
mangools-weekly-rank-report.json	Every Monday at 08:00, builds a plain-text summary of your SERPWatcher trackings for the last 7 complete days: how many keywords rank in the top 100, their average position, and how many moved up or down. Connect a Slack, Gmail or Send Email node to its last step to receive it. Spends no lookups.
mangools-ai-agent.json	A chat AI Agent with eight read-only Mangools tools: location search, KWFinder related keywords and keyword details, SERPChecker, SERPWatcher trackings and AI Search Watcher monitors. Each KWFinder or SERPChecker call the agent makes spends a paid lookup. You add an OpenAI credential for the chat model.

To import one, open a new workflow in n8n, click the ... menu next to the workflow name, choose Import, then From URL, and paste the full address, for example:

https://apidocs.mangools.com/n8n/mangools-weekly-rank-report.json

You can also download the file from the table and choose Import, then From file.

The workflows come set to Header Auth. On each MCP node, pick your credential in Credential for Header Auth. A Header Auth credential named exactly Mangools API key is picked for you. To use OAuth instead, switch Authentication to MCP OAuth2 on every MCP node: the weekly report has two.

A scheduled workflow runs only after you publish it with the Publish button, and its schedule uses the time zone of your n8n instance.

Build it yourself

AI Agent

Add a Chat Trigger, an AI Agent, a chat model (for example OpenAI or Anthropic) and an MCP Client Tool node, and connect the MCP Client Tool to the agent's Tool input.

On the MCP Client Tool node, set Tools to Include to Selected and pick read-only tools only. The tool set also contains tools that create, update and delete trackings, monitors, lists, tags and reports, and an agent with access to them can use them on its own.

Scheduled workflow

Add a Schedule Trigger and an MCP Client node, and pick one tool in the node's Tool field, for example serpwatcher_list_trackings. The node calls that tool every time the schedule fires and passes the result to the next node. No AI model is involved.

Good to know

Paid lookups. Tools that look up new KWFinder, SERPChecker, LinkMiner or SiteProfiler data spend lookups from your Mangools plan, for example a keyword search, a SERP check, a backlink lookup or a SiteProfiler overview. Accounts without API access are charged double for lookups made through MCP.
SERPWatcher and AI Search Watcher reads spend no lookups. Adding trackings, keywords, monitors or prompts uses the allowances of your plan, as it does in the apps.
Large results are shortened by default. Set full: true in a tool's input to get the raw data, and limit to change how many items a list returns. Defaults differ per tool, for example 50 trackings or 25 keywords of tracking stats.
Timeouts. A keyword KWFinder has not seen before can take close to a minute. The node's Timeout option defaults to 60000 ms, so raise it for KWFinder tools. The keyword research and AI Agent workflows use 120000 ms.

Troubleshooting

Problem	Cause	Fix
"Could not connect to your MCP server. Authentication failed."	No credential on the node, or Authentication does not match the credential type	Pick a credential and set Authentication to Header Auth or MCP OAuth2 to match it
"Upstream request failed (Mangools API 401 on ...): Invalid API Key"	The key in the Header Auth credential is wrong or was regenerated. The tool list still loads with a wrong key, so the error appears only when a tool runs. In an AI Agent the error goes to the model instead of stopping the node.	Copy the current key from mangools.com/api-token into the credential
A tool call times out	The 60000 ms default is too short for a keyword KWFinder has not seen before	Raise the node's Timeout option, for example to 120000 ms
"Your browser blocked the sign-in window."	The browser blocked the OAuth pop-up	Allow pop-ups for your n8n address and click Connect again
The Mangools sign-in finishes but never returns to n8n	The OAuth Redirect URL points to an address your browser cannot reach	Set `N8N_EDITOR_BASE_URL` to the public `https` address of your instance and connect again

n8n

On this page