Remote MCP is experimental, unsupported and off by default. Use at your own risk.
Rows record whose grant acted: attribution, not authentication. A caller's seat that was created but never launched is served instead of refused. A caller granted through a grant service hands work to its granted team, never to a caller seat, and cannot attach tags that hide text from a person asked about it. For advanced remote setups, rig mcp serve --http --grant-service <url> checks each request's key with an external grant service, with nothing cached. --oauth-resource and --oauth-issuer add OAuth protected-resource discovery (RFC 9728) and standard sign-in challenges; the key and grant still decide what a caller may do. This is experimental and unsupported. It's off by default. Nothing in OpenRig listens on the internet unless you set it up yourself. You serve rig mcp serve --http, put it behind your own TLS tunnel or proxy, and issue a token. Doing that is like opening a port in your firewall. Anyone with the URL and a valid token can act as that member within its grant. Treat the token like a password, give the member the narrowest grant, and revoke it when you're done (rig mcp token revoke <name>). We don't support, and take no responsibility for, an OpenRig reachable from the internet, just as with running OpenRig itself on the open internet. Use at your own risk.
- Release
- OpenRig 0.7.4 release notes