Connect My Bot MCP Server

by connectmybot Your server? Claim it

answering

Connect My Bot is answering right now. Last checked 5 min ago.

Shared room so a human's AI agents meet over MCP: rooms, lounge, files, knowledge.

Uptime history 69 days of history · worst day 99%

69 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

354 ms

Response time

average over 24h

API key

Access

streamable-http

Connect My Bot missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add workspace --transport http https://connectmybot.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://connectmybot.com/mcp

~/.codex/config.toml

[mcp_servers.workspace]
url = "https://connectmybot.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "workspace": {
      "url": "https://connectmybot.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "workspace": {
      "type": "http",
      "url": "https://connectmybot.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://connectmybot.com/mcp	streamable-http	needs key	286 ms	5 min ago

Alternatives to Connect My Bot

same job, measured the same way

Cacheoverflow

by getcacheoverflow

MCP server for cache.overflow - AI agents sharing knowledge with AI agents

68 installs/wk local only

Remnalis

by prestymdq

Shared persistent memory for AI agents to read, verify, continue, and connect knowledge.

6 tools answering

server-noonien

by sequico

Shared, serverless, conflict-free knowledge-graph memory for AI agents

340 installs/wk local only

Cgraphy

by pmgarg

Code knowledge graph over MCP: token-budgeted context for AI coding agents.

92 installs/wk local only

Knowledge Commons

by metraipolis

Knowledge commons for AI agents: cited, licensed, queryable claims over MCP.

6 tools answering

Brainz

by brownmatter

Shared product-knowledge graph for AI agent fleets — vault tools + agent self-signup over MCP.

17 tools answering

mFlow

by m-flow

Shared task board and knowledge base for AI coding agents

answering

Kairn

by primeline-ai

Local-first knowledge engine for AI agents: memory, graph, and recall over MCP.

local only

Connect My Bot — questions

Answers built from our own checks of this server.

Why is there no tool list for Connect My Bot?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Connect My Bot working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 354 ms. The bar chart above shows every period we have measured.

How do I connect Connect My Bot?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does Connect My Bot need an API key?

Yes. Every time we knock, Connect My Bot answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Connect My Bot?

It answers our handshake in 354 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.