n8n -custom

This MCP server provides a custom n8n integration designed to work with Antigravity. It exposes 27 MCP tools that map to n8n REST API capabilities, including workflows, executions, variables, credentials, node types, tags, and system information. After starting the server, you can manage your n8n instance through the MCP interface or via the Antigravity integration using the configured N8N_API_URL and API key. The tools allow you to list, create, update, and delete workflows; execute workflows with custom data; manage environment variables and credentials; query node types and tags; and monitor system health and connectivity checks. To connect, point your MCP client (e.g., Antigravity) at the mcp_config.json entry for n8n-mcp and supply the required API credentials in the environment variables.

Prerequisites:

• Node.js >= 18 installed on your machine or server
• npm (Node package manager) installed
• Access to an n8n instance with API capabilities and an API key
• A working Antigravity configuration if you plan to use mcp_config.json integration

Steps:

1. Clone the repository git clone https://github.com/burnham/n8n-mcp-server-custom.git cd n8n-mcp-server-custom

2. Install dependencies npm install

3. Configure environment cp .env.example .env Edit .env with:

   • N8N_API_URL set to your n8n instance URL
   • N8N_API_KEY set to a valid API key from n8n Settings → API

4. Build the project (TypeScript) npm run build

5. Run tests (optional) npm test

6. Start the MCP server node dist/index.js

7. (Optional) Configure Antigravity MCP config In your Antigravity mcp_config.json, add: { "mcpServers": { "n8n-mcp": { "command": "node", "args": ["/absolute/path/to/n8n-mcp-server-custom/dist/index.js"], "env": { "N8N_API_URL": "https://your-instance.n8n.cloud", "N8N_API_KEY": "your_api_key_here" } } } }

Tips and notes:

• Always use absolute paths when configuring the MCP server in external tools (e.g., Antigravity).
• Keep your .env file gitignored to avoid leaking API credentials.
• Regenerate and rotate your N8N_API_KEY as needed and update the MCP config accordingly.
• If you encounter initialization EOF errors with Antigravity, this custom server is designed to mitigate that issue; ensure your N8N_API_URL is reachable from your deployment environment.
• For production deployments, consider running the MCP server behind a secure gateway with proper TLS termination and access controls.