Plug Perfect Wiki into Gemini CLI, and your terminal agent can look up product specs, metric definitions and team processes in the middle of a task β then write back what it learned.
A single gemini mcp add registers the server in your user settings. Authenticate once inside a session, and Gemini CLI can call every Perfect Wiki tool.
When a task depends on how your company does things, Gemini CLI queries Perfect Wiki mid-task, cites the page it relied on, and can record new decisions back into the knowledge base.
queries/weekly_churn.sql with a comment linking to the definition.gemini mcp add --transport http --scope user perfect-wiki https://api.perfectwiki.xyz/mcpgemini and run /mcp auth perfect-wiki./mcp to see the Perfect Wiki tools, then ask something like βWhat does our on-call handbook say about paging?βMore details in the Perfect Wiki MCP server guide and Gemini CLI's MCP documentation.
Generate a token in the Perfect Wiki settings of the knowledge base you want to expose. Each token is scoped to a single knowledge base and has read & write access.
Analysts and data engineers get SQL and dashboards built on the definitions in your metrics glossary β not on whatever the model assumes βactiveβ means.
Joining a team or picking up an unfamiliar repo? Gemini CLI reads the architecture and ownership pages and explains the service in context.
Compare what the product spec asks for with what the code does, and turn the gaps into a to-do list before release.
Ask a natural-language question and get an AI answer with sources.
List every page in the connected 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 info about the connected knowledge base.
Download any of our 284 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 284 SOP templates βAdd the server with gemini mcp add, start a Gemini CLI session and run /mcp auth perfect-wiki. Finish the sign-in in your browser, choose the knowledge base and allow access.
With --scope user the entry is written to ~/.gemini/settings.json under mcpServers, so it is available in every project. You can edit that file directly too β for a legacy API token, add a headers entry with your Authorization header.
Since June 2026, Gemini CLI serves Gemini Code Assist Standard and Enterprise licences and paid Gemini API keys. Free and Google AI Pro/Ultra consumer users have moved to Antigravity CLI, which is configured differently β see our Google Antigravity guide.
Only if you allow it. When you connect with OAuth you choose read-only (wiki:read) or read & write (wiki:write) on the consent screen. Legacy API tokens always have full access to their knowledge base. Most MCP clients also ask for your confirmation before running a tool that writes.
Yes. Each connection is scoped to one knowledge base, so add the server once per knowledge base and give each a unique name β for example perfect-wiki-hr and perfect-wiki-engineering. The assistant can then search or update a specific knowledge base by name.
The Perfect Wiki MCP server only forwards the requests Gemini CLI 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 β
Keep your SOPs, manuals and FAQs in Perfect Wiki β and give your whole team answers right where they work.