Hey community! We’ve refreshed n8n Docs with a new information architecture that makes it easier to navigate, discover related topics, and find answers faster.
Connect your agent directly to the docs (MCP)
You can now access our docs via MCP, so you can connect your agent to n8n Docs directly and use it as a source of truth while you build.
Contributing is easier (and more consistent)
We’ve added a contribution guide and a style guide to help you propose changes that fit our internal standards and keep the docs consistent.
If you want extra help getting your changes into shape, we also have skills in the n8n-docs repo that guide you in making contributions aligned with those standards.
Spot an issue?
If you notice broken links, missing content, or anything that looks off, please create an issue in the n8n-docs repo.
docs mcp of n8n can we access it thorhg the instance level mcp? like am using instance level mcp
like **https://<n8n>.<n8n>.<n8n>/mcp-server/http just an example using mcp wiht opencode and the calude code?
No, for now the two are via separate MCP servers that do different things
n8n instance MCP (https://<your-instance>/mcp-server/http) lets AI clients like Claude Code build, edit, and execute workflows in your instance.
The docs MCP (https://docs.n8n.io/~gitbook/mcp) is served by GitBook (the underlying documentation platform) and just gives AI tools access to n8n’s documentation content — no connection to your instance.
You can use both simultaneously in Claude, for example, by adding them as separate MCP servers in your config.