n8n MCP server
n8n in any MCP client, through Memtro: n8n does not publish this server. Memtro's n8n connector reads n8n through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
n8n workflow automation, on n8n Cloud or self-hosted: list workflows and what they are built from, read execution history (status, timing, failures, never the data that passed through) and tags; can publish, unpublish, archive, restore and delete workflows, set their tags, retry, stop and delete executions, and create or delete tags.
Reads
n8n_list_workflowsN8n workflows: name, whether active, archived, how many triggers and nodes, which node types it uses, tags, created and updated.n8n_get_workflowOne n8n workflow: name, active, tags, and its nodes by name and type (which disabled), without parameters, credentials or pinned data.n8n_list_executionsN8n execution history, newest first as n8n returns it: id, workflow id, status (success, error, crashed, running, waiting, canceled…), mode, started…n8n_list_tagsTags defined in n8n (used to group workflows).
Acts, when you ask
These change something in n8n. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
n8n_create_tagCreates a tag in n8n. It is not attached to any workflow, runs nothing and notifies nobody; everyone on the instance can see it.n8n_delete_tagDeletes an n8n tag by id (destructive).n8n_publish_workflowPublishes (activates) an n8n workflow, the latest version unless a version id is given.n8n_unpublish_workflowUnpublishes (deactivates) an n8n workflow: its triggers, schedules and webhooks stop, and anything that relied on them stops being handled.n8n_archive_workflowArchives an n8n workflow (n8n's soft delete; it leaves the workflow list and stops running).n8n_unarchive_workflowRestores an archived n8n workflow.n8n_delete_workflowDeletes an n8n workflow.n8n_set_workflow_tagsSets the tags on an n8n workflow, replacing its whole tag list with the tag ids given (an empty list removes them all).n8n_retry_executionRetries an n8n execution (normally a failed one), starting a new execution.n8n_stop_executionStops one running or waiting n8n execution.n8n_stop_workflow_executionsStops one n8n workflow's executions in the given states (queued, running, waiting), optionally only those started in a window.n8n_delete_executionDeletes an n8n execution record and the data it holds.
Connect it
First connect n8n on Dashboard → Connections, then add Memtro to your client once. The n8n tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared n8n connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which workflows failed today?
- › Is the invoice sync workflow active, and when did it last run?
- › Which workflows use the Slack node?
- › Retry last night's failed CRM import
- › Unpublish the old Acme lead routing workflow
Questions
- Is this an official n8n MCP server?
- No. It is Memtro's MCP server with Memtro's n8n connector behind it: the connector reads n8n through its API with the credentials you connect on Dashboard → Connections, and n8n publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in n8n?
- Only when you ask, and only what it has been granted: create a tag (refused if the name already exists); delete a tag (workflows that carried it lose the label); publish a workflow so its triggers go live; unpublish a workflow so its triggers stop; archive a workflow, or restore an archived one; delete a workflow (permanent); set a workflow's tags (replaces its list); retry a failed execution (repeats what the workflow does); stop a running or waiting execution; stop one workflow's queued, running or waiting executions; delete an execution record (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.