n8n-extending-mcp

Expose custom n8n workflows as MCP tools with typed inputs.

421|46|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/n8n-io/skills --skill n8n-extending-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-extending-mcp
Source: https://github.com/n8n-io/skills/tree/main/skills/n8n-extending-mcp
Command: npx skills add https://github.com/n8n-io/skills --skill n8n-extending-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

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).

Frequently Asked Questions about n8n-extending-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I expose n8n workflows as MCP tools for an AI agent?

You expose n8n workflows as MCP tools by wrapping business logic or API calls into a stateless workflow that the agent discovers via workflow search and invokes through execute_workflow with typed inputs, returning structured non-secret output.

Can I use n8n to list credentials and query executions when MCP lacks those features?

Yes, you can wrap n8n REST API calls into workflows to list credentials or query executions across the instance. The agent invokes these admin-style wrappers as tools to perform programmatic operations that MCP lacks natively.

What is the safest way to return data from an MCP tool workflow?

The safest approach is a credential-safe design returning only non-secret structured output like IDs and metadata. Validate that the tool workflow is stateless when possible and document side effects so the agent uses it correctly.

Does an agent need user approval to invoke a workflow as an MCP tool?

Yes, this design requires explicit user approval before the agent creates or invokes the workflow. This ensures you maintain control over side effects and credential access when the agent calls general-purpose action workflows or third-party API wrappers.

When should I wrap a third-party API call into an n8n MCP tool workflow?

Wrap a third-party API call when MCP lacks the needed functionality or when you want a reusable, tool-like workflow. This turns business logic or integrations into an MCP-callable tool the agent can reliably invoke by name during a session.