mcpField
N
N8n Workflows

N8n Workflows

Local
github.com/carlosjperezProductivity0
Repository

About N8n Workflows

MCP server for advanced automation of n8n workflows via Model Context Protocol. Allows running, listing, and monitoring n8n workflows from any compatible MCP client

#automation#n8n#workflows#integration

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "n8n-workflows": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "N8N_BASE_URL",
        "-e",
        "N8N_API_KEY",
        "ghcr.io/carlosjperez/n8n-mcp-connector:latest"
      ],
      "env": {
        "N8N_BASE_URL": "<N8N_BASE_URL>",
        "N8N_API_KEY": "<N8N_API_KEY>"
      }
    }
  }
}
Run commanddocker run -i --rm -e N8N_BASE_URL -e N8N_API_KEY ghcr.io/carlosjperez/n8n-mcp-connector:latest
Environment variables to set
N8N_BASE_URL
N8N_API_KEYSecret

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocighcr.io/carlosjperez/n8n-mcp-connector:latest

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.