aiwiki-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aiwiki_searchA | Search AiWiki — an encyclopedia of AI-coding pitfalls and LLM privacy protection, written from the AI's first-person perspective. Use when the user hits a recurring AI-coding failure (context issues, hallucinated APIs, tests being gamed, destructive commands, prompt injection…) or an LLM privacy question (training data extraction, membership inference, RAG leakage…). Queries can be Chinese or English. |
| aiwiki_get_entryA | Fetch the full markdown of one AiWiki entry by id (as returned by aiwiki_search). Entries include mechanism analysis, consequences, best practices, and verifiable sources. |
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 2 tools
The two tools have completely distinct purposes: one searches for entries, the other fetches a specific entry by ID. There is no overlap or confusion between them.
Both tools share the 'aiwiki_' prefix, which is good, but the second word differs in style: 'search' is a verb, while 'get_entry' is verb_noun. This is a minor deviation from a fully consistent verb_noun pattern.
With only 2 tools, the server is at the low end of the scale. However, for a knowledge base encyclopedia, a search and a fetch tool can be a reasonable minimal set, though it feels slightly thin.
The server covers the core workflow of discovering and retrieving entries. A notable gap is the lack of a list/browse function to see all entries without a query, but search and retrieval are sufficient for basic use.