MCP Wiki Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WIKI_PATH | No | Absolute path to a local wiki folder. If unset, defaults to ./wiki next to server.py. | |
| WIKI_GIT_URL | No | URL of a remote git repository to use as the wiki source. Takes precedence over WIKI_PATH. | |
| WIKI_CACHE_DIR | No | Directory used to cache the cloned remote wiki repository. Defaults to the system tempdir. | |
| WIKI_GIT_BRANCH | No | Branch to use for the remote git repository. Defaults to "main". |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wiki_gitA | Search or read the 'git' wiki topic. No args: list pages. query=: find matches. page=<filename.md>: full page. |
| wiki_pythonA | Search or read the 'python' wiki topic. No args: list pages. query=: find matches. page=<filename.md>: full page. |
| wiki_sqlA | Search or read the 'sql' wiki topic. No args: list pages. query=: find matches. page=<filename.md>: full page. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Tools are clearly separated by wiki topic (git, python, sql), so an agent can pick the right one when the topic is known. However, the identical interface and absence of a generic topic parameter or cross-topic search mean ambiguity arises when the topic is unspecified or spans multiple wikis.
All tool names follow a consistent wiki_<topic> pattern (wiki_git, wiki_python, wiki_sql), making them predictable and easy to parse.
Three tools map to three topics, which is a reasonable number for the stated scope, though a single parameterized tool would reduce duplication and scale better.
Read/list/search operations are covered per topic, but there is no write capability (create/edit/delete) and no way to discover or query other topics, leaving notable gaps for a wiki server.