Documentation
TrustRouter MCP
TrustRouter MCP gives AI agents a structured interface to the TrustRouter control plane for onboarding, diagnostics, and guided operations.
It complements the REST API instead of replacing it. Use MCP when an AI assistant needs context and safe actions. Use REST and webhooks for production traffic and long-lived system integrations.
AI-assisted onboarding
Guide operators and partners through connection setup, validation, and route preparation without exposing raw control-plane internals.
Diagnostics and troubleshooting
Inspect system health, queues, connection events, and safe trace windows through an AI assistant.
Safe control-plane actions
Run bounded actions such as connection tests, queue inspection, route suggestions, and trace enable/disable flows.
When to use MCP vs REST
- Use REST and webhooks for production traffic, message delivery, and stable backend integrations.
- Use MCP for AI-driven workflows, guided setup, diagnostics, and support operations.
- Do not treat MCP as a high-volume runtime transport for sending messages.
Current capability set
- System health overview
- Queue diagnostics
- Billing reconciliation visibility
- Circuit breaker visibility
- Connection diagnostics and recent events
- Connection tests
- Connection create and update workflows
- Connection trace enable and disable
- Route listing and route default suggestions
Access profiles
internal-ops
For SRE, support, and internal operations assistants.
partner-onboarding
For tenant-scoped onboarding and guided partner setup workflows.
read-only-audit
For diagnostics-only workflows where no write actions should be exposed.
Request access
If you want to use TrustRouter MCP for partner onboarding, support automation, or AI-assisted control-plane workflows, contact the TrustRouter team for access and profile configuration.