ibmi-docs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IBMI_DOCS_VERSION | No | IBM i documentation version to use, e.g. 7.5.0. | |
| IBMI_DOCS_LOG_LEVEL | No | Logging level (e.g., DEBUG, INFO, WARNING). | |
| IBMI_DOCS_MAX_CHARS | No | Maximum number of characters to include from fetched document content. | |
| IBMI_DOCS_CACHE_PATH | No | File path for caching API responses. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_ibm_docsA | Search IBM i documentation (IBM's own docs search index). Prefer short object/command names (e.g. HTTP_GET, WRKACTJOB, CHGJRN) over long prose. Results are ranked by IBM relevance — read titles/snippets and pick the best match; do not assume hit #1 is always right. Next step: call fetch_ibm_doc with the chosen result's href. |
| fetch_ibm_docA | Fetch one IBM i documentation topic as plain text. Pass the href (or content API URL) from search_ibm_docs. Returns title, url, text, and truncated/stale flags. Prefer search first so you pick the right 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 2 tools
The two tools have clearly distinct roles: one searches the documentation index, the other fetches a specific page. There is no overlap or ambiguity in their purposes.
Both tools use a consistent verb_object pattern: 'search_ibm_docs' and 'fetch_ibm_doc'. The slight singular/plural difference is minor and does not affect consistency.
Two tools is exactly right for a documentation search and retrieval server. Each tool is essential and there is no redundant functionality.
The workflow of search-then-fetch is fully covered. A user can find a relevant topic and retrieve its content without dead ends.