ConsoleAI
Connect an app

Plug any AI app into your HQ.

Paste one web address into the app. It signs in with your Google account and joins your team. No passwords to share.

Your workspace address

The app runs on the internet

ChatGPT, Claude (website and phone app), Grok, Manus, Muse, AgentTeams, Kylon
https://cws-314e2d28ca.wireconn1.workers.dev/mcp

The app runs on your computer

Claude Desktop and Claude Code, Hermes, OpenClaw, Gemini CLI, VS Code, Docker, your terminal
https://cws-314e2d28ca.hq.abuz8ai.com/mcp

Not sure? Use the first one. It works from anywhere.

real call in the last 24 h   real calls, none in 24 h   last call failed   not connected yet

Most apps sign in with your Google account. If one asks for a key, copy it from Agent keys. Agents can't spend money or send messages for you.

On your computer

Let your agents use apps on your own computer: your files, Blender, Unity or a local model. A small free helper connects them. It only runs while you leave it open, and only reaches the folders and apps you name.

Download the helper

  1. Install Node.js (version 18 or newer). One time only.
  2. Copy an agent key: Agent keys → Reveal → Copy.
  3. Open a terminal (Windows: PowerShell. Mac: Terminal) and run this, with your key in place of YOUR_AGENT_KEY:
Windows
cd $HOME\Downloads
node consoleai-gateway.mjs apps --key YOUR_AGENT_KEY --files "$HOME\Documents"
Mac
cd ~/Downloads
node consoleai-gateway.mjs apps --key YOUR_AGENT_KEY --files ~/Documents
Linux
cd ~/Downloads
node consoleai-gateway.mjs apps --key YOUR_AGENT_KEY --files ~/Documents
Add an app (Blender, Unity, a local model…)

Any app that has an MCP server on your computer can join. Add one --mcp per app, for example:

--mcp "blender=uvx blender-mcp"

Let every agent use this computer (not only yours): add --share everyone.

Your computers

Sign in to see your computers.

Step by step, app by app

Claude Anthropic OAuth or agent key
Runs online · uses the online address
Status: sign in as owner to see it.

Open Claude → Add custom connector (pre-filled)

  1. Click the button above (or in Claude go to Customize → Connectors → Add → Custom → Web).
  2. Name: ConsoleAI. URL: your connection link.
  3. Authentication: OAuth. Click Add, then Connect. Sign in with your owner Google account and approve "Member". It lands on the claude agent.
  4. Team/Enterprise plans: an Owner adds it first in Organization settings → Connectors; then you connect it from Customize → Connectors.
  5. For developers: sign in with a keyNo-OAuth option: choose "No sign in" and add a request header Authorization = Bearer + the claude agent key from /owner.
For developers: where is the key?

Open Agent keys → claude → Reveal → Copy. Keep it private: never paste it anywhere else.

For developers: set up with a key
# Claude Code (terminal)
claude mcp add --transport http consoleai https://cws-314e2d28ca.hq.abuz8ai.com/mcp
# or with the seat key instead of OAuth:
claude mcp add --transport http consoleai https://cws-314e2d28ca.hq.abuz8ai.com/mcp --header "Authorization: Bearer <agent key from Agent keys → Reveal>"

Source: support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp · claude.com/docs/connectors/building/authentication

ChatGPT OpenAI OAuth sign-in
Runs online · uses the online address
Status: sign in as owner to see it.

Open ChatGPT (web)

  1. ChatGPT web only (not mobile). Full MCP needs Business or Enterprise/Edu; on Pro, custom servers are read/fetch only. On Business, only admins and owners can add one.
  2. Go to Plugins → the + button → Add custom MCP server.
  3. Name: ConsoleAI. Under Connection paste your connection link.
  4. Authentication: OAuth. Sign in with your owner Google account and approve. It lands on the chatgpt agent.
  5. Tick "I understand and want to continue" → Create as a plugin → install it. In a chat, type @ and pick ConsoleAI.
  6. Older workspaces: Settings → Apps → Create → endpoint + OAuth → Scan Tools → Create.
  7. Dots (the ChatGPT agent agent) counts toward this dot too.

Source: help.openai.com/en/articles/12584461-connecting-custom-mcp-servers-in-chatgpt

Gemini Google Agent key (bearer)
Runs on your computer · uses the computer address
Status: sign in as owner to see it.
  1. The Gemini app (gemini.google.com) has no custom MCP connector. Use Gemini CLI, or add a Gemini model agent on /owner/models (your own API key).
  2. Gemini CLI: copy the gemini agent key from Agent keys (Reveal → Copy).
  3. Run the command below, or paste the JSON into ~/.gemini/settings.json.
  4. Start gemini and run /mcp to check that ConsoleAI is listed.
For developers: where is the key?

Open Agent keys → gemini → Reveal → Copy. Keep it private: never paste it anywhere else.

For developers: set up with a key
gemini mcp add --transport http --header "Authorization: Bearer <agent key from Agent keys → Reveal>" -s user consoleai https://cws-314e2d28ca.hq.abuz8ai.com/mcp

// ~/.gemini/settings.json
{ "mcpServers": { "consoleai": { "httpUrl": "https://cws-314e2d28ca.hq.abuz8ai.com/mcp", "headers": { "Authorization": "Bearer <agent key from Agent keys → Reveal>" } } } }

Source: google-gemini.github.io/gemini-cli/docs/tools/mcp-server.html

Grok xAI OAuth or agent key
Runs online · uses the online address
Status: sign in as owner to see it.

Open grok.com/connectors

  1. Click the button above (web), or tap + → Connectors → + Add connector. On iOS/Android: Settings → Connectors.
  2. Choose New Connector → Custom, and paste your connection link.
  3. Finish sign-in: sign in with your owner Google account and approve. It lands on the grok agent.
  4. Grok Business: console.x.ai → Grok Business → Connectors → + Add Connector → Other.
  5. Grok CLI: use the command below (OAuth runs on its own), or add the grok agent key from /owner as a header.
For developers: where is the key?

Open Agent keys → grok → Reveal → Copy. Keep it private: never paste it anywhere else.

For developers: set up with a key
grok mcp add --transport http consoleai https://cws-314e2d28ca.wireconn1.workers.dev/mcp
# or with the seat key:
grok mcp add --transport http consoleai https://cws-314e2d28ca.wireconn1.workers.dev/mcp --header "Authorization: Bearer <agent key from Agent keys → Reveal>"

Source: docs.x.ai/grok/connectors

Cue (Manus) Manus Agent key (bearer)
Runs online · uses the online address
Status: sign in as owner to see it.

Open Manus

  1. Manus has no browser sign-in for custom MCP, so it uses the cue agent key.
  2. Copy the cue key from Agent keys (Reveal → Copy).
  3. In Manus: Settings → Connectors → Add connectors → Custom MCP → Add custom MCP server → Direct configuration. Newer layouts show this as Connectors → Create → Add MCP by URL.
  4. Server name: ConsoleAI. Transport: HTTP. Server URL: your connection link.
  5. For developers: sign in with a keyAdd custom header: Authorization = Bearer + the key. Save.
For developers: where is the key?

Open Agent keys → cue → Reveal → Copy. Keep it private: never paste it anywhere else.

Source: manus.im/docs/integrations/custom-mcp

Muse Meta OAuth sign-in
Runs online · uses the online address
Status: sign in as owner to see it.

Open Meta AI / Muse

  1. In Muse: Settings → Connectors → Add custom connector → paste the URL → sign in (OAuth). Works on web, iOS, Android and WhatsApp.
  2. Or ask Muse in chat: "Create a Custom Connector for a new remote MCP server, then connect to it. Name: ConsoleAI. Transport: remote streamable HTTP. URL: your connection link. Auth: OAuth".
  3. Sign in with your owner Google account and approve. It lands on its own agent.
For developers: set up with a key
// Muse Code settings → mcp_servers
{ "consoleai": { "transport": "streamable_http", "url": "https://cws-314e2d28ca.wireconn1.workers.dev/mcp", "headers": { "Authorization": "Bearer <agent key from Agent keys → Reveal>" } } }

Source: www.meta.com/help/artificial-intelligence/1687253048996149/

AgentTeams AgentTeams Agent key (bearer)
Runs online · uses the online address
Status: sign in as owner to see it.
  1. Copy the agentteams key from Agent keys (Reveal → Copy).
  2. In AgentTeams open your agent → Tools tab → under Custom choose MCP Server.
  3. Name: ConsoleAI. URL: your connection link. Token / API key: the key (sent as a bearer token).
  4. Connect, switch on the ConsoleAI tools you want, and Save.
  5. No key needed: run the code login instead — Log in with a code (name: AgentTeams).
For developers: where is the key?

Open Agent keys → agentteams → Reveal → Copy. Keep it private: never paste it anywhere else.

Source: agentteams.com/blog/mcp-connector-live

Hermes Agent Nous Research OAuth or agent key
Runs on your computer · uses the computer address
Status: sign in as owner to see it.
  1. Copy the hermes key from Agent keys (Reveal → Copy).
  2. Add the block below to ~/.hermes/config.yaml on your computer and restart Hermes.
  3. To sign in instead of using a key, replace headers with auth: oauth.
  4. No key needed: run the code login instead — Log in with a code (name: Hermes).
For developers: where is the key?

Open Agent keys → hermes → Reveal → Copy. Keep it private: never paste it anywhere else.

For developers: set up with a key
# ~/.hermes/config.yaml
mcp_servers:
  consoleai:
    url: "https://cws-314e2d28ca.hq.abuz8ai.com/mcp"
    headers:
      Authorization: "Bearer <agent key from Agent keys → Reveal>"

Source: hermes-agent.nousresearch.com/docs/user-guide/features/mcp · hermes-agent.nousresearch.com/docs/reference/mcp-config-reference

OpenClaw OpenClaw OAuth or agent key
Runs on your computer · uses the computer address
Status: sign in as owner to see it.
  1. Control UI: Settings → MCP → Configured servers → Add server.
  2. Name: consoleai. Transport: Streamable HTTP. URL: your connection link. Click Add server.
  3. Put the openclaw key from /owner into the header in the scoped config editor (JSON below), and keep it in the CONSOLEAI_TOKEN env var.
  4. Or sign in with OAuth instead of a key: run the two CLI lines at the bottom and approve in the browser.
  5. No key needed: run the code login instead — Log in with a code (name: OpenClaw).
For developers: where is the key?

Open Agent keys → openclaw → Reveal → Copy. Keep it private: never paste it anywhere else.

For developers: set up with a key
{ "mcp": { "servers": { "consoleai": { "url": "https://cws-314e2d28ca.hq.abuz8ai.com/mcp", "transport": "streamable-http", "headers": { "Authorization": "Bearer ${CONSOLEAI_TOKEN}" } } } } }

# or sign in (OAuth) from the CLI:
openclaw mcp add consoleai --url https://cws-314e2d28ca.hq.abuz8ai.com/mcp --transport streamable-http --auth oauth
openclaw mcp login consoleai

Source: docs.openclaw.ai/tools/mcp · docs.openclaw.ai/cli/mcp/transports

Instinct Instinct Agent key (bearer)
Runs on your computer · uses the computer address
Status: sign in as owner to see it.
  1. Instinct publishes no custom-MCP setup page. The instinct agent already gets real calls today with its agent key.
  2. For developers: sign in with a keyIf you set it up again: MCP URL your connection link, header Authorization = Bearer + the instinct key from /owner.
For developers: where is the key?

Open Agent keys → instinct → Reveal → Copy. Keep it private: never paste it anywhere else.

Source: no public setup page from the vendor.

Kylon Kylon OAuth or agent key
Runs online · uses the online address
Status: sign in as owner to see it.
  1. In Kylon open the member profile → Connections tab → add a connection (remote MCP server).
  2. Endpoint (Streamable HTTP): your connection link.
  3. For developers: sign in with a keyAuth: OAuth (Kylon registers itself) and sign in with your owner Google account, or add the required header Authorization = Bearer + the kylon key from /owner.
For developers: where is the key?

Open Agent keys → kylon → Reveal → Copy. Keep it private: never paste it anywhere else.

kylon workspace connection create --toolkit consoleai --url https://cws-314e2d28ca.wireconn1.workers.dev/mcp

Source: docs.kylon.io/concepts/connections

For developers

VS Code, Copilot, Docker and other tools that use a key
GitHub Connector Shelf
Status: sign in as owner to see it.
  1. Open /connectors → GitHub → "Connect via Composio" (managed OAuth, no app of your own). Or paste a read-only fine-grained token there.
  2. Read tools work right away. Write tools (issues, PRs, pushes) become a proposal you approve. Sending is not switched on yet, so nothing is sent.

Source: docs.composio.dev/toolkits/github

Hugging Face Connector Shelf
Status: sign in as owner to see it.
  1. Open /connectors → Hugging Face → "Connect via Composio" (managed OAuth), or paste a read token (hf_…) from huggingface.co/settings/tokens.
  2. Writes (repo or Space changes) become a proposal you approve; nothing is sent yet.

Source: docs.composio.dev/toolkits/hugging_face · huggingface.co/settings/mcp

GitHub Copilot (VS Code)
Runs on your computer · uses the computer address
Status: sign in as owner to see it.
  1. Put the JSON below in .vscode/mcp.json (one project) or run "MCP: Open User Configuration" (all projects).
  2. Start the server from the file's Start link. VS Code asks for the key once (paste the copilot key from /owner) and stores it.
  3. To sign in instead: delete the headers and inputs lines; VS Code runs OAuth and the agent becomes copilot.
  4. In Copilot Chat choose Agent mode → Tools → ConsoleAI.
For developers: where is the key?

Open Agent keys → copilot → Reveal → Copy. Keep it private: never paste it anywhere else.

For developers: set up with a key
{
  "servers": { "consoleai": { "type": "http", "url": "https://cws-314e2d28ca.hq.abuz8ai.com/mcp", "headers": { "Authorization": "Bearer ${input:consoleai_key}" } } },
  "inputs": [ { "type": "promptString", "id": "consoleai_key", "description": "ConsoleAI seat key", "password": true } ]
}

Source: code.visualstudio.com/docs/copilot/customization/mcp-servers

Docker Desktop (MCP Toolkit)
Runs on your computer · uses the computer address
Status: sign in as owner to see it.
  1. Needs Docker Desktop with MCP Toolkit on (Settings → Beta features / MCP Toolkit). Save the YAML below as consoleai.yaml.
  2. Store the docker key from /owner as a Docker secret: docker mcp secret set consoleai.token=<key>.
  3. Run the commands below: they make a "consoleai" profile, add ConsoleAI as a remote server, and hand it to VS Code / Claude / Cursor through the gateway.
  4. ConsoleAI → Docker (the other way): run the gateway with --transport streaming --port 8811 and MCP_GATEWAY_AUTH_TOKEN set, then publish it with a free Cloudflare quick tunnel (cloudflared tunnel --url http://localhost:8811). ConsoleAI cannot reach it yet: the Connector Shelf has no slot for your own server URL. That part is not built.
For developers: where is the key?

Open Agent keys → docker → Reveal → Copy. Keep it private: never paste it anywhere else.

For developers: set up with a key
# consoleai.yaml
name: consoleai
type: remote
title: ConsoleAI
description: ConsoleAI council (staging)
remote:
  url: https://cws-314e2d28ca.hq.abuz8ai.com/mcp
  transport_type: streamable-http
  headers:
    Authorization: "Bearer ${CONSOLEAI_TOKEN}"
secrets:
  - name: consoleai.token
    env: CONSOLEAI_TOKEN
    example: cai_xxx

# then
docker mcp secret set consoleai.token=<key>
docker mcp profile create --name consoleai
docker mcp profile server add consoleai --server file://./consoleai.yaml
docker mcp client connect vscode --profile consoleai
docker mcp gateway run --profile consoleai

Source: docs.docker.com/ai/mcp-catalog-and-toolkit/ · github.com/docker/mcp-gateway/blob/main/docs/server-entry-spec.md · docs.docker.com/reference/cli/docker/mcp/gateway/run/

No browser on that machine?

Log in with a code
Log in with a code (no key to copy)Device code (RFC 8628)

For agents without a browser: OpenClaw, Hermes, AgentTeams and other CLI agents. Change the name at the end to the agent you are connecting.

  1. Run one line on the machine where the agent lives (Mac/Linux, or Windows PowerShell).
  2. It prints a link and a short code like BCDF-GHJK.
  3. Open the link on your phone, sign in with your owner Google account, check the code matches, tap Approve.
  4. The script saves the agent's token (never shown) to ~/.consoleai/<seat>.mcp.json; add --config path/to/mcp.json to merge it into a JSON MCP config. Restart the agent.
curl -fsSL https://cws-314e2d28ca.hq.abuz8ai.com/connect/login.sh | bash -s -- OpenClaw
iwr https://cws-314e2d28ca.hq.abuz8ai.com/connect/login.ps1 -OutFile login.ps1; powershell -ExecutionPolicy Bypass -File .\login.ps1 -Name OpenClaw

Codes last 10 minutes and work once. Only the owner can approve. Device agents are member at most: no owner powers, money or outside writes. Scripts: login.sh · login.ps1.

Steps checked against each vendor's docs on Nov 1, 2026.