What problem does it solve?
It solves the problem of missing or insufficient MCP capabilities by letting you wrap n8n actions—or any general workflow—so a coding agent can call them by name during a session.
Core Features & Use Cases
- Wrap n8n admin-style capabilities the MCP lacks: list credentials, query executions across the instance, fetch instance metadata, and perform other programmatic operations through n8n REST API calls.
- Expose general-purpose workflows as tool actions: turn business logic or third-party integrations into an MCP-callable tool the agent can invoke reliably.
- Provide a safe, production-ready tool pattern: validate that the tool workflow is stateless when possible, avoid returning secrets, and document naming/side effects so the agent uses the tool correctly.
Quick Start
Ask the agent to build a wrapper workflow that “exposes listing credentials as an MCP tool,” then approve creating it on your n8n instance and ensure it returns only IDs and metadata (not secret values).