MCP server connections
Connect Ogma to remote Model Context Protocol servers to give the support bot guild-specific tools. Each Discord server has its own connections, credentials, enabled state, and tool allowlist.
Manage connections from MCP servers in your server dashboard (same team access as Agentic tools).
What Ogma supports
Ogma connects to remote MCP servers over HTTPS:
- Streamable HTTP (recommended)
- Legacy SSE (for older MCP endpoints)
Local stdio servers are not supported — the MCP server must be reachable on the public internet (or from Ogma’s network).
For each connection, Ogma can:
- authenticate with encrypted HTTP headers;
- discover the server’s available tools;
- expose only the tools you allow;
- use allowed tools in live ticket replies and ticket playground simulations.
Connections are isolated by guild. A tool configured for one Discord server is never made available to another.
Add a connection
- Open MCP servers → New MCP server.
- Enter a name, URL, and transport (Streamable HTTP unless your provider says otherwise).
- Add authentication headers if the remote server requires them. Header values are encrypted at rest and are never shown again after save — you can leave a value blank when editing to keep the current secret.
- Click Connect and discover tools. Ogma saves the connection, connects once, and lists the tools the server exposes.
- Review the tool list. Discovered tools are selected by default — uncheck any you do not want the bot to call. Destructive or write tools should be reviewed carefully.
- Click Save allowlist to keep the connection disabled while you test, or Enable server when you are ready for live tickets.
You can configure up to ten MCP servers per guild. Names must be unique within the guild.
Safe rollout
| Configuration | Behaviour |
|---|---|
| Connection disabled | Ogma does not contact the MCP server during AI replies. |
| Enabled with no allowed tools | No MCP tools are exposed to the model. |
| Some tools allowed | Only those tools are available. |
| Discovery unavailable | Ogma continues using knowledge search and its other tools. |
| Tool call fails | The failed result is returned to the AI turn; the bot and other tools continue. |
Recommended rollout
Test allowed tools in the ticket playground before relying on them in live support. Use the Monitoring tab to watch recent calls and failures.
Edit, rotate credentials, or remove
Open a connection from the MCP servers list:
- Configuration — update URL, transport, headers, or the tool allowlist. Click Discover tools to refresh the list after the remote server changes.
- Overview — enable or disable the connection.
- Monitoring — recent tool calls, failures, and latency.
When rotating credentials, send the full header set you want to keep. Omit a header’s value to retain its current encrypted secret; omit a header entirely to remove it.
Delete a connection from the overview menu when you no longer need it.
Security considerations
Only allow tools whose authorization and side effects you understand. MCP tools do not use Ogma’s Agentic-tool staff approval queue — the allowlist is the enforcement boundary. Destructive tools should implement confirmation and access controls on the MCP server itself.
Ogma only allows HTTPS URLs that resolve to public endpoints. Outbound requests have timeouts and size limits, and a maximum number of MCP tool calls can run in one AI turn across all connections for your guild.
See Agentic tools for Ogma’s webhook-based custom tool system.