@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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsB | Search the API documentation for an endpoint or concept |
| get_endpointA | Get full documentation for a specific API endpoint |
| list_endpointsB | List all available API endpoints |
| get_changelogA | 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. Ready-to-use code snippets per endpoint in every supported language. Use |
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
Each tool targets a distinct resource: changelog, endpoint docs, guides, SDK methods, endpoint listings, SDK listings, and search. No two tools appear to overlap in purpose, so an agent can reliably select the right one.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (get_, list_, search_). The verbs are clear and the nouns are specific, making the naming predictable and uniform.
With 7 tools, the set is well-scoped for an API documentation server. Each tool serves a clear function without redundancy, and the count falls comfortably within the ideal 3-15 range.
The tool surface covers the core documentation workflows: discovering endpoints, retrieving details, searching, accessing guides, checking changelog, and SDK info. The only notable gap is the lack of a list_guides tool, though search_docs can partially compensate.