This project provides a Model Context Protocol (MCP) server for NATS, enabling AI models and applications to interact with NATS messaging systems
Most team communication work still happens through a UI a human drives. MCP Nats MCP server moves it into the conversation instead. This project provides a Model Context Protocol (MCP) server for NATS, enabling AI models and applications to interact with NATS messaging systems through a standardized interface. It exposes a comprehensive set of tools for interacting.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The server publishes 1 tool. What each one is for:
Prerequisites — The Prerequisites tool exposed by this serverConfiguration is passed through the environment: NATS_URL, NATS_SYS_CREDS, NATS_A_CREDS, NATS_NO_AUTHENTICATION, NATS_USER, NATS_PASSWORD. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Nats's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by sinadarbouy; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
**Cursor** (`mcpServers`):
```json
{
"mcpServers": {
"nats": {
"env": {
"NATS_URL": "nats://localhost:4222",
"NATS_SYS_CREDS": "<base64 of SYS account creds>",
"NATS_A_CREDS": "<base64 of A account creds>"
},
"url": "http://localhost:8000/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| NATS_URL | Endpoint or connection string the server talks to. | Yes |
| NATS_SYS_CREDS | Configuration value read at startup. | Optional |
| NATS_A_CREDS | Configuration value read at startup. | Optional |
| NATS_NO_AUTHENTICATION | Configuration value read at startup. | Optional |
| NATS_USER | Configuration value read at startup. | Optional |
| NATS_PASSWORD | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.