AI knowledge base for n8n.
Give your n8n AI Agents a knowledge base to work from. Add Perfect Wiki with the MCP Client Tool and automate support replies, onboarding and documentation updates — all answered from your own SOPs.
Drop Perfect Wiki into any AI Agent node.
Attach the MCP Client Tool to your AI Agent, point it at Perfect Wiki and connect an MCP OAuth2 credential. The agent can then search, read and update your knowledge base as steps in any workflow.
- →HTTP Streamable transport — no custom HTTP requests to build
- →MCP OAuth2 credential with dynamic client registration
- →Choose which Perfect Wiki tools the agent may call
- Endpoint URL
- https://api.perfectwiki.xyz/mcp
- Server Transport
- HTTP Streamable
- Authentication
- MCP OAuth2
- Tools to Include
- All
Workflows that answer from your SOPs — around the clock.
Trigger on a new ticket, email or chat message, let the agent look up the answer in Perfect Wiki, and send a reply or route the case. When an answer is missing, the same workflow can draft the page that fills the gap.
- →Replies drafted from approved SOPs, with the source page
- →Routes cases the knowledge base can’t answer to a human
- →Creates or updates pages from resolved tickets
How to connect Perfect Wiki to n8n.
- 1Open your workflow, select the AI Agent node and add the MCP Client Tool. On n8n 1.122+ you can also use the standalone MCP Client node.
- 2Set Endpoint URL to
https://api.perfectwiki.xyz/mcpand Server Transport to HTTP Streamable (n8n 1.104+). - 3Set Authentication to MCP OAuth2, create a new MCP OAuth2 API credential with Use Dynamic Client Registration turned on (n8n 1.119+), and click Connect to sign in to Perfect Wiki.
- 4Set Tools to Include to All — or pick only the tools this workflow needs — and run a test execution.
More details in the Perfect Wiki MCP server guide and n8n's MCP documentation.
Use Bearer Auth
For service-account style workflows that shouldn't depend on a personal sign-in, set Authentication to Bearer Auth and paste a Perfect Wiki API token as the Bearer Token.
Generate the token in the Perfect Wiki settings of the knowledge base the workflow should use. Tokens are scoped to one knowledge base and have read & write access — limit Tools to Include if the workflow only needs to read.
What your team does with Perfect Wiki in n8n.
Ticket triage and replies
On every new helpdesk ticket, the agent searches your SOPs, drafts the reply and routes anything it can’t answer to the right team.
Answer bots for Slack and email
Connect an inbox or chat trigger so employees get policy and process answers from the wiki without waiting for a person.
Docs updated from resolved cases
When a ticket closes with a new fix, a scheduled workflow turns the resolution into a new or updated troubleshooting page.
Ask a question in plain language and get an AI answer from your SOPs and FAQs, with the source pages.
See which knowledge bases the connection covers and the access level for each.
List every page in a knowledge base.
Read the full content of a specific page.
Create a new page — draft SOPs straight from chat.
Update an existing page, so SOPs never go stale.
Remove pages that are no longer needed.
Get the name and access level of one knowledge base.
Start from a ready-made SOP. Keep it alive here.
Download any of our 294 standard operating procedure templates in Word, PDF, Excel or CSV, no sign-up needed. Then put it in Perfect Wiki so your team can find it and ask about it.
Browse all 294 SOP templates →- Health & SafetyFire Evacuation SOP Template
- Health & SafetyFirst Aid Response SOP Template
- Health & SafetyHazard Identification and Risk Assessment SOP Template
- Health & SafetyHazardous Chemical Handling SOP Template
- Health & SafetyManual Handling and Lifting SOP Template
- Health & SafetyPPE Selection and Use SOP Template
Frequently asked questions
HTTP Streamable transport in the MCP Client Tool requires n8n 1.104 or later, and the MCP OAuth2 credential with dynamic client registration requires 1.119 or later. The standalone MCP Client node is available from 1.122.
Use MCP OAuth2 when a person connects their own Perfect Wiki account and you want read-only or read & write access chosen on the consent screen. Use Bearer Auth with an API token for service-style workflows that should run independently of any one user.
Yes. Connect with read-only permission on the OAuth consent screen, or narrow Tools to Include to ask, list_knowledgebases, list_pages and get_page so the agent never sees the write tools.
Uploaded files are a snapshot: they go stale the moment a policy changes, and they stay in one chat or project. Through the MCP server, n8n reads the current version of your SOPs and FAQs from Perfect Wiki every time, links to the source page, and only reaches the knowledge bases you connect.
Only if you allow it. When you sign in with OAuth you choose Read only or Read & write on the consent screen, and writes only work in knowledge bases where you can edit. Legacy API tokens always have full access to their one knowledge base. Most MCP clients also ask for your confirmation before running a tool that writes.
Yes, with a single connection. When you sign in, choose all knowledge bases you can access (including ones you get access to later) or only the ones you select. n8n can search across all of them at once and has to name the target knowledge base for every change. API tokens cover one knowledge base each, so add one server entry per token.
The Perfect Wiki MCP server only forwards the requests n8n makes. Tool results — the pages and answers it fetches — are passed to the model as part of the conversation and handled under your AI provider's data policy.
The MCP server is included in every Perfect Wiki plan, and the same API rate limits apply. You can try it with the 14-day free trial — no credit card required.
Didn't find what you're looking for? Contact our support →
Put your SOPs to work in n8n.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.