🧰 NATS MCP toolbox
About
This is a collection of cli tools to expose MCP tools via NATS microservices. It can be used either standalone (exposing existing MCP Servers via NATS) or as library in Go to expose functions as tools.
Details
- Author
- hofer
- Downloads
- 175
- Categories
- Developer Tools, Other
Jump to
- Exposes MCP tools via NATS microservices
- Can be used standalone or as a Go library
- Supports exposing existing MCP servers over NATS
- Provides a command to list available tools
- Works with local agents through MCP configuration
- Uses NATS_URL environment variable for default URLs
Run ./nats-mcp tool --url <nats-server> --command <mcp-server-binary> [args] to expose an existing MCP server via NATS. Use ./nats-mcp client list --url <nats-server> to list available tools. Configure a local agent by adding ./nats-mcp server --url <nats-server> to your MCP config. The NATS_URL environment variable sets the default NATS server URL.
🧰 NATS MCP toolbox
This is a collection of cli tools to expose MCP tools via NATS microservices. It can be used either standalone (exposing
local/existing MCP Servers via NATS) or as library in Go to expose functionality as tools.
> [!WARNING]
> 🚨 🚧 This tool is under active development 🚧 🚨
>
> This tool is very much work in progress. While the tools should all work, expect almost
> daily breaking changes.
Usage
Exposing an existing MCP Server via NATS:
./nats-mcp tool --url "nats://localhost:4222" --command="./whatever-mcp-server" arg1 arg2
To check what MCP tools are exposed via NATS use the following command:
./nats-mcp client list --url "nats://localhost:4222"
To then actually use the tool with your local agent, add the following command to your MCP config:
./nats-mcp server --url "nats://localhost:4222"
Given the --url parameter is used for allmost all arguments, the NATS_URL environment variable is used as a default.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
