How do I use MCP servers with Ergod?
An MCP server is a set of tools Ergod can call as if they were its own. /mcp registers one over streamable HTTP or as a stdio process in your sandbox container, probes what it exposes, turns it on and off, and forgets it. A session host can share a server they registered into the channel session, and the room sees its tools on the next turn; nobody can share someone else's. The other direction, other agents calling Ergod as an MCP server, is on its own page.
14 commands in one group; all of them are Discord-only today, because they act on a server. Most days you will not type any of them: @Ergod and plain English is the normal way in.
Bring your own tools - remote (HTTP) or in-container stdio MCP servers. Surfaces as native tool calls.
Show every MCP server registered to your workspace, transport, enabled state, and health.
Connect a remote MCP server over streamable-HTTP. Tools surface on your next turn.
Add a stdio MCP server that runs in your sandbox container. One-click installer for npx, uvx, etc.
Register an MCP server with multiple HTTP headers.
Probe a server and print everything it exposes - tools, resources, prompts.
Wipe ALL your MCP server registrations — irreversible.
Disconnect and forget a server. Stops in-container processes; revokes any channel-session grants.
Turn MCP on for your workspace (on by default for new tenants).
Turn MCP off. Servers stay configured; no tools exposed to the model.
Re-enable a specific server you'd previously disabled.
Disable a single server without removing its registration.