openwiki-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@openwiki-mcpgenerate the wiki for our repository using OpenWiki"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
openwiki-mcp
MCP server that exposes OpenWiki (OpenChamber) documentation generation as Model Context Protocol tools, so an official, unmodified OpenCode (or any MCP host) can generate and update repository wikis.
Fully independent of the opencode source tree — openwiki itself is resolved as
an external package (npm install or a staged offline bundle), and agent
credentials are relayed via environment variables, never stored.
Tools
Tool | Maps to agent | Notes |
| — (local only) | Inspects |
|
| First-time wiki generation. Optional |
|
| Diff-based refresh; only stale pages are regenerated. |
Related MCP server: mediawiki-mcp-server
Prerequisites
Node.js >= 22 (the MCP server and the agent child process both run under
node)An openwiki package install:
npm install -g openwiki # online machine, or# offline machine: copy a prepared bundle and point at it set OPENWIKI_PACKAGE_ROOT=D:\path\to\staged\bundle\node_modules\openwikiOPENWIKI_PACKAGE_ROOTmay point either directly at the package root or at a layout that containsnode_modules/openwiki. The staged bundle needs no junction or symlink tricks — Node resolves the agent's bare imports through the normalnode_moduleswalk.
Agent model configuration
The server relays (never stores) the following variables into the agent child process:
Env var (server side) | Meaning |
|
|
| Model id, e.g. |
| Point at a local OpenAI-compatible gateway to keep real keys out of the agent env |
| Key for the openai-compatible provider |
| Key for the |
| Optional; explicit path to the openwiki install |
Per-call modelId/language/userMessage tool arguments override the ambient
environment for that run.
Registering with OpenCode
Add to your opencode.json / opencode.jsonc:
{
"mcp": {
"openwiki": {
"type": "local",
"command": ["node", "D:/path/to/openwiki-mcp/dist/index.js"],
"environment": {
"OPENWIKI_PACKAGE_ROOT": "D:/path/to/staged/bundle/node_modules/openwiki",
"OPENWIKI_PROVIDER": "openai-compatible",
"OPENWIKI_MODEL_ID": "gpt-5",
"OPENAI_COMPATIBLE_BASE_URL": "http://127.0.0.1:4096/v1"
}
}
}
}The three tools then appear in every OpenCode conversation as ordinary tools.
Development
npm install
npm run build # tsc -> dist/
npm test # node --test (status inspection unit tests)
npm run dev # run the server via tsx (dev)Smoke tests:
node scripts/smoke.mjs <dir> status # local inspection only
node scripts/smoke.mjs <dir> init "note" # full agent run (needs model env)Manual MCP protocol check:
@'
{"jsonrpc":"2.0","id":0,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"t","version":"1"}}}
{"jsonrpc":"2.0","method":"notifications/initialized"}
{"jsonrpc":"2.0","id":1,"method":"tools/list"}
'@ | node dist/index.jsDesign notes
src/openwiki/resolve.ts— package resolution:OPENWIKI_PACKAGE_ROOT, thenrequire.resolve("openwiki/package.json").src/openwiki/worker.mjs— adapter worker: reads one job from stdin, imports the agent entry by absolute path, emits NDJSON progress on stdout. Ported from the opencode fork'spackages/openwikiadapter and kept independent.src/openwiki/run.ts— spawns the worker as a child of the MCP server, so a hung agent can never take down the MCP host.src/status.ts— local status inspection (no model cost).v0.1 maps
generateto the agent'sinitcommand, matching openwiki 0.3.x whereinitis the first-generation command andupdatethe refresh one.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityCmaintenanceMCP server for codewiki.google — AI-powered wiki documentation for open-source repositories. Search repos, fetch wiki content, and ask questions about any repo.37214MIT
- AlicenseAqualityAmaintenanceMCP server for MediaWiki wikis. Search, read, edit, and manage wiki content from AI assistants. Includes formatting, link checking, revision history, and markdown conversion.4320MIT
- AlicenseAqualityCmaintenanceEnables searching and retrieving Minecraft Wiki content in multiple formats (wikitext, HTML, markdown) through MCP tools, with batch retrieval and health monitoring.51MIT
- Flicense-qualityCmaintenanceEnables building and querying a local wiki knowledge base from raw source files via MCP tools and a PyQt viewer.
Related MCP Connectors
Generate AGENTS.md, AP2 compliance docs, checkout rules, debug playbook & MCP configs from any repo.
Self-hostable team wiki; agents read & write it via MCP; Atlas turns your repo into a cited wiki.
A MCP server built for developers enabling Git based project management with project and personal…
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Blanceone/openwiki-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server