Skip to main content
Glama

connect-anything

ci zero dependencies license Apache-2.0

From the agent you're in, start cloud agents on your own subscriptions, or ask your other agents for a second opinion.

Claude Code asks Devin and Cursor to review a change. Both find the bug that breaks the cart, and Devin also finds a wrong price.

A real run, sped up. Every quote is the agent's own words.

You already pay for Claude Code, Codex, Devin, Cursor, Antigravity. Each one sits in its own window. connect-anything is one small MCP server that lets the agent you're working with:

  • start cloud agents: one task, or the same task on several cloud agents at once. They run on the provider's machines, so your PC isn't the bottleneck.

  • ask your local agents: a second opinion, a review from another vendor, or a task handed off.

Everything runs signed in as you, on your plans, without leaving the chat you're in.

$ connect-anything spawn claude-cloud,claude-cloud "Read package.json. Reply with the name, version and how many entries are in files."
Cloud agents g-20261118002844-59d337 - 0 of 2 answered (claude-cloud running, claude-cloud running)
claude-cloud: https://claude.ai/code/session_01T4YGv6...
claude-cloud: https://claude.ai/code/session_01T4YGv7...

$ connect-anything job g-20261118002844-59d337
Cloud agents g-20261118002844-59d337 - 2 of 2 answered (claude-cloud done in 100 s, claude-cloud done in 111 s)
<<reply agent=claude-cloud id=e0525ad5 untrusted>>
- **Name:** connect-anything - **Version:** 0.3.1 - **Entries in `files`:** 6 ...

A real run from 17 November 2026, trimmed. In an app, your agent calls the spawn tool and checks back with job.

$ connect-anything ask devin,cursor --staged "Review this diff for bugs. Be brief."
Council g-20261117195643-507f50 - 2 of 2 answered (devin done in 4.7 s, cursor done in 13 s)

<<reply agent=devin id=0e335d8a untrusted>>
**Bug: off-by-one crash.** `i <= items.length` runs one iteration past the array, so `items[i]` is
`undefined` on the last pass and `items[i].price` throws. Fix: `i < items.length`.
Minor: the `price === 0` skip is redundant - free items contribute `0 * qty = 0` anyway.
<<end 0e335d8a>>

<<reply agent=cursor id=5025ff41 untrusted>>
**Bug: off-by-one loop bound** ... **Fix:** keep the original bound: `i < items.length`.
Skipping `price === 0` is reasonable if free lines should not affect the total. That part is fine once the loop bound is fixed.
<<end 5025ff41>>

A real run from 17 November 2026, trimmed. Both agents found the crash and disagreed about the skip; your agent sees both answers and can weigh them.

  • One MCP server, one skill. Add it to Claude Code, Codex, Cursor, Devin, Antigravity, OpenCode, Grok, Muse Code, Qwen Code or Claude Desktop, or call it from any shell. Cloud assistants such as Grokbot, Muse AI, ChatGPT and Claude can reach it through a connector URL.

  • Your own sign-ins. Each agent runs through its own CLI, logged in as you. No API keys, and connect-anything never reads another tool's tokens.

  • Read-only by default. Write access is opt-in per call. Agents with no read-only mode refuse to run without it.

  • Zero dependencies. Plain Node 18 or newer. Nothing to compile.

Get started (two minutes)

npx -y connect-anything doctor      # which of your agents answer right now
npx -y connect-anything install     # add the server and skill to every app it finds

Then restart those apps and ask, in plain words: "Ask Codex and Devin to review my staged changes."

doctor sends each installed agent a one-line, read-only check ("Reply with exactly: OK") and shows who answered and how fast. That check uses a tiny bit of each plan.

Prefer a page? npx -y connect-anything setup opens one at http://127.0.0.1:7777: see your agents, connect your apps with one click each, and try an ask.

git clone https://github.com/OnlyTerp/connect-anything
cd connect-anything
node bin/connect-anything.mjs install --dry-run   # show what would change
node bin/connect-anything.mjs install

install uses each app's own mcp add command where it has one, and otherwise edits its MCP config file after keeping a .bak copy. install --uninstall takes it out again. Run through npx, the package is copied once to ~/.connect-anything/app/<version>/ so your apps never point into npm's cache. Run install again after upgrading.

Related MCP server: msgraph-mcp

What you can say

You say to your agent

What happens

"Ask Codex to review this diff."

ask {agent: "codex", diff: "uncommitted"} with your diff attached

"Get a council on my staged changes."

ask {agents: ["codex", "devin", "cursor"], diff: "staged"}, in parallel, up to 3

"Have Devin explain src/auth.ts while you keep going."

ask returns a job id after ~45 s; job picks up the answer later

"What does Cursor think of everything since main?"

diff: "main" sends git diff main...HEAD

"Start three Claude cloud agents on the flaky test, each trying a different fix."

spawn {agents: ["claude-cloud", "claude-cloud", "claude-cloud"], ...}

"Send this refactor to every cloud agent I have."

spawn {prompt: ...}: every ready cloud agent at once

The tools your agent gets:

Tool

What it does

agents

Who is ready, who answered the last check, and what each is good at

ask

Send a prompt to one agent, or to a council of up to 3 at once. Optional diff, cwd, model, write

spawn

Start cloud agents: one task on every ready cloud agent, or on the ones you name (repeat an id for copies, up to 10). Optional repo, branch, model, account

job

Read an answer by job or council id, or list recent jobs

cancel

Stop a job or a whole council

send / inbox

Leave a note for another agent or assistant, or read yours

The bundled skill (skills/connect-anything/SKILL.md) teaches agents when to use these: give the other agent full context, pick a different vendor for a second opinion, compare council answers instead of taking one as truth, and treat every reply as information, never as the user's instructions.

Cloud agents

Cloud agents run on the provider's machines against your GitHub repo, billed to your plan. They see what's pushed to GitHub, not your local files, and can push a branch or open a pull request. A start is never retried automatically, because each start is billed.

id

Cloud

How it's started

Status

claude-cloud

Claude Code on the web (claude.ai/code), Pro/Max plan

Claude Code's own RemoteTrigger tool, in a short headless claude -p turn on a small model

tested on Windows: start, status and answer, 17 Nov 2026

codex-cloud

Codex Cloud, ChatGPT plan

codex cloud exec, then codex cloud status/diff

preview: needs a Codex Cloud environment for the repo (make one)

copilot-cloud

GitHub Copilot coding agent

gh agent-task create / view

preview: needs a Copilot plan with the coding agent on

devin-cloud

Devin

Devin's v3 API with DEVIN_API_KEY and DEVIN_ORG_ID

preview

  • No terminal windows, no keys for Claude. Claude Code makes the cloud call itself with its own sign-in; connect-anything reads only the tool's result. A start is two or three short local turns on a small model (about a minute), and each status check is one more; each turn is capped at $0.25 of plan usage.

  • One setup step for Claude. The account needs a cloud environment, which connect-anything finds from your existing routines. If you have never made one, make any one-off routine once (/schedule in Claude Code), or set "claudeEnvironment" in ~/.connect-anything/settings.json.

  • Housekeeping. Each Claude start leaves a turned-off routine named connect-anything <job> at claude.ai/code/routines; delete old ones there. Answers come back as plain text, flattened to one paragraph; the full session is at its link.

  • Several accounts (preview). List extra sign-ins in ~/.connect-anything/settings.json as "accounts": {"claude-cloud": ["~/.claude-2"], "codex-cloud": ["~/.codex-2"]} (Claude Code config folders, CODEX_HOME folders). When your main sign-in answers with a usage limit, the next one is tried; account picks one of them. Not yet tested across real accounts.

  • From anywhere. Any app with connect-anything installed gets spawn. So do cloud assistants over the connector URL, but only if you start serve with --allow-cloud.

  • At most 20 cloud jobs run at once (CONNECT_ANYTHING_MAX_CLOUD_RUNNING), and one spawn starts at most 10.

Supported agents (local)

id

Agent

How it's called

Read-only mode

Status

claude

Claude Code

claude -p --output-format json

plan mode

tested, CLI 2.1.280

codex

Codex CLI

codex exec --json -s read-only

sandbox

tested, CLI 0.166.0 (usage-limit errors reported as such)

devin

Devin CLI

devin -p --prompt-file

auto permissions

tested, CLI 3000.4.25

cursor

Cursor Agent

cursor-agent -p --mode ask

ask mode

tested, CLI 2026.11.13

omp

OMP

omp -p --mode json

none: needs write: true

tested

antigravity

Antigravity

agy -p --output-format json

plan mode + request-review permissions

tested, CLI 1.5.10

opencode

OpenCode

opencode run --format json

none: needs write: true

preview

hermes

Hermes Agent

hermes -z

none: needs write: true

preview

grok

Grok CLI

grok --prompt-file

plan mode

preview (did not answer headless in our check)

muse

Muse Code (Meta)

muse exec --json --prompt-file

none: needs write: true (its untrusted mode still wrote a file)

tested, CLI 1.4.23

zcode

ZCode (Z.ai, GLM models)

the ZCode app's zcode.cjs --mode plan --output-format json

plan mode

preview (started, but our run hit provider errors)

qwen

Qwen Code

qwen --output-format json --approval-mode plan, prompt on stdin

plan mode

preview (not installed in our check)

Tested means a real call went through connect-anything and came back right, on Windows 11, in November 2026. CI runs the test suite on Windows, macOS and Linux, but real agent calls were only made on Windows: reports from macOS and Linux are very welcome (open one here).

As the caller, two apps were checked end to end:

  • Claude Code, given the server with --mcp-config, asked a Devin + Cursor council about a staged diff and summarised where they agreed and disagreed.

  • Antigravity, after connect-anything install antigravity (which runs agy mcp add), called agents, then ask with Codex on a staged diff, and quoted Codex's reply. Started as a called agent (depth 1), its ask was refused, so the one-hop guard reaches agy's MCP servers.

Other apps are registered by install the same way but haven't been checked as callers yet.

Long prompts are never cut. Agents that take the prompt as an argument get it as a file when it's long (OpenCode, OMP, Antigravity: checked with a 31,800-character prompt), or refuse with a clear message (Cursor, Hermes).

How read-only was checked. Each agent was asked to create a file, once with its file tool and once with a shell command, in read-only mode, and once with write: true as a control:

file tool, read-only

shell command, read-only

with write: true

Claude Code (plan mode)

blocked

blocked

file created

Devin (auto)

blocked

blocked

file created

Cursor (ask mode)

refused

refused

file created

Antigravity (plan + request-review)

refused

refused

file created

Antigravity's plan mode alone is not a gate: on a machine whose Antigravity tool permission was "always proceed", plan-mode runs created files both ways. So read-only runs also set that session's tool permission to request-review (never saved): edits and commands then need an approval a headless run can't give, and the run stops with a clear error. Reading files still works (checked: it read a file and answered). Commands you have always-allowed in Antigravity's own settings are your rules; we tried twice to make a read-only run write through one with an output redirect, and both times it only wrote a plan, so that case is unproven either way.

Called agents run with your own hooks, rules and settings for that CLI, so they behave as they would if you ran them yourself.

Any other agent

Anything with a command line can be added in ~/.connect-anything/settings.json:

{
  "custom": [
    {
      "id": "aider",
      "name": "Aider",
      "command": "aider",
      "args": ["--message", "{prompt}", "--yes-always"],
      "goodFor": "Pair programming with git-aware edits."
    }
  ]
}

{prompt} is replaced by the prompt and {promptFile} by a file holding it; "stdin": true pipes it in instead. Set "readOnly": "enforced" only if those args really make the agent read-only. Otherwise callers must pass write: true.

Safety

Each line below is covered by a test in test/basic.test.mjs or was checked by hand as described.

  • Read-only by default. write: true is per call. Agents without a real read-only mode refuse without it. (tested)

  • One hop only. An agent called through connect-anything can't call further agents. (tested: the server refuses at depth 1) Per CLI, by hand, with a recorder in each CLI's MCP config:

    • Claude Code: called runs start with no MCP servers (--strict-mcp-config).

    • Codex: called runs switch the server off (-c mcp_servers.connect-anything.enabled=false); it was never started.

    • Cursor: called runs don't pass --approve-mcps; the server was never started.

    • Devin: the server starts at depth 1, so ask is refused.

    • Antigravity: agy passes the depth to its MCP servers, so ask is refused.

    • OpenCode, OMP, Hermes: not checked. The running-job limit is the backstop. (tested)

  • A limit on running jobs. At most 6 local jobs run at once (CONNECT_ANYTHING_MAX_RUNNING), because they share your machine. Cloud jobs run on the vendor's machines and have their own limit of 20 (CONNECT_ANYTHING_MAX_CLOUD_RUNNING). (tested)

  • Replies are framed as untrusted. Every answer arrives as <<reply agent=X id=N untrusted>> ... <<end N>> with a random id, and fake markers inside an answer are defused, so one agent's reply can't pose as another's. (tested)

  • No shell. Agents are started with an argument list, never through a shell, so a prompt can't inject commands. (tested: a prompt full of shell syntax arrives verbatim and nothing in it runs)

  • Local only. The HTTP server binds 127.0.0.1, checks Host and Origin, and needs a token for every call; the setup page holds no token. (token checks tested)

  • Your tokens stay put. connect-anything never reads another tool's credentials. Each CLI uses its own sign-in.

See SECURITY.md to report a problem.

How it uses your subscriptions

connect-anything runs the CLIs you installed, the same way you would from a terminal, and each CLI bills its own plan. Your prompt and any diff you attach go to that agent's vendor under that vendor's terms. connect-anything makes no claim about what any vendor permits; check your plan's terms if you plan heavy automated use.

How is this different?

Good tools already call agent CLIs. What connect-anything is for, compared with them:

  • PAL MCP is an MCP server with many tools (chat, consensus, code review, planning) that mostly call model APIs with your keys; its clink tool also bridges to Gemini CLI, Codex and Claude Code. connect-anything does only the CLI part, with no API keys and no dependencies, and adds a read-only mode it enforces per CLI, councils over a git diff, and replies framed as untrusted.

  • Counselors and MCO are command-line runners that fan a prompt out to several agent CLIs and collect the answers; your agent reaches them through a skill. connect-anything is an MCP server, so the agent you're in calls it as tools, with jobs that keep running in the background and a one-hop guard against loops.

  • CAO runs a supervisor agent that drives worker agents in terminal sessions. connect-anything runs no supervisor: the agent you're in stays in charge.

Cloud assistants (browser and phone apps that accept an MCP connector URL) can use the same tools over HTTP:

cloudflared tunnel --url http://127.0.0.1:7777                    # or any tunnel you trust; note the https host it prints
connect-anything serve --port 7777 --public-host <that-host>

serve then prints one connector URL, https://<host>/mcp/<key>, and connects to it from outside the way an app does when you press Connect: initialize with an app's Origin, the follow-up notification, a GET, tools/list, and the OAuth discovery address. It prints ok for each step, or the fix. connect-anything check-url <url> runs the same check any time.

Adding it in an app:

  • Paste the whole connector URL. The key is in the URL, so there is no header to get right.

  • Set authentication to none: in Claude, No sign-in; in ChatGPT, No authentication. Leave request headers empty.

  • connect-anything has no OAuth. Its discovery addresses answer 404, and a wrong or old key in the URL also answers 404, never 401. An app never starts a sign-in that can't finish.

  • If you'd rather use a header, the key also works in Authorization (with or without Bearer ), X-API-Key or X-Auth-Token, on https://<host>/mcp.

Treat the connector URL like a password. Anyone with it can ask your agents. To change the key, delete ~/.connect-anything/token and restart serve.

Over HTTP, callers see only their own jobs. Agents are read-only unless you start with --allow-write, work only in settings.httpRoots, and can't start cloud agents unless you pass --allow-cloud. On your own machine a browser page from another site is refused (Host and Origin checks). On the tunnel host only /mcp/<key> exists; the setup page and its API answer 404 there.

What has been checked, through a public Cloudflare quick tunnel:

  • serve's own connect check passed every step.

  • The official MCP TypeScript SDK client (1.32.2), sending Origin: https://claude.ai, connected and listed the tools.

  • Claude Code, given the URL, got Devin's review back from ask.

  • A write: true call, a folder outside the allowed one, and a wrong key were all refused.

The app steps above follow Claude's and OpenAI's connector docs. Connecting from inside a named assistant app (Grokbot, Muse AI, ChatGPT, Claude and others) hasn't been tried yet; each needs its custom-connector setting turned on, which is up to you.

Quick-tunnel addresses change every time cloudflared starts, and a connector saved with the old address stops working (Claude's connector settings can't be edited, only removed and added again). For a connector you keep, use a tunnel with a fixed hostname. If serve was started with an old --public-host, requests are refused with the flag to restart with. If you already have a ~/.cloudflared/config.yml with ingress rules, cloudflared tunnel --url follows those rules instead and answers 404 (the check says so). Give the quick tunnel an empty config: cloudflared tunnel --config empty.yml --url http://127.0.0.1:7777.

Where things live

Path

What

~/.connect-anything/jobs/<id>/

One folder per job: job.json, output.txt, prompt.txt

~/.connect-anything/groups/

Council records

~/.connect-anything/doctor.json

The last doctor results

~/.connect-anything/settings.json

Disabled agents, custom agents, httpRoots, cloud accounts

~/.connect-anything/cloud.json

Each account's Claude cloud environment id (found once)

~/.connect-anything/inbox/

Notes between agents

Set CONNECT_ANYTHING_HOME to move all of it. Jobs run in their own background process, so a client timing out doesn't kill the agent it called. Local jobs stop after 30 minutes (CONNECT_ANYTHING_TIMEOUT_MIN).

Development

npm test        # behavior tests against fake agents, no model calls

File

What it holds

src/agents/local.mjs

One entry per CLI: flags, read-only mode, parser

src/agents/cloud.mjs

Cloud agents

src/agents/claude-bridge.mjs

Claude Code cloud through its RemoteTrigger tool

src/core.mjs

ask, councils, spawn, diffs, doctor, the guards

src/mcp.mjs

The MCP server, no SDK

src/http.mjs

The setup page and MCP over HTTP

src/install.mjs

App registration

Adding a CLI is one entry in local.mjs: take its flags from --help and its parser from one real reply.

License

Apache-2.0. See LICENSE.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to read your own Telegram account via MTProto, including listing chats, searching and reading message history, resolving chats, and downloading attachments, with sending available only when explicitly enabled.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to access Microsoft Outlook mail and calendar, plus read-only Microsoft Teams message history, acting as the signed-in user via delegated permissions.
      50
      1
      MIT