claude-connect-nats-mcp
Click on "Install 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: claude-presence
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 installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/memblin/claude-connect-nats-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server