Frequently Asked Questions

Product Information: Sedai MCP Integration

What is Sedai MCP and how does it work?

Sedai MCP (Model Context Protocol) is an integration layer that allows you to bring Sedai's autonomous cloud optimization and AI assistant capabilities directly into your own agents and tools. With MCP, your agents can access the same features as Sedai's AI assistant (Sed) without custom integration or separate logins. MCP exposes Sedai's optimization, cost savings, and resource management tools to any MCP-compliant client, enabling agent-to-agent workflows and eliminating the need for platform-specific dashboards. Note: MCP requires your agent or tool to support the MCP protocol; legacy or non-compliant tools may not be compatible.

What capabilities does Sedai MCP provide to my agents?

Sedai MCP provides your agents with the same tools and skills available in Sedai's AI assistant, including the ability to pull optimization status, retrieve savings data, surface cost and performance opportunities, and initiate actions such as adjusting settings or managing resource groups. As Sedai's assistant (Sed) gains new features, they become available through MCP automatically, with no feature lag or separate roadmap. Note: Some advanced features may require specific agent support for full functionality; check your agent's documentation for compatibility.

Which tools and platforms are compatible with Sedai MCP?

Sedai MCP works with any MCP-compliant client, including Claude Desktop, Claude Code, Cursor, Windsurf, VS Code (GitHub Copilot), ChatGPT / Codex, OpenCode, and Cline. You can also add Sedai as an MCP tool in your own internal agent tooling. Note: Compatibility depends on MCP support in your chosen tool; tools without MCP support will not be able to integrate with Sedai MCP.

How does Sedai MCP differ from traditional custom integrations?

Traditional custom integrations require building and maintaining bespoke connections for each platform, which can be time-consuming and difficult to scale. Sedai MCP eliminates this overhead by providing a standardized protocol that any MCP-compliant agent can use to access Sedai's capabilities. This approach enables agent-to-agent workflows and ensures that your agents always have access to the latest Sedai features without waiting for separate integration updates. Note: Organizations with highly specialized or legacy systems may still require custom integration work if MCP is not supported.

Is there any feature gap between Sedai MCP and Sedai's AI assistant (Sed)?

No, there is no feature gap between Sedai MCP and Sedai's AI assistant (Sed). Both share the same underlying capability layer, so any new skills or features added to Sed are immediately available through MCP as well. There is no separate roadmap or lag in feature availability. Note: Some agent interfaces may not expose all features if they do not support the full MCP protocol.

Features & Capabilities

What actions can my agents perform through Sedai MCP?

Through Sedai MCP, your agents can pull optimization status, retrieve cost savings data, surface performance and resource opportunities, and initiate actions such as adjusting settings or managing resource groups. These capabilities are the same as those available in Sedai's AI assistant, enabling your agents to participate in cloud optimization workflows without manual dashboard interaction. Note: The range of actions available depends on the agent's implementation of the MCP protocol.

How does Sedai MCP support agent-to-agent workflows?

Sedai MCP provides a common interface that allows agents to communicate and coordinate actions with Sedai as part of larger, automated workflows. This enables day-to-day operations to move through agents talking to other agents and systems, rather than being limited by platform-specific UIs. Note: Effective agent-to-agent workflows require all participating agents to support the MCP protocol.

Does Sedai MCP require custom integration or separate logins?

No, Sedai MCP does not require custom integration or separate logins. You simply add Sedai as a tool your agent already knows how to use, provided the agent supports the MCP protocol. This reduces integration overhead and streamlines adoption. Note: Agents without MCP support will require additional integration work.

Technical Requirements & Implementation

How long does it take to implement Sedai MCP?

Initial setup for Sedai integrations can be completed in as little as 15 minutes using agentless or agent-based deployment, depending on your environment and agent support for MCP. For more advanced use cases, such as AI Agent Optimization, implementation typically takes two to three weeks. Note: Implementation time may vary based on your agent's MCP compatibility and internal workflow complexity.

Where can I find technical documentation for Sedai MCP?

Comprehensive onboarding resources and technical documentation for Sedai, including guides for integrating with agents and optimizing environments, are available at https://docs.sedai.io/get-started. These resources cover Kubernetes, Databricks, GPU optimization, and more. Note: Documentation for MCP-specific integration may require coordination with your agent vendor or internal development team.

Security & Compliance

What security and compliance certifications does Sedai MCP support?

Sedai is SOC 2 certified, demonstrating adherence to stringent security and data protection standards. This certification applies to all Sedai platform integrations, including MCP. For more details, visit the Sedai Security page. Note: Detailed limitations not publicly documented; ask sales for specifics regarding MCP-specific compliance scenarios.

Pricing & Plans

How is Sedai MCP priced?

Sedai's pricing is resource-based and determined by the resources optimized and the value delivered. For Kubernetes environments, tailored pricing is available. All costs are transparently outlined on the Sedai pricing page, with no hidden fees. Discounts from connected cloud billing accounts are factored into cost and savings calculations. Note: For MCP-specific pricing or custom use cases, contact Sedai sales for details. Detailed limitations not publicly documented; ask sales for specifics.

Use Cases & Benefits

Who should use Sedai MCP?

Sedai MCP is designed for organizations and teams that use agent-based workflows and want to integrate autonomous cloud optimization directly into their existing tools. It is especially valuable for IT/cloud operations, SREs, platform engineers, and technology leaders seeking to automate cloud management, reduce operational toil, and align cost and performance objectives. Note: Teams without MCP-compliant agents may not benefit from MCP integration; consider Sedai's other platform options.

What are the main benefits of using Sedai MCP?

Sedai MCP enables your agents to access autonomous optimization, cost savings, and performance improvements without manual dashboard interaction. Key benefits include up to 50% reduction in cloud costs, up to 75% reduction in latency, and up to 6X productivity gains for engineering teams. MCP also eliminates custom integration overhead and ensures your agents always have access to the latest Sedai features. Note: Actual benefits depend on agent compatibility and the scope of integration; not all environments may realize the maximum stated improvements.

Limitations & Considerations

What are the limitations of Sedai MCP?

Sedai MCP requires your agents or tools to support the MCP protocol; legacy or non-compliant tools may not be compatible. Some advanced features may require specific agent support for full functionality. Detailed limitations are not publicly documented; contact Sedai sales for specifics regarding your environment. Best fit for teams already using MCP-compliant agents; teams with highly specialized or legacy systems may need custom integration work.

Live Webinar: Autonomous FinOps in the Age of AI

Sign Up
Sedai Logo

Bring Sedai Into the Agents You Already Use

Sedai's MCP (Model Context Protocol) integration puts the same capabilities available in Sed — Sedai's AI assistant — directly into your own agents. No custom integration, no separate login: just add Sedai as a tool your agent already knows how to use.

Sedai MCP Architecture.png
Background

If Your Agents Can't Reach Sedai, They're Missing Part of the Picture

Knowledge about your cloud and AI infrastructure is scattered — cost data in one tool, optimization opportunities in another, resource configuration somewhere else. Increasingly, teams are pulling that picture together with their own agents. Sedai should be one of the tools those agents can reach.

Custom integrations don't scale.

Wiring your own agent or internal tooling into another platform's API usually means building and maintaining a bespoke integration for each one.

Agent-to-agent workflows need a common interface.

As more of the day-to-day work moves through agents talking to other agents and systems, a platform that's only reachable through its own UI becomes a dead end in that workflow.

A platform's capabilities shouldn't lag behind its own product.

Some integrations are narrow, bolt-on developer utilities — separate from, and slower to update than, the vendor's own in-product experience.

Key Capabilities

Sedai's MCP server exposes the same tools and skills that power Sed, so your own agents get the same capabilities Sedai's assistant has — nothing held back.

Pull Information From Sedai

Ask your agent to check optimization status, pull savings data, or surface opportunities from Sedai — no dashboard required.

Take Action Through Sedai

Ask your agent to kick off the same actions available in Sed — adjusting settings, managing resource groups — as part of a larger workflow.

Plug Into What You Already Run

Add Sedai as an MCP tool in Claude Code, Copilot, or your own internal agent tooling, alongside whatever else is already in your stack.

Grow Automatically With Sed

Sed and MCP share one underlying capability layer. As Sed gains new skills, they become available through MCP too, with no separate roadmap or lag.

One Capability Layer, Two Surfaces

Everything available through Sedai's MCP integration is also available in Sed, Sedai's AI assistant — and vice versa. There's no separate roadmap and no feature gap between the two; they're built from the same underlying tools and skills.

Sed example chat

Works With Your Tools

Sedai's MCP integration works with any MCP-compliant client, including:

Claude Desktop

Claude Code

Cursor

Windsurf

VS Code (GitHub Copilot)

ChatGPT / Codex

OpenCode

Cline

See Sedai's MCP Integration in Your Own Workflow