Amplify runs a Model Context Protocol (MCP) server so AI assistants such as ChatGPT, Claude and Cursor can list your projects, check build status, export code, and (with your permission) build and publish new projects.
Add this endpoint to any MCP client that supports MCP authorization. The client registers itself, opens an Amplify sign-in page, and you approve the access you want. No key to copy.
https://amplify.is/api/mcpTransport: Streamable HTTP. Sign-in: OAuth 2.1 with PKCE (S256) and dynamic client registration. Discovery: /.well-known/oauth-protected-resource, /.well-known/oauth-authorization-server and /.well-known/mcp.json.
| Scope | Allows | Tools |
|---|---|---|
amplify:read | See your own projects, build status and download exports. Cannot change or delete anything and cannot spend credits. | amplify_list_projects, amplify_get_project, amplify_get_build_status, amplify_export_project, amplify_read_export_file, amplify_list_templates, amplify_get_project_status |
amplify:build | Start a build from a text description and publish it. Builds use your Studio credits. A build and a publish each ask for confirmation first (a preview with the cost, then confirm). | amplify_create_project, amplify_publish_project |
For clients without OAuth support, create a personal key under Connections in the studio and send it as Authorization: Bearer amp_…. Keys are shown once, only a SHA-256 hash is stored, and you can revoke a key at any time. Keys have the same two scopes, chosen when you create the key.
Every published game and site also gets its own public endpoint at https://amplify.is/share/<slug>/mcp, described by /share/<slug>/mcp.json. Public read tools need no sign-in. Owners can turn each endpoint off and choose its tools. All endpoints are listed in /.well-known/mcp.json.