Server
Talk to Cycloid’s Internal Development Portal from your agent to provision stacks and platform workflows.
Overview
io.cycloid.mcp/server is a MCP server for the Build phase that connects your agent to the Cycloid.io Internal Development Portal over authenticated streamable HTTP.
What is this MCP server?
- Remote MCP at https://mcp.cycloid.io/mcp with required X-CY-API-KEY and X-CY-ORG headers
- Open-source server repo: github.com/cycloidio/cycloid-mcp-server (version 1.0.1)
- Interact with Cycloid.io Internal Development Portal and platform entities via streamable-http
- Tenant-scoped via organization canonical name header
- Fits platform-engineering teams exposing golden paths to AI-assisted developers
- Server version 1.0.1; schema dated 2025-09-29
- 2 required headers: X-CY-API-KEY (secret), X-CY-ORG
- Source repository: github.com/cycloidio/cycloid-mcp-server
What problem does it solve?
Your golden-path infra lives in Cycloid’s portal but your coding agent cannot trigger stacks or platform actions without you clicking through forms.
Who is it for?
Small teams on Cycloid.io who want MCP access to their IDP while building and shipping on standardized platform templates.
Skip if: Solo hackers with no Cycloid tenant who only need a single VPS and no internal developer platform.
What do I get? / Deliverables
After you add API key and org headers, the agent can drive Cycloid portal and platform operations alongside your application code.
- Authenticated Cycloid remote MCP registration
- Agent-driven portal and platform interactions on your tenant
- Faster alignment between app repos and org Cycloid catalogs
Recommended MCP Servers
Journey fit
IDP integrations land on Build when you connect the product repo to org-standard infra catalogs and pipelines. Integrations captures MCP bridges into external platform APIs like Cycloid, distinct from writing app frontend or unit tests.
How it compares
Cycloid IDP platform MCP, not a generic GitHub Actions skill or local-only Terraform generator.
Common Questions / FAQ
Who is io.cycloid.mcp/server for?
Developers on Cycloid.io organizations who use an internal development portal and want Claude Code, Cursor, or Codex to invoke platform APIs via MCP.
When should I use io.cycloid.mcp/server?
Use it while integrating app work with Cycloid stacks, catalogs, or platform workflows during Build, and when operating those resources through the same portal.
How do I add io.cycloid.mcp/server to my agent?
Register https://mcp.cycloid.io/mcp as streamable-http and supply X-CY-API-KEY (secret) and X-CY-ORG (tenant canonical name) headers per Cycloid’s MCP guide.