Developer · Local MCP server
Octri API Docs
Search an Octri project's API docs and call its endpoints as tools, shaped by its SDK Studio config.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.octri/mcp- Version
- 1.1.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-25
- Updated
- 2026-09-25
- Publisher
- dev.octri · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain octri.dev · how
- Website
- octri.dev
- Repository
- github.com/octridev/octri-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @octri/mcp | 1.1.1 | stdio |
How to connect Octri API Docs
Octri API Docs runs locally from a Node.js package published to the npm registry: @octri/mcp version 1.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @octri/mcp@1.1.1. It reads these environment variables: OCTRI_PROJECT_ID (required), OCTRI_API_BASE_URL, OCTRI_API_TOKEN (secret), OCTRI_API_KEY (secret), OCTRI_API_KEY_HEADER, OCTRI_API_USERNAME and OCTRI_API_PASSWORD (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@octri/mcp@1.1.1"
],
"env": {
"OCTRI_PROJECT_ID": "<value>",
"OCTRI_API_BASE_URL": "<value>",
"OCTRI_API_TOKEN": "<secret>",
"OCTRI_API_KEY": "<secret>",
"OCTRI_API_KEY_HEADER": "<value>",
"OCTRI_API_USERNAME": "<value>",
"OCTRI_API_PASSWORD": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from dev.octri
| Server | Runs |
|---|---|
| Octri CLIPush OpenAPI specs, build SDKs in ten languages, publish API docs, and triage production SDK errors. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| OctoCounts MCP ServerAnalyze and compare public GitHub repo line counts (SLOC) via OctoCounts, from any MCP client. | Local · stdio |
| OctoperfDrive OctoPerf load testing from any AI agent: import, edit, validate, run scenarios, read metrics. | Remote · HTTPLive check: sign-in required |
| Octopus BlackboardShared memory & coordination for AI coding agents - a blackboard, not an orchestrator. | Local · stdio |
| OctoWatch DLPRead-only OctoWatch DLP Cloud MCP: risks, idle time, productivity, monitoring. | Local · stdio |
| ocularVision tools for coding agents: screenshots, OCR, UI diffs, errors, tables, and charts. | Local · stdio |
| Ocultar PiiZero-egress PII redaction for Claude. Runs locally - no data leaves your infrastructure. | Local · stdio |
| Odoo MCP GatewaySecurity-first MCP gateway for Odoo 17/18/19 - YAML-driven security, 27 tools. | Local · stdio |