Aindreyway MCP Codex Keeper
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_documentationC | List all available documentation sources |
| add_documentationC | Add a new documentation source |
| update_documentationC | Update documentation content from source |
| search_documentationC | Search through documentation content |
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 4 tools
Each tool targets a distinct action on documentation sources: listing, adding, updating, and searching. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern with snake_case (list_, add_, update_, search_). This makes the API predictable and easy to navigate.
Four tools is a well-scoped set for a documentation keeper, covering the essential operations without bloat or unnecessary additions.
The set covers list, add, update, and search, but lacks a delete operation, which is a minor gap in full lifecycle management. Agents can work around this limitation, but it is not a complete CRUD surface.