Claude MCP Knowledge Base
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | Your GitHub Personal Access Token for indexing repositories. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_knowledge_baseA | Search the MCP knowledge base for documentation, examples, and best practices. Searches across official MCP repos, community servers, and your repositories with .claude/ directories. |
| list_repositoriesA | List all repositories currently indexed in the knowledge base with file counts. |
| get_mcp_specificationA | Get the current MCP protocol specification, best practices, and common patterns. Always up-to-date knowledge about MCP development. |
| add_blocklist_entryA | Add an entry to the blocklist. Can block MCP servers or exclude file patterns from indexing. |
| check_blocklistC | Check if a server or file pattern is blocked. |
| update_knowledge_baseA | Manually trigger a knowledge base update from GitHub. Normally happens automatically every 30 minutes. |
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 6 tools
Most tools target distinct resource-action pairs, but search_knowledge_base and get_mcp_specification both cover MCP documentation and best practices and could be confused. The descriptions help by distinguishing broad search from canonical spec retrieval, so the ambiguity is limited.
All tool names consistently follow a verb_noun pattern: search, list, get, add, check, update. Multiword objects like blocklist_entry and knowledge_base do not break the predictability of the naming convention.
Six tools is a well-scoped count for a knowledge base MCP server. Each tool covers an essential workflow: searching, listing indexed content, retrieving the spec, managing blocklist entries, and triggering updates.
The core search, listing, spec retrieval, and update workflows are covered, but the blocklist lifecycle is incomplete—there is no way to remove an entry or list all blocked entries. An accidental blocklist addition becomes a dead end for the agent.