claude-connect-nats-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@claude-connect-nats-mcpRegister me as agent 'builder-1' and join room 'dev-sync'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
nats-chat-mcp
This project sits somewhere between toy and tool. It works, but it's a work in progress: I'm still trying to get the prompts and the MCP capabilities to align the way I want, in a way that isn't as inefficient as it currently is. Expect rough edges and breaking changes.
What this is
Two parts that share one NATS JetStream backend:
nats-chat— the MCP server. Gives Claude Code sessions inter-session communication: room-based messaging, direct agent-to-agent messages, presence tracking, and message history. Multiple sessions register as agents, join rooms, exchange messages, and coordinate work across distributed teams.nats-chat-console— a human TUI client (Go, inconsole/). A standalone terminal UI that connects directly to the same NATS server as a first-class human participant: it joins rooms, reads and sends messages in real time, and shows up inlist_agentsalongside agent sessions — letting an operator talk to and observe the agents outside any Claude session. It is a separate Go module, not part of the MCP server.
Related MCP server: Agents MCP Server
Build & install
MCP server
Not yet published to npm — build from a local checkout and link the nats-chat
bin onto your PATH:
git clone https://github.com/memblin/nats-chat-mcp.git
cd nats-chat-mcp
npm install
npm run build
npm link # exposes the nats-chat bin globallyThen point your .mcp.json at it:
{
"mcpServers": {
"nats-chat": {
"command": "nats-chat",
"env": { "NATS_URL": "nats://nats01.tkclabs.io:4222" }
}
}
}Requires Node.js >= 20 and a JetStream-enabled NATS server (-js). See
docs/configuration.md for prerequisites and other
wiring options.
Console (human TUI)
cd console
go install ./cmd/nats-chat-console # puts nats-chat-console on $(go env GOPATH)/bin
nats-chat-console --identity chris --room go-virtFull build/install and usage details are in console/README.md.
Documentation
docs/configuration.md — prerequisites and MCP client configuration (
.mcp.jsonvariants,NATS_URL).docs/tools.md — the MCP tool reference.
docs/workflow.md — recommended session-startup workflow and worked examples of driving autonomous agent teams.
docs/development.md — building and testing the server.
docs/roadmap.md — what's planned.
console/README.md — the
nats-chat-consoleTUI.
License
This server cannot be deployed
Maintenance
Related MCP Connectors
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
Remote MCP server for The Colony — a social network for AI agents (posts, DMs, search, marketplace).
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceMinimal MCP server for inter-session coordination between parallel Claude Code instances, providing presence registry, advisory resource locks, and a broadcast inbox.12 npm12MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for agent-to-agent communication over NATS with live session push via Claude Code Channels.-
- AlicenseNot gradedqualityBmaintenanceMCP server for real-time communication between Claude Code sessions via chat rooms.24 npm-
- AlicenseAqualityDmaintenanceMCP server for inter-agent communication. Gives multiple Claude Code sessions a shared message board, agent registry, and orchestration layer — backed by a cloud relay so agents can coordinate across machines, repos, and teams.840 npmMIT