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
your connection link
The app runs on the internet
https://cws-314e2d28ca.wireconn1.workers.dev/mcpThe app runs on your computer
https://cws-314e2d28ca.hq.abuz8ai.com/mcpNot 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.
- Install Node.js (version 18 or newer). One time only.
- Copy an agent key: Agent keys → Reveal → Copy.
- 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
Step by step, app by app
Open Claude → Add custom connector (pre-filled)
- Click the button above (or in Claude go to Customize → Connectors → Add → Custom → Web).
- Name: ConsoleAI. URL: your connection link.
- Authentication: OAuth. Click Add, then Connect. Sign in with your owner Google account and approve "Member". It lands on the claude agent.
- Team/Enterprise plans: an Owner adds it first in Organization settings → Connectors; then you connect it from Customize → Connectors.
For developers: sign in with a key
No-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 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.
- Go to Plugins → the + button → Add custom MCP server.
- Name: ConsoleAI. Under Connection paste your connection link.
- Authentication: OAuth. Sign in with your owner Google account and approve. It lands on the chatgpt agent.
- Tick "I understand and want to continue" → Create as a plugin → install it. In a chat, type @ and pick ConsoleAI.
- Older workspaces: Settings → Apps → Create → endpoint + OAuth → Scan Tools → Create.
- Dots (the ChatGPT agent agent) counts toward this dot too.
Source: help.openai.com/en/articles/12584461-connecting-custom-mcp-servers-in-chatgpt
- 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).
- Gemini CLI: copy the gemini agent key from Agent keys (Reveal → Copy).
- Run the command below, or paste the JSON into ~/.gemini/settings.json.
- 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
- Click the button above (web), or tap + → Connectors → + Add connector. On iOS/Android: Settings → Connectors.
- Choose New Connector → Custom, and paste your connection link.
- Finish sign-in: sign in with your owner Google account and approve. It lands on the grok agent.
- Grok Business: console.x.ai → Grok Business → Connectors → + Add Connector → Other.
- 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
- Manus has no browser sign-in for custom MCP, so it uses the cue agent key.
- Copy the cue key from Agent keys (Reveal → Copy).
- 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.
- Server name: ConsoleAI. Transport: HTTP. Server URL: your connection link.
For developers: sign in with a key
Add 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.
- In Muse: Settings → Connectors → Add custom connector → paste the URL → sign in (OAuth). Works on web, iOS, Android and WhatsApp.
- 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".
- 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/
- Copy the agentteams key from Agent keys (Reveal → Copy).
- In AgentTeams open your agent → Tools tab → under Custom choose MCP Server.
- Name: ConsoleAI. URL: your connection link. Token / API key: the key (sent as a bearer token).
- Connect, switch on the ConsoleAI tools you want, and Save.
- 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.
- Copy the hermes key from Agent keys (Reveal → Copy).
- Add the block below to ~/.hermes/config.yaml on your computer and restart Hermes.
- To sign in instead of using a key, replace headers with auth: oauth.
- 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
- Control UI: Settings → MCP → Configured servers → Add server.
- Name: consoleai. Transport: Streamable HTTP. URL: your connection link. Click Add server.
- 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.
- Or sign in with OAuth instead of a key: run the two CLI lines at the bottom and approve in the browser.
- 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 consoleaiSource: docs.openclaw.ai/tools/mcp · docs.openclaw.ai/cli/mcp/transports
- Instinct publishes no custom-MCP setup page. The instinct agent already gets real calls today with its agent key.
For developers: sign in with a key
If 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.
- In Kylon open the member profile → Connections tab → add a connection (remote MCP server).
- Endpoint (Streamable HTTP): your connection link.
For developers: sign in with a key
Auth: 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
For developers
VS Code, Copilot, Docker and other tools that use a key
- Open /connectors → GitHub → "Connect via Composio" (managed OAuth, no app of your own). Or paste a read-only fine-grained token there.
- 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.
- Open /connectors → Hugging Face → "Connect via Composio" (managed OAuth), or paste a read token (hf_…) from huggingface.co/settings/tokens.
- 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
- Put the JSON below in .vscode/mcp.json (one project) or run "MCP: Open User Configuration" (all projects).
- 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.
- To sign in instead: delete the headers and inputs lines; VS Code runs OAuth and the agent becomes copilot.
- 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
- Needs Docker Desktop with MCP Toolkit on (Settings → Beta features / MCP Toolkit). Save the YAML below as consoleai.yaml.
- Store the docker key from /owner as a Docker secret: docker mcp secret set consoleai.token=<key>.
- 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.
- 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 consoleaiSource: 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
For agents without a browser: OpenClaw, Hermes, AgentTeams and other CLI agents. Change the name at the end to the agent you are connecting.
- Run one line on the machine where the agent lives (Mac/Linux, or Windows PowerShell).
- It prints a link and a short code like
BCDF-GHJK. - Open the link on your phone, sign in with your owner Google account, check the code matches, tap Approve.
- The script saves the agent's token (never shown) to
~/.consoleai/<seat>.mcp.json; add--config path/to/mcp.jsonto 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.