Skip to main content
Codeezly

MCP Server

Build, edit, and publish Codeezly apps from ChatGPT, Claude, Cursor, or VS Code. Codeezly runs a remote MCP server, so any Model Context Protocol client can drive your account.

What it is

The Model Context Protocol (MCP) is an open standard that lets AI assistants call external tools. Codeezly exposes an MCP server that wraps the same build, edit, and publish actions you use in the app — so you can create a full app straight from a chat with your favorite assistant.

  • docs.mcp.whatItIs.points.endpoint
  • Authentication: connect with a Codeezly access token sent as an HTTP Bearer token.
  • Scope: every tool runs as you and only touches apps you own.
  • Asynchronous: generation and edits run as background jobs — you submit a request, then poll until it finishes.

Connecting a client

Point any MCP client at the Codeezly endpoint and supply your access token as a Bearer token. A typical client configuration looks like this:

{
  "mcpServers": {
    "codeezly": {
      "url": "https://frontend-production-10bb.up.railway.app/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_CODEEZLY_ACCESS_TOKEN>"
      }
    }
  }
}

Replace YOUR_CODEEZLY_ACCESS_TOKEN with a token from your Codeezly account. The token carries your identity, so keep it secret.

The tools

The server advertises eight tools:

  • codeezly_list_apps — list the apps in your account.
  • codeezly_read_app — read an app's files, or a single file by path.
  • codeezly_account_insight — a summary of your account and usage.
  • codeezly_create_app — create a new app from a prompt. Returns a project id and a job id.
  • codeezly_edit_app — apply a follow-up instruction to an existing app.
  • codeezly_publish_app — publish an app, optionally on a chosen subdomain.
  • codeezly_revert_app — roll an app back to its last successful checkpoint.
  • codeezly_get_job_status — poll a create or edit job until it completes.

How generation works over MCP

Because building takes longer than a single request, codeezly_create_app and codeezly_edit_app return right away with a job to track:

  1. Call codeezly_create_app or codeezly_edit_app and note the returned job id.
  2. Call codeezly_get_job_status with that job id until the status is succeeded.
  3. When it succeeds, use codeezly_read_app, codeezly_edit_app, or codeezly_publish_app on the returned project.

For example:

// 1. Submit a build job
codeezly_create_app({
  prompt: "A habit tracker with weekly streaks and a dark theme"
})
// => { "project_id": "proj_abc123", "job_id": "job_xyz789" }

// 2. Poll until the job finishes
codeezly_get_job_status({ job_id: "job_xyz789" })
// => { "status": "running" }
// ...poll again...
// => { "status": "succeeded", "project_id": "proj_abc123" }

// 3. Read the result, then edit or publish
codeezly_read_app({ project_id: "proj_abc123" })
codeezly_edit_app({
  project_id: "proj_abc123",
  instruction: "Add a settings page with a reminder toggle"
})
codeezly_publish_app({ project_id: "proj_abc123", subdomain: "my-habits" })

Made a change you don't like? codeezly_revert_app rolls the app back to its last working version.

Billing & ownership

  • Usage is metered against your Codeezly credits, exactly like building in the app.
  • There is no free generation path over MCP — the same quotas and limits apply.
  • You can only read, edit, publish, or revert apps you own.
  • Every tool call runs as the user who owns the access token, so the permissions and limits match your Codeezly account.