# Amplify MCP server

Source: https://glimind.com/server/mcp-registry%2Fis.amplify%2Famplify
Registry id: `mcp-registry/is.amplify/amplify`
Status: live (checked 2026-11-22T17:09:15.472Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 689
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "amplify-mcp-server": {
      "type": "http",
      "url": "https://app.amplify.is/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http amplify-mcp-server https://app.amplify.is/mcp
```

## Tools (19)

- `confirm_action`: Run a spending action (create_project, create_build, edit_project) the user confirmed: pass the confirmToken it returned. Each token runs once, within 10 minute
- `create_build`: Same as create_project, for apps that order builds for their customers, but it answers as soon as the build has started (status building, with the projectId): p
- `create_project`: Create a project from a prompt and build it. A prompt that asks for a game ("build a game", "make a 3D shooter", "búðu til leik") is built with the Amplify 3D g
- `edit_project`: Apply a follow-up edit prompt to a project (creates a new version; an edit that changes nothing is free). Spends credits (depends on `tier`, default standard). 
- `get_account`: Who this connection acts as: user, active org, plan, credit balance, and the scopes granted.
- `get_build_status`: Where a project's build is: queued, building, ready or failed, with its version and preview/public address when ready.
- `get_connection`: This connection: which projects it may use (all, one project, or only the ones it created), its daily credit cap, what it spent today (UTC) and what is left.
- `get_credits`: Credit balance and the 50 most recent ledger entries (a connection limited to some projects gets the balance and its own cap only).
- `get_project`: One project: status, kind, files, model, published address, preview path.
- `get_publish_check`: Run the publish gate's checks for a project without publishing (what would block it).
- `get_result`: The delivery of a finished build: a claim link (single use, 30 days; calling again returns the same open link) that copies the build into the recipient's own Am
- `get_usage_today`: Today's model usage against the daily cap.
- `list_approvals`: The org's approval queue (pending by default): publish requests and other actions waiting for a human. Approving happens in the app, not here.
- `list_custom_domains`: Custom domains attached to a project and their status (read-only; adding or removing domains is done in the app).
- `list_projects`: List the org's projects (id, name, kind, status, timestamps), newest first. A connection limited to some projects sees only those.
- `list_published_sites`: Projects that are published, with their public slug and address.
- `list_versions`: Version history of a project.
- `publish_project`: Ask to publish a project at a public address. This goes through the publish gate: it queues an approval that the owner confirms in the app (Approvals tab); noth
- `read_project_file`: Read one text file of a project (relative path such as index.html or app.js).

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
