n8n -rust

This MCP server is a Rust-based adapter that enables programmatic access to n8n workflows, executions, and tags through the MCP protocol. It exposes endpoints to retrieve, create, update, activate/deactivate, and delete workflows; manage executions; and handle tag operations. You can use it to automate workflows from external systems, trigger workflow runs via webhooks, and query history and tag metadata. Connect your MCP client to the server-name endpoint using the provided MCP protocol commands, then issue operations such as listing all executions, creating or updating workflows, and executing a workflow that starts with a webhook trigger. The server is designed to work with an n8n instance, so ensure the n8n instance is accessible from the MCP server and that any required authentication is configured in environment variables or through n8n API credentials.

Prerequisites:

• Docker installed and running on the host
• Access to an n8n instance (URL and credentials if required)

Install and run:

1. Pull the Rust-based MCP server image (assumes image name n8n-rust-server): docker pull n8n-rust-server:latest

2. Run the MCP server container with necessary environment variables: docker run -d --name n8n-mcp-server
   -e N8N_BASE_URL="https://your-n8n-instance"
   -e N8N_WEBHOOK_SECRET="optional-secret"
   -e MCP_LOG_LEVEL="info"
   -p 8080:8080
   n8n-rust-server:latest

3. Verify the server is running and reachable on port 8080. Use your MCP client to connect to the server at http://localhost:8080 (adjust port as configured).

Optional: If you prefer building from source, ensure Rust is installed, then follow the repository’s build instructions to compile and run the binary locally, and expose it via a reverse proxy if needed.

Notes and tips:

• Ensure the n8n instance is reachable from the MCP server (network rules, firewalls, and TLS considerations).
• If you enable webhooks for running workflows, make sure the MCP server can receive webhook callbacks from n8n and that any public URL is accessible by n8n.
• Environment variables can be extended to include authentication headers or tokens required by your n8n instance.
• Check the MCP client compatibility with this Rust-based server for supported operations (executions, workflows, and tags).
• Enable verbose logging during initial setup to diagnose connectivity or permission issues; reduce after confirming stable operation.