mcp serve

Runs the CLI itself as an MCP server over stdio, so an AI assistant can manage your Octri account with typed tools: push a spec, wait for a build, read the generated source, and read the production errors that build caused. It's separate from the server you publish for your own API.

It uses your stored profile, so sign in with auth login first. The assistant never sees your session or token.

To connect an assistant with nothing to install, use Octri's hosted server at https://mcp.octri.dev/mcp instead. It covers projects, specs, SDK builds and docs pages. See AI assistants.

octri mcp serve [--allow-publish] [--allow-delete]

Flags

--project <id>stringdefault: the selected project

The project tools act on when a call doesn't name one.

--profile <name>string

Which stored environment to use.

--api-url <url>string

Point at another API.

--allow-publishboolean

Also offers the tools that publish: SDK builds and the MCP package to registries, the docs nav, status page posts, and the MCP custom domain.

--allow-deleteboolean

Also offers the tools that delete or revoke: specs, components, webhooks, incidents, announcements, SLOs, the MCP domain, installations and sign-ins.

What it can do

Reads are always on, and so are writes that only reach your own project, such as saving docs settings. Anything public or irreversible is offered only with the flag for it.

Area	Always on	With `--allow-publish`	With `--allow-delete`
Specs	List, push, import from a URL, read the source, converter import		Delete a spec
SDKs	Languages, operations, settings, validate, preview, build, wait, retry, read and diff generated files, repos, quickstart	Publish a build to registries
Docs	Pages, nav, home page, redirects, nav buttons, theme and settings, playground, custom code, components, draft endpoints, GitHub docs files, release history	Publish the nav	Delete a component
MCP	Tools, permissions, usage, calls, package, domain, installations, sign-ins, audit log, changes, outages, quality, dismissing a finding, narrowing an installation	Publish the package, set the custom domain	Remove the domain, revoke an installation or a sign-in
Monitoring	Summary, issues and their status, logs, releases, performance, incidents, announcements, SLOs and setting one	Create, post to and edit incidents, save announcements	Delete incidents, announcements and SLOs
Webhooks	List, events, create, update, test, deliveries		Delete a webhook

Some things stay with you

The assistant can't create an installation, replace its credential, rotate its token or widen its access, because each would put a secret in its context. It can only narrow an installation's limits. Tools never return the address of an installation with link access either, since that address alone lets anyone use the stored credential. Run those from your own terminal.

Every ID a tool takes must be a plain ID, so an assistant can't steer a harmless call onto a gated one by packing a path into it.

Examples

Add it to an assistant

Most assistants read a config like this one.

{
  "mcpServers": {
    "octri": {
      "command": "octri",
      "args": ["mcp", "serve"]
    }
  }
}

octri auth login: Sign in to Octri and store the session in your profile.
Global flags

Flags

What it can do

Examples

Add it to an assistant

Related