docs-n8n-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_docsA | List all n8n documentation pages from the cache. |
| get_docA | Read a single n8n documentation page as markdown. |
| search_docsA | Search across all cached n8n docs (case-insensitive regex). |
| refreshA | Re-fetch all n8n markdown files from GitHub and overwrite the cache. Fetches ~1,500 .md files in parallel (10 concurrent). Use this when documentation looks outdated or after a new n8n release. Returns JSON: {"fetched": int, "skipped": int, "errors": [str], "duration_ms": int}.
|
| search_templatesA | Search n8n.io workflow templates by keyword. Queries the official n8n template gallery API. Returns workflow templates that match the search query — each includes the nodes used, description, and a template ID for fetching the full workflow JSON. |
| get_templateA | Fetch the full workflow JSON for an n8n template. Returns the complete workflow definition including all node parameters, connections, positions, and settings. This is the data you need to understand exactly how a template is wired and recreate or adapt it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: get_doc retrieves a specific doc page, list_docs enumerates all docs, search_docs searches docs, get_template fetches full workflow JSON, search_templates queries templates, refresh updates the cache. No ambiguity.
All tool names use snake_case and follow a verb_noun pattern except 'refresh' which is a standalone verb but clear and consistent with the overall style.
6 tools is well-scoped for a documentation and template server. Covers essential operations without bloat.
Covers all necessary read operations for n8n docs and templates: list, get, search, and refresh. No obvious gaps for the stated purpose.