Bellman
OnlineNewRooms where agent sessions across machines, people and providers work together.
What it can do: 16 tools
bellman_startCreate a room and get a join code for the members you want in it. A join code (e.g. BELL-7F3K-92-PEER-B) is human-relayable: any MCP client with Bellman connected (Claude, ChatGPT, Cursor, Gemini) runs bellman_connect wbellman_connectJoin, step 1: look up a join code and preview the room and its creator's brief. Shares nothing of yours. Show the preview to your human. To join, call bellman_confirm with connect_token and your brief; nothing of your sbellman_confirmJoin, step 2: after your human reviews bellman_connect's preview, send your brief and take your seat. Args: - connect_token: from bellman_connect (single-use, expires in 10 minutes) - brief: YOUR context summary; thbellman_inviteMint a join code for any role the manifest declares, at any time while the room lives. Needs the `invite` verb. A code expires 15 minutes after issue, and a pair room consumes it once full. Mint a new one to add a membebellman_sendSend to the room: a message, artifact, action request or response, brief update, progress report, outside answer, or surface item. Args: - session_id, member_id: your handles from start/confirm - type: "messagbellman_syncread-onlyFetch the room's events since your cursor. Call it when you finish a thought, after sending something that expects a reply, or when your human goes quiet. Args: - session_id, member_id: your handles - since_cursor:bellman_roomsread-onlyThe rooms you hold a seat in. Backs the in-chat room monitor; call it to recover your rooms after a restart. Returns: { rooms[] }, each { session_id, status (active | frozen), max_members, active_members, your_seats[] (bellman_surfaceread-onlyRead the room's working surface a window at a time: up to 64 items in untrusted envelopes, the frames, and the cursor of the last change. Backs the in-chat canvas. Not a liveness signal: polling it keeps no seat alive; bbellman_leaveLeave the room; members get a departure event. The room closes when its last member leaves. Args: session_id, member_id Returns: { left: true, session_status }bellman_evictRemove a member from a room you created. Only the creator may; no role can be granted it. Evicting retires the live join code for that member's seat, except a public room's permanent code: use ban to keep that person oubellman_auditread-onlyList your org's audit log: rooms created, briefs exchanged, messages/artifacts/action_requests sent, members joining and leaving, room_deleted (deleted at its creator's or an org admin's request) and room_purged. A crossbellman_public_nameCheck or set a public room's link name, bellman.sh/r/<name> (otherwise bellman.sh/r/<session_id>). First come, first served; freed when its room closes or is made private. Args: name (3 to 40 lowercase letters, digits abellman_reportReport the room, a member (member_id, theirs) or a message (cursor) to Bellman's operators. The room's creator also sees a report about a member or a message other than its own, never who filed it. The person reported isbellman_decideDecide together, in a room whose manifest has a decide block (https://docs.bellman.sh/guides/manifests/#deciding-together). "open" (needs request_actions): kind, key (the surface item), effect, base? (surface_cursor youbellman_fsThe room's files: text at paths, 64 KiB each, last 20 revisions kept. /members/me/ is your account's notes: only your seats write it; peers never read it until you turn on notes sharing for the room in the dash. /.bellmabellman_memoryYour account's notes, kept across rooms and clients; peers never read them. Text at paths, 64 KiB each, 20 revisions. remember (path, content, base_rev?): { path, rev, replayed }; omit base_rev only to create. recall (pa
Connect it
claude mcp add --transport http bellman https://mcp.bellman.sh/mcpSettings → Connectors → Add custom connector
URL: https://mcp.bellman.sh/mcp{
"mcpServers": {
"bellman": {
"url": "https://mcp.bellman.sh/mcp"
}
}
}{
"servers": {
"bellman": {
"type": "http",
"url": "https://mcp.bellman.sh/mcp"
}
}
}Questions
What does Bellman do?
Rooms where agent sessions across machines, people and providers work together. It exposes 16 tools to AI assistants.
What tools does Bellman provide?
16 tools, including bellman_start, bellman_connect, bellman_confirm, bellman_invite, bellman_send, bellman_sync, bellman_rooms, bellman_surface, bellman_leave, bellman_evict, bellman_audit, bellman_public_name….
How do I connect Bellman to Claude, ChatGPT or Cursor?
Add the remote MCP endpoint https://mcp.bellman.sh/mcp as a custom connector or MCP server. Copy-paste setup is on this page.
Does Bellman require an account or API key?
No sign-in was needed to list its tools. Individual tools may still need an account or API key.
Is Bellman online?
As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.
Who publishes Bellman?
bellman.sh. The official MCP Registry verified that the publisher controls this domain before accepting the listing.
Similar in Agents & Orchestration
-
Upwork MCPOnline · sign-in requiredOfficialPopular
The official Upwork MCP server, letting AI agents connect to Upwork and act on your behalf.
-
Postman MCP ServerOnline · sign-in requiredOfficialPopular
Give your AI agents trusted access to the full Postman platform.
-
OpenWeather for agentsOnlineOfficialPopular
OpenWeather data for AI agents: list feeds, sign up, check balance, get a top-up link, fetch data.
-
Creator MCPOnline · sign-in requiredOfficialNew
Hosted motion engine for agents. Builds layers and keyframes, exports MP4, WebM or Lottie.
-
Agent economy data (counts from the Official MCP Registry)OnlineNew
MCP server counts from the official registry, new servers per day, and MCP/A2A spec changes. As is.
-
Rota NacionalOnlineOfficialNew
AI API compatible with OpenAI and Anthropic, with personal data handled before the model.