Documentation MCP Server Overview

MCP Server Overview

CloudCode exposes a Model Context Protocol (MCP) server as a backend function, allowing external AI agents and automation tools to interact with your projects programmatically via a standard JSON-RPC 2.0 interface.

What you can do with MCP
  • Create, read, update, search, and delete projects and files, with version history and restore
  • Manage workspaces, environment variables, custom domain records, tags, and your profile
  • Read chat history, post messages, stream an external agent's output into a project chat, or run the CloudCode AI agent
  • Read and record deployment history, activity logs, terminal sessions, project memories, error history, and session changelogs
  • Submit and manage Auto-Fix jobs that push fixes to GitHub, watch CI, and verify the live deploy
Note
The MCP server follows the open Model Context Protocol standard and works with MCP clients that support remote HTTP servers with a custom Authorization header — including Claude Code, Cursor, and Claude Desktop (via the mcp-remote bridge). See Usage examples for configs.
Endpoint
text
POST https://tytvylihloorkrcgkzok.supabase.co/functions/v1/mcp-server

Requests are JSON-RPC 2.0 messages sent by HTTP POST; each response is a single application/json body (no SSE stream, no session ID). Batch requests (a JSON array) are supported and answered with an array. The server identifies itself as cloudcode-mcp 2.0.0 and reports protocol version 2024-11-05.

Implemented methods: initialize, notifications/initialized, ping, tools/list, tools/call, resources/list, resources/read, prompts/list, and prompts/get. Anything else returns error -32601. Resource subscriptions and list-changed notifications are not supported.

Errors
  • Missing or invalid token: HTTP 401 with JSON-RPC error -32000 "Unauthorized"
  • Unknown method: error -32601. Unknown resource URI or prompt name: error -32602
  • Tool failures (database errors, not found, validation) are returned as a normal result with isError: true and a text message — not as JSON-RPC errors
  • Unhandled server errors: HTTP 500 with error -32603