publishLABSCO SUMMARY
It can create and delete streams, not just read them.
stream_delete and kv_delete are in the same toolset as stream_list, so whatever you point NATS_URL at is fully writable by the model. Point it at a development cluster while you are learning what the assistant does with it. kv_history is the tool people forget exists — it turns the KV store into an audit trail rather than a set of current values.
What it is
A NATS client exposed over stdio. It covers core messaging, JetStream stream lifecycle and the key-value store, so an assistant can inspect and drive a message bus directly.
What you get
- 17 tools in four groups
- Core:
publishandrequestfor fire-and-forget and request-reply - Streams:
stream_list,stream_info,stream_create,stream_delete,stream_publish,stream_fetch,stream_consumer_create - KV:
kv_create_bucket,kv_list_buckets,kv_get,kv_put,kv_delete,kv_list_keys,kv_history - Server:
server_infofor diagnostics
Requirements
The npm package @daanrongen/nats-mcp, version 1.1.4, launched with bunx @daanrongen/nats-mcp; Claude Code takes claude mcp add nats. One required variable, NATS_URL, pointing at your server — for example nats://localhost:4222. Nothing else to configure.
Setup effort
One command — bunx @daanrongen/nats-mcp
USE CASES
01
Checking whether a stream is actually receiving messages
List the streams, read one's info, and fetch recent messages from it.
02
Testing a request-reply service by hand
Send a request on the subject and read the reply, without writing a client.
03
Inspecting or fixing a config value in the KV store
Read a key, see how it changed over time, and put a new value.
04
Standing up a stream for a new subject
Create the stream and a consumer for it in the same conversation.
17 tools
Listed in project docs. Your client may show a different list.
requeststream_liststream_infostream_createstream_deletestream_publishstream_fetchstream_consumer_createkv_create_bucketkv_list_bucketskv_getkv_putkv_deletekv_list_keyskv_historyserver_infoBEFORE YOU INSTALL
What to know first
Tools you get
17 tools named in the project's documentation.
Requires
- bunx on PATH
- NATS_URL — your NATS server URL (e.g. nats://localhost:4222)
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
bunx @daanrongen/nats-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"nats": {
"type": "stdio",
"command": "bunx",
"args": [
"@daanrongen/nats-mcp"
],
"env": {
"NATS_URL": "nats://localhost:4222"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add nats -e NATS_URL=nats://localhost:4222 -- bunx @daanrongen/nats-mcp
