AI knowledge base for Cline.
Add Perfect Wiki to Cline as a remote MCP server. Before Cline plans a task, it can look up how your team builds things — and when the task is done, write down what changed.
Connect Cline in two minutes.
Register Perfect Wiki from Cline's Remote Servers tab, then add your Perfect Wiki API token to cline_mcp_settings.json. Cline lists the knowledge base tools right next to your other MCP servers.
- →Streamable HTTP transport — nothing to install locally
- →Token scoped to a single knowledge base
- →Pick which Perfect Wiki tools Cline may auto-approve
- Server name
- perfect-wiki
- Server URL
- https://api.perfectwiki.xyz/mcp
- Transport
- Streamable HTTP
Plan with your team's knowledge — act with Cline.
In Plan mode, Cline pulls the relevant specs and conventions from Perfect Wiki so the plan matches how your team works. In Act mode, it can record decisions and updated instructions back to the wiki.
- →Plans grounded in your specs and architecture notes
- →Reads a single page instead of guessing from the codebase
- →Writes decisions back to the wiki once the work is done
How to connect Perfect Wiki to Cline.
- 1Generate an API token in the Perfect Wiki settings of the knowledge base Cline should use.
- 2In Cline, click the MCP Servers icon, open the Remote Servers tab and enter the name
perfect-wiki, the URLhttps://api.perfectwiki.xyz/mcpand the transport Streamable HTTP. Click Add Server. - 3The form has no headers field, so open
cline_mcp_settings.jsonand add theAuthorizationheader with your token, as shown on the right. - 4Ask Cline something like “Check Perfect Wiki for our logging conventions.”
More details in the Perfect Wiki MCP server guide and Cline's MCP documentation.
Keep "type": "streamableHttp" — each Perfect Wiki token is scoped to one knowledge base and has read & write access. Add tool names such as "ask" to autoApprove to skip the confirmation prompt for read-only calls.
What your team does with Perfect Wiki in Cline.
Plans that match your architecture
Cline reads your architecture notes and service pages while planning, so proposals fit the system you actually run.
Onboarding a new codebase
New to a repo? Let Cline combine the code with your wiki’s setup guides and glossary to explain how the pieces fit.
Decision records without the chore
When Cline finishes a change that involved a trade-off, ask it to capture the decision as a new wiki 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 →Frequently asked questions
Without an explicit type, Cline treats a remote server as SSE. The Perfect Wiki MCP server uses Streamable HTTP, so set "type": "streamableHttp" (or pick Streamable HTTP in the Remote Servers form).
The Remote Servers form doesn’t have a headers field. Add the server there, then open cline_mcp_settings.json and add a headers object with "Authorization": "Bearer <your-api-token>".
Yes. List the tools you trust in the autoApprove array — for example ask, list_pages and get_page — and keep write tools like update_page out of it so Cline still asks before changing a page.
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, Cline 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. Cline 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 Cline 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 Cline.
Keep your SOPs, manuals and FAQs in Perfect Wiki — and give your whole team answers right where they work.