Connecting tools with MCP integrations
ZephMatrix connects to AWS for cloud cost investigations and uses MCP-compatible tools for routing, collaboration, and supporting actions.
Where integrations are managed
Integrations are configured from the ZephMatrix dashboard. Start with AWS, then add the tools that help route and resolve cost findings:
- • Connect AWS with a scoped cross-account IAM role
- • Register MCP servers and collaboration tools
- • Control which agents can call which tools
- • Configure routing, inbound triggers, and outbound webhooks where needed
MCP as the primary integration surface
MCP allows tools to be declared with schemas and capabilities, so agents can call collaboration and business systems safely. ZephMatrix uses direct APIs where depth and reliability matter, such as AWS cost, inventory, tags, and metrics.
Common integration path
Start by connecting AWS so ZephMatrix can investigate spend, inventory, tags, and utilization. Then add collaboration tools through MCP or direct integrations so findings can be routed to the right owner.
- • Use AWS as the source of cost and resource evidence
- • Use Slack, Jira, GitHub, or MCP hubs for owner routing and follow-through
- • Route sensitive infrastructure changes through governed execution and approval policies
For step-by-step examples of specific integrations (email, ticketing, or custom APIs), refer to the main documentation, the Platform Capabilities page, or the integrations screens in the dashboard.