mcp installations
An installation is a server address of its own, backed by a credential you store, so a team can use your API through agents without anyone pasting a key into a config file. This lists each one with its ID, name, the kind of credential and its last characters, who may use it, its limits and when it was last used. Changes apply at once, with no MCP publish. See installations for a team.
octri mcp installations [list | create | update | credential | rotate | connections | revoke]octri mcp installations create <name>
Creates an installation and prints its address and, with token access, its token. The token is shown once, so copy it then.
Arguments
<name>stringrequiredWhat to call it.
Flags
--scheme <scheme>stringrequiredHow the stored credential is sent to your API. With neither secret flag, the secret is asked for, masked. It's never a flag value, which would land in your shell history.
| Value | Meaning |
|---|---|
apiKey | An API key in a header. --header names it, such as X-API-Key |
bearer | A bearer token |
basic | A username and password. --username gives the username, and the secret is the password |
--header <name>stringFor apiKey: the header the key goes in.
--username <name>stringFor basic: the username.
--secret-env <VAR>stringThe name of an environment variable that holds the secret, without $.
--stdinbooleanReads the secret from a pipe.
--access <who>listWho may use it, comma-separated.
| Value | Meaning |
|---|---|
token | Anyone with its token, for scripts and shared agents |
team | People on this project, signed in with Octri |
link | Anyone with the address. Only for a --read-only installation |
--read-onlybooleanOnly tools that read.
--dry-runbooleanBuilds each call and sends none.
--deny <tools>listHides these tools by name.
octri mcp installations update <id>
Changes the name, access or limits, and leaves alone whatever you don't pass. Turning token access on prints a new token.
Arguments
<id>stringrequiredThe installation.
Flags
--name <name>stringA new name.
--access <who>listReplaces who may use it.
--read-onlybooleanOnly tools that read. --no-read-only lifts it.
--dry-runbooleanSends nothing. --no-dry-run lifts it.
--deny <tools>listReplaces the denied tools. --deny= clears them.
octri mcp installations credential <id>
Replaces the stored credential. It takes --scheme and the secret the same way create does.
Arguments
<id>stringrequiredThe installation.
octri mcp installations rotate <id>
Issues a new token. The old one stops working at once.
Arguments
<id>stringrequiredThe installation.
octri mcp installations connections <id>
Lists the people signed in through one installation.
Arguments
<id>stringrequiredThe installation.
octri mcp installations revoke <id> --yes
Deletes the installation and its stored credential, so every client using it stops on its next call.
Arguments
<id>stringrequiredThe installation.
Flags
--yesbooleanrequiredConfirms it.
Examples
Create a read-only installation for the team
The secret comes from a variable, so it never appears in the command.
octri mcp installations create "Support team" --scheme bearer --secret-env DEMO_API_TOKEN --access team,token --read-only✔ Creating Support team
✔ Support team created (inst_5lvRjw7vImpUP5uVCn9V5K)
url https://api.octri.dev/api/v1/public/mcp/6acd4f5218c2528b5932744f/i/inst_5lvRjw7vImpUP5uVCn9V5K/mcp
octri_mcp_it_EXAMPLE-shown-once-copy-it-now
â–² Copy this token now. It is not shown again.List installations
octri mcp installations✔ Loading installations
MCP installations (1)
ID NAME CREDENTIAL ACCESS LIMITS USED
─────────────────────────── ────────────── ─────────────── ────── ───────── ────
inst_Ek0ndc8C6eaRNV7V9nnpXW Docs sandbox bearer ••••real token read-only -Related
octri mcp connections: List and sign out the people signed in to the hosted server.octri mcp audit: Every write an agent attempted, approved or not, filtered and exportable.- Hosted server and sign-in