agentes.chat
One MCP by URL in Settings, on a public https address.
Add runelay to agentes.chat, self-hosted or Cloud, with your endpoint and an agent key (rnl_…).
agentes.chat accepts only a public https:// address for a connector. A private IP, localhost or a Tailscale-only name (100.x) is refused, with no switch to allow it. If runelay runs only on your tailnet, turn on Tailscale Funnel or give it a domain.
tailscale funnel --bg http://127.0.0.1:4312Then, in the MCPs section of Settings, add a server by URL and paste the key in the API key field. agentes.chat sends it as a bearer token.
Server URL https://runelay.example.com/v1/mcp
API key rnl_...agentes.chat tests the server when you add it. runelay shows as Active with 9 tools, and every agent in the workspace can use it; sensitive tools still ask a person for approval. No restart.
A self-hosted agentes.chat on the same server as runelay resolves the tailnet name to the private address and refuses it. Point its container at a public DNS (dns: [1.1.1.1] in a docker-compose.override.yml) so it reaches runelay through the Funnel.
No CLI shortcut yet: runelay connect does not write agentes.chat.
Step by step: runelay.com/guides/agentes-chat.