@octri/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OCTRI_API_KEY | No | API key for the documented API, not for Octri. Sent in the OCTRI_API_KEY_HEADER header. | |
| OCTRI_API_TOKEN | No | Bearer or OAuth2 token for the documented API, not for Octri. | |
| OCTRI_PROJECT_ID | Yes | The Octri project whose docs and endpoints this server exposes. | |
| OCTRI_API_BASE_URL | No | Base URL for endpoint calls. Defaults to the Base URL set in the project's SDK Studio. | |
| OCTRI_API_PASSWORD | No | Basic-auth password for the documented API. | |
| OCTRI_API_USERNAME | No | Basic-auth username for the documented API. | |
| OCTRI_API_KEY_HEADER | No | Header that carries OCTRI_API_KEY. | X-API-Key |
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
} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsB | Search the API documentation for an endpoint or concept |
| get_endpointB | Get full documentation for a specific API endpoint |
| list_endpointsA | List the API's endpoints and guides, grouped by section. A large API lists its sections with endpoint counts instead: pass |
| get_changelogC | Get recent API changes and breaking changes |
| list_sdksA | List the available SDK client libraries for this API (languages, versions, and download links) |
| get_guideA | Get the full content of a written guide (tutorial / conceptual doc) by its slug |
| get_sdk_methodsA | Show how to call this API through its generated SDKs. With |
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 7 tools
The tools divide cleanly into discovery (search_docs, list_endpoints), retrieval (get_endpoint, get_guide, get_changelog), and SDK tooling (list_sdks, get_sdk_methods). There is minor overlap in that list_endpoints and get_sdk_methods (without slug) both effectively enumerate endpoints, but their descriptions clarify the difference (endpoint catalog vs SDK method index).
Every tool follows a consistent verb_noun snake_case pattern: search_docs, get_endpoint, list_endpoints, get_changelog, list_sdks, get_guide, get_sdk_methods. The verbs map predictably to actions (list = enumerate, get = fetch a specific item, search = query), with no style deviations.
Seven tools is well-scoped for an API documentation server, covering discovery, retrieval, changelog, and SDK integration without padding. Each tool corresponds to a distinct documentation task that earns its place.
The surface covers the full documentation lifecycle: search, enumerate (endpoints and guides), fetch specific endpoints and guides, review changelogs, and consume SDKs (catalog plus per-endpoint method code). No obvious gaps remain for the stated purpose of browsing and consuming API docs and SDKs.