get_build_status — Amplify MCP Tool Read-only

get_build_status (get build status) is one of 19 tools on the Amplify MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call get_build_status from your client

Claude Code Amplify get_build_status run in your project directory
Claude Desktop Amplify get_build_status ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Amplify get_build_status ~/.cursor/mcp.json
VS Code Amplify get_build_status .vscode/mcp.json
Zed Amplify get_build_status ~/.config/zed/settings.json
Windsurf Amplify get_build_status ~/.codeium/windsurf/mcp_config.json
Cline Amplify get_build_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Amplify get_build_status ~/.gemini/settings.json
Grok Amplify get_build_status .mcp.json (in your project root)
ChatGPT Amplify get_build_status Settings → Connectors → Advanced → Developer mode
Claude.ai Amplify get_build_status Settings → Connectors → Add custom connector
LangChain Amplify get_build_status pip install langchain-mcp-adapters

Fastest route

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

Other tools on this server

get_account
list_projects
get_project
read_project_file
list_versions
get_publish_check
list_published_sites
list_approvals
get_credits
get_connection
get_usage_today
create_project
create_build
edit_project
confirm_action
get_result
publish_project
list_custom_domains

This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

Amplify MCP server