docs-n8n-mcp

by okdk7788

Overview Schema Source Related Servers Discussions Admin

Python

Local

List n8n Docs

list_docs

Read-onlyIdempotent

List all cached n8n documentation pages, with optional category filtering for specific node types or guides.

Instructions

List all n8n documentation pages from the cache.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_docs"
  }
}

Input Schema

Name	Required	Description	Default
`category`	No	Optional filter. Common values: - "core-nodes" : built-in core nodes (Code, HTTP Request, IF, etc.) - "app-nodes" : third-party app integrations (Slack, Airtable, etc.) - "trigger-nodes" : trigger nodes (Webhook, Cron, etc.) - "credentials" : credential setup guides - "cluster-nodes" : AI/LangChain nodes - "build" : workflow building guides - "get-started" : getting started tutorials - "deploy" : self-hosting/deployment - "administer" : administration guides - "release-notes" : version history Pass empty string (default) to list all.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds that data comes from cache, which is useful context. However, it does not disclose potential staleness of cached data or performance characteristics, which would enhance transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words. It is appropriately front-loaded, conveying the core action and resource immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (one optional parameter, output schema present), the description is largely complete. It could mention that results are from cache and may not be live, but overall it suffices for the agent to understand the tool's purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with the 'category' parameter having detailed examples. The tool description itself adds no extra parameter meaning beyond what the schema provides, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List'), the resource ('all n8n documentation pages'), and the source ('from the cache'). It effectively distinguishes from sibling tools like 'get_doc' (retrieves a single doc) and 'search_docs' (searches docs).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'get_doc' or 'search_docs'. There is no mention of prerequisites, typical use cases, or conditions where another tool would be better.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server