Agenten stärken
Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
npx -y @octri/[email protected]Claude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.
OCTRI_API_KEY=<secret> OCTRI_PROJECT_ID=<value> OCTRI_PROFILE=<value> HTTPS_PROXY=<secret> NO_PROXY=<value> claude mcp add dev.octri-cli -- npx -y @octri/cli@1.0.6In einem Terminal ausführen.
{ "mcpServers": { "dev.octri-cli": { "command": "npx", "args": [ "-y", "@octri/[email protected]" ], "env": { "OCTRI_API_KEY": "<secret>", "OCTRI_PROJECT_ID": "<value>", "OCTRI_PROFILE": "<value>", "HTTPS_PROXY": "<secret>", "NO_PROXY": "<value>" } } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
octri is the command line for your Octri project. It does what the dashboard
does: push a spec, build SDKs, publish docs, and work through the errors those
SDKs report from production.
Octri takes an OpenAPI spec and gives you a documentation site, client libraries in ten languages, an MCP server, and monitoring for the API behind all of it. See octri.dev.
Push OpenAPI specs, build SDKs in ten languages, publish API docs, and triage production SDK errors.
Node 20 or newer.
npm install -g @octri/cli
octri --help
octri auth login
octri projects use
octri specs push ./openapi.yaml
auth login prompts for your email and password, and for your authenticator
code if you have two-factor on. projects use with no argument opens a picker.
specs push waits for the pipeline, not the upload. Your spec parses in about a
second, then the doc pages, search index and changelog get written behind it.
The spinner names the stage it is on.
octri sdk audit # what is costing you, scored
octri sdk build --lang go,typescript --download
In a terminal, sdk build draws a lane per language and repaints it through
generating, verifying, packaging, installing, ready. Piped or under
CI it prints append-only lines instead, and exits non-zero if any language
fails, so it works as a build step with no extra flags.
sdk audit scores the spec and marks which findings the generator can fix on
its own. octri sdk audit apply <key> writes one in.
For a look at real generator output without spending a build:
octri sdk preview --lang go
octri sdk preview --lang go --show client.go
octri docs versions publish <specId>
octri docs versions label <specId> "Stable"
octri docs domain set docs.example.com
docs domain prints the CNAME and TXT records to create, then docs domain verify checks them.
Reads and triage run on your session, so they need nothing but a login:
octri monitoring summary
octri monitoring issues --status unresolved
octri monitoring issue <id>
octri monitoring resolve <id>
monitoring issue prints the stack and marks which frames resolved against
uploaded source maps. When none of them did, the release those errors came from
has no symbols, and the CLI says so.
The two upload commands work differently. They talk to the monitoring service directly with an ingest token, because a CI job has one secret and no way to log in:
# CI
octri monitoring sourcemaps upload ./dist \
--url "$MONITORING_URL" --token "$MONITORING_TOKEN" \
--environment "$MONITORING_ENVIRONMENT" --release "$GIT_SHA"
# your own machine, already signed in
octri monitoring sourcemaps upload ./dist
Run octri monitoring config for the three values to store as CI secrets. The
release you upload under has to equal the release your SDK reports at runtime,
or the service has nothing to pair a trace with.
Run octri <group> --help for one group on its own.
Global flags: --project <id>, --profile <name>, --api-url <url>, --json,
--quiet, --plain, --no-color.
--json is the one to script against:
octri sdk builds --json | jq '.[0].status'
octri monitoring issues --status unresolved --json | jq 'length'
NO_COLOR and FORCE_COLOR are both honoured.
State lives in ~/.octri/config.json, mode 0600, since it holds session
tokens. OCTRI_CONFIG_DIR moves it.
Profiles keep environments side by side:
octri config use prod --api-url api.octri.dev
octri config set defaultLanguages go,rust,swift
Every value resolves flag first, then environment, then the stored profile.
The CLI and octri mcp serve read the standard proxy variables, in upper or
lower case, with no extra Node flag. https:// requests use HTTPS_PROXY, or
HTTP_PROXY when that is the only one set. Hosts listed in NO_PROXY, and
their subdomains, connect directly; * turns the proxy off.
export HTTPS_PROXY=http://user:[email protected]:3128
export NO_PROXY=localhost,127.0.0.1,corp.example
octri specs push ./openapi.yaml
If the proxy inspects TLS with its own certificate authority, point Node at
that CA with NODE_EXTRA_CA_CERTS=/path/to/ca.pem.
MCP clients usually start servers with a minimal environment, so set these in
the server's env block rather than relying on your shell.
octri mcp serve
This speaks MCP over stdio and offers the same commands as typed tools. An assistant can push a spec, wait for the build, read the generated Go, and then read the production error that build caused.
To add it to Cursor or VS Code in one click, through npx so no global install
is needed:
The server uses the profile from octri auth login, so sign in first, or set
OCTRI_API_KEY in its environment. Listed in the official MCP Registry as
dev.octri/cli.
// Claude Desktop / Cursor
{
"mcpServers": {
"octri": {
"command": "octri",
"args": ["mcp", "serve"]
}
}
}
Credentials come from your stored profile and the assistant never sees them. Reads are open. The two operations you cannot take back are refused unless you start the server with the flag for them:
octri mcp serve --allow-publish # publishing to package registries
octri mcp serve --allow-delete # deleting specs
Tool failures come back as tool results rather than protocol errors, so an assistant can read the message and correct itself.
/ws/sdk socket authenticates
from a header or cookie, which Node's built-in WebSocket cannot set, and a
WebSocket dependency would buy about a second of latency on a build that takes
minutes.tar and zip readers, so
neither binary needs to be installed. Both refuse entries that would write
outside the destination directory.@modelcontextprotocol/sdk is the only runtime dependency. Colour, spinners,
progress bars, tables and prompts are all local.MIT licensed.
Push OpenAPI specs, build SDKs in ten languages, publish API docs, and triage production SDK errors.
{ "mcpServers": { "dev.octri-cli": { "command": "npx", "args": [ "-y", "@octri/[email protected]" ], "env": { "OCTRI_API_KEY": "<secret>", "OCTRI_PROJECT_ID": "<value>", "OCTRI_PROFILE": "<value>", "HTTPS_PROXY": "<secret>", "NO_PROXY": "<value>" } } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Der Herausgeber nennt diese Umgebungsvariablen: OCTRI_API_KEY, OCTRI_PROJECT_ID, OCTRI_PROFILE, HTTPS_PROXY, NO_PROXY.
Octri CLI läuft lokal über stdio.
Zuletzt geprüft: 2026-11-08. Push OpenAPI specs, build SDKs in ten languages, publish API docs, and triage production SDK errors.