Octopus is a skill registry reached through MCP. Your client handles sign-in and retrieves the instructions and files for a selected skill. The tools your client already has determine how it can carry out those instructions.

Before you start

Install a current version of Codex with remote HTTP MCP and OAuth support. You need an Octopus account and permission to configure MCP servers in your client. Use an account on this environment; staging and production accounts are separate.

1. Add the server

Run these commands in your terminal:

codex mcp add octopus --url https://app.9octopus.work/mcp --oauth-client-registration dcr
codex mcp login octopus --oauth-client-registration dcr
codex mcp list

Codex uses dynamic client registration for this connection. Its CLI and IDE extension share MCP configuration. If your version does not recognize the registration option, update Codex and check codex mcp add --help before retrying.

2. Approve the connection

Your client opens an Octopus sign-in and consent page. Check the client name, sign in, and approve access. If your terminal prints a login URL instead of opening a browser, use that URL to finish the same flow.

You do not need to create a connection record first or paste bearer tokens into a configuration file. The client handles the OAuth exchange. After it completes, open Connected agents to confirm that the connection is active.

3. Find and load a skill

Ask your agent to find a public skill for a concrete task. For example:

Use the Octopus MCP server to find public skills for reviewing an API change. Show me the relevant descriptions and sources before choosing one.

You can also browse the catalog, inspect a skill’s manifest and source, and use Copy agent prompt. That prompt includes a skill ID and an exact version ID. Ask the agent to confirm the loaded version before following its instructions.

A pinned release keeps the selected instructions consistent. It does not guarantee that all instructions suit your project; check the skill’s requirements and the permissions available to your client.

4. Manage or revoke access

Each client connection is independently revocable from Connected agents. Revocation invalidates its access. To reconnect, clear or log out of the saved client connection and repeat authentication; Octopus creates a new connection when the exchange completes.

Troubleshooting

  • Authentication required or HTTP 401: repeat codex mcp login octopus --oauth-client-registration dcr, then finish browser consent.
  • Expired consent: restart login from the client. Authorization requests are short-lived and cannot be reused.
  • Pending connection: the client has not completed its token exchange. Restart login, then revoke the abandoned pending entry.
  • Tools are missing: reconnect or restart the client so it refreshes the tool list. Confirm that the configured endpoint matches the one above.
  • No matching public skill: refine the task or browse the catalog. A successful connection does not guarantee a skill exists for every request.

Choose your next workflow

Try a code review, accessibility review, or data analysis.

Client configuration reference: Codex MCP documentation. Commands checked against local CLI help on October 25, 2026.