
Amplify MCP server
Which MCP servers are Amplify's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-11-12
- Registry nameis.amplify/amplifyverified in the MCP registry
The registry name sits under amplify.is. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Staterequires sign-inchecked 2026-11-12
On 2026-11-12 the server answered and asked for a sign-in with a Amplify account (OAuth). It shows its tool list only to signed-in users, so we list none here.
Should an agent connect it
- Whether its tools do the product's job has not been judged yet.
Once connected
- create_project, create_build, edit_project, publish_project change data without a sign-in: anyone with the address can call them.
- Parameters are untyped or undescribed in 13 of 19 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
Measured daily
- INITE MCP score60 of 100answers 100 · definitions 89 · context 100 · use 0 · connects 100 · lowered until one of our scenario runs passes · lowered by the warning signs below
- Answered100% of days10 of 10 daily checks
- Median first answer319 ms
- Space in an agent's context≈ 2,263 tokensthe definitions of all its tools (19), which an agent carries on every turn
- Tool definitionsB · 89 of 100
- Typed results0 of 19 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 13 of 19
Worth a look
- Tools that change data, on a server that answers without a sign-in: create_project, create_build, edit_project, publish_project
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
get_accountdescribed by the serverWho this connection acts as: user, active org, plan, credit balance, and the scopes granted.
list_projectsseen, not called yetList the org's projects (id, name, kind, status, timestamps), newest first. A connection limited to some projects sees only those.
get_projectdescribed by the serverOne project: status, kind, files, model, published address, preview path.
read_project_filedescribed by the serverRead one text file of a project (relative path such as index.html or app.js).
list_versionsseen, not called yetVersion history of a project.
get_publish_checkdescribed by the serverRun the publish gate's checks for a project without publishing (what would block it).
list_published_sitesseen, not called yetProjects that are published, with their public slug and address.
list_approvalsseen, not called yetThe org's approval queue (pending by default): publish requests and other actions waiting for a human. Approving happens in the app, not here.
get_creditsdescribed by the serverCredit balance and the 50 most recent ledger entries (a connection limited to some projects gets the balance and its own cap only).
get_connectiondescribed by the serverThis 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_usage_todaydescribed by the serverToday's model usage against the daily cap.
create_projectchanges datadescribed by the serverCreate 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 game engine (priced as a 3D game: 60 credits on standard); anything else is a…
create_buildchanges datadescribed by the serverSame 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): poll get_build_status, then get_result for the delivery link. `idempotencyKey`…
edit_projectchanges datadescribed by the serverApply 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). Spends credits, so it is two-step: this call returns needs_confirmation with…
confirm_actionchanges datadescribed by the serverRun a spending action (create_project, create_build, edit_project) the user confirmed: pass the confirmToken it returned. Each token runs once, within 10 minutes, on this connection only.
get_build_statusdescribed by the serverWhere a project's build is: queued, building, ready or failed, with its version and preview/public address when ready.
get_resultdescribed by the serverThe 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 Amplify account, plus a preview address at once.
publish_projectchanges datadescribed by the serverAsk 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); nothing goes live until they do.
list_custom_domainsseen, not called yetCustom domains attached to a project and their status (read-only; adding or removing domains is done in the app).
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"amplify": {
"type": "http",
"url": "https://app.amplify.is/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http amplify https://app.amplify.is/mcpclaude.ai, ChatGPT and other clients: add https://app.amplify.is/mcp as a custom connector in the settings.
The first time it connects, the client opens a Amplify sign-in.
OpenAPI spec
4 paths, read 2026-11-12. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.