Skip to main content
The Model Context Protocol (MCP) is how external AI agents discover and call Cyberun’s runtime: list workflows, submit tasks, watch progress, fetch results, cancel runs. Cyberun ships a cloud MCP server that speaks the official Streamable HTTP transport and works with every mainstream MCP client out of the box.

Cloud MCP

Hosted at core.cyberun.cloud/api/v1/mcp. 15 tools that wrap the team’s full runtime API. Authenticated with an integration key (sk-). Use from anywhere.

AI skill

One shell command (npx skills add cyberun-cloud/skills) teaches Claude Code, Cursor, Windsurf, Codex CLI, or any other skill-aware agent how to use Cyberun without you re-explaining.

API reference

The HTTP surface that MCP wraps. Useful when you need an operation MCP doesn’t expose, or when you’re not in an MCP-aware environment.

​
When to use MCP

​
Standards compliance

The server implements the official Model Context Protocol specification. It speaks Streamable HTTP as defined in MCP 2025-03-26 and later (including the MCP-Protocol-Version header required by 2025-06-18+), uses Bearer-token authentication on Authorization: Bearer …, surfaces tool errors as CallToolResult with isError: true, and emits notifications/progress for long-running tools. Verified-compatible clients:
  • Claude Code (CLI and IDE)
  • Claude Desktop
  • Cursor
  • Windsurf
  • VS Code 1.101 and later (native HTTP MCP)
  • Codex CLI
  • Any client that supports the legacy stdio path via mcp-remote

​
What you can do over MCP

The common workflow operations are:
  • List workflows the team has published.
  • Submit a workflow with parameters; receive a task_id.
  • Stream task progress until terminal state, with MCP notifications/progress events along the way.
  • Fetch the result — output metadata plus signed download URLs.
  • Cancel a task that hasn’t finished yet.
  • List the team’s agents and see which are idle.
The Cloud MCP additionally exposes container-service inspection, file presign for workflow inputs, and workflow lookup by slug. For the complete tool inventory with input schemas, see Cloud MCP → Tools.

​
Authentication, briefly

  • Cloud MCP: Authorization: Bearer sk-... — an integration credential issued from Cyberun Cloud’s access settings. The team scope is baked into the key; no X-Team-ID header is required for MCP requests.
Full auth details are on the server’s page.

​
Next

Connect Cloud MCP

Endpoint, auth, every tool, per-client install snippets.

Install the AI skill

Teach the agent the API + MCP layout in one command.

MCP spec

Background reading on the protocol itself.