Skip to content

Explain MCP exposure in the agents README #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
asim merged 2 commits into from
Nov 1, 2026
Merged

Explain MCP exposure in the agents README #7

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
136fb6b
Document exposing agents and services through the MCP gateway
asim Nov 1, 2026
98a9139
Show automatic MCP discovery as the default
asim Nov 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,35 @@ micro chat
stops them. DevOps and Monitor currently inspect systemd units, which
`micro run` does not create. For a Linux server installation, see [deploy](deploy).

## MCP

Expose running agents and services to an MCP client through Go Micro's gateway.
With `micro run` running, start the gateway in another terminal on the same host:

```sh
micro gateway --mcp-address 127.0.0.1:3000
```

Add a **Streamable HTTP** MCP server in your client with this URL:

```text
http://127.0.0.1:3000/mcp
```

The gateway automatically exposes discovered service endpoints as tools.
The client lists and calls them without configuring each tool individually.
The gateway and agents must use the same registry; the default is local mDNS.
An MCP client only needs the gateway connection, not registry access.

For remote access, put the gateway behind HTTPS, enable `--auth` with
`MICRO_AUTH_TOKEN`, and configure the client to send that bearer token. Use the
public HTTPS URL ending in `/mcp`, rather than the loopback URL above.

To expose only a subset, optionally repeat `--mcp-tool <tool-name>`.
The default includes write endpoints such as Release's dispatch operation.
MCP calls do not inherit chat approval; restrict exposed tools before giving
clients access to deployment actions.

## Development

```sh
Expand Down
Loading