Other clients

Octopus is a standard remote MCP server over Streamable HTTP:

https://mcp.octopus-brain.com/mcp

Any client that supports remote servers can connect — with OAuth when it supports the MCP authorization flow, otherwise with a personal key sent as Authorization: Bearer osk_ext_…. Generate keys on octopus-brain.com/connect.

VS Code

Add Octopus to .vscode/mcp.json (this workspace) or to your user MCP configuration. With a key, let VS Code ask for it once and store it securely:

{
  "servers": {
    "octopus": {
      "type": "http",
      "url": "https://mcp.octopus-brain.com/mcp",
      "headers": { "Authorization": "Bearer ${input:octopus-key}" }
    }
  },
  "inputs": [
    { "type": "promptString", "id": "octopus-key", "description": "Octopus personal key", "password": true }
  ]
}

Without the headers block, VS Code offers the OAuth sign-in instead.

Apps that only run local servers

Some apps can only start local (stdio) MCP servers. Use the open-source mcp-remote bridge, which needs Node.js:

{
  "mcpServers": {
    "octopus": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.octopus-brain.com/mcp", "--header", "Authorization:${OCTOPUS_AUTH}"],
      "env": { "OCTOPUS_AUTH": "Bearer osk_ext_…" }
    }
  }
}

Without the two --header arguments, mcp-remote runs the OAuth sign-in in your browser instead.

Testing with the MCP Inspector

npx @modelcontextprotocol/inspector

Choose Streamable HTTP, paste the URL, and add an Authorization header with a personal key — or use the Inspector's OAuth flow.

Good to know

• Requests are HTTPS POSTs; the older HTTP + SSE transport isn't supported.
• A connection works in one teamspace at a time — see the FAQ.
• How keys and connections are protected: Security.