For agents

Agents are first-class here.

Agents connect over MCP, deploy with verification, and get repair context when apps fail.

Start here

Connect

claude mcp add --transport http fastdeploy https://platform.fastdeploy.app/api/mcp --header "Authorization: Bearer <token>"

<token> is a bearer token from your platform login; treat it like a password — don't commit it or bake it into screenshots or config you share.

MCP reference

The tools

Deploy & manage 6 tools
deploy_appCreate, deploy, and wait for healthy; returns logs on failure.
update_appAtomically redeploy code with verification.
delete_appRemove an app and its runtime resources.
get_appGet one app and its current state.
list_appsList apps available to the current account.
validate_codeRun AST and security checks without deploying.
Functions 4 tools
create_functionCreate a handle(event) function with an optional cron schedule.
update_functionUpdate function code or its schedule.
run_functionRun a function on demand.
get_function_executionsRead recent function run results.
Observe & repair 4 tools
get_logsRead recent application logs.
get_attentionList open incidents that need attention.
get_fix_briefGet code, evidence, and guidance for a failing app.
sdk_docsCheck runner packages and platform SDK modules.

From signal to working code

The repair loop

01

Notice

get_attention returns the open incident.

See the payload
{
  "app_id": "app-fn-7c2",
  "kind": "function_failures",
  "status": "open",
  "consecutive_failures": 5,
  "last_error": {
    "type": "ModuleNotFoundError",
    "traceback": "ModuleNotFoundError: No module named 'jsonn'"
  }
}

02

Brief

get_fix_brief collects code, evidence, and guidance.

See the payload
{
  "app_id": "app-fn-7c2",
  "files": {"handler.py": "import jsonn\n..."},
  "recent_failures": [
    {"status": "error", "error": "No module named 'jsonn'"}
  ],
  "guidance": [
    "An import isn't available in the runner.",
    "Check sdk_docs before changing dependencies."
  ]
}

03

Correct

Call update_function with the corrected code.

See the payload
{
  "app_id": "app-fn-7c2",
  "code": "import json\n\ndef handle(event):\n    return {\"body\": json.dumps(event)}",
  "schedule": "*/15 * * * *",
  "verify": true,
  "result": {
    "status": "updated"
  }
}

04

Return

The next run succeeds, and the incident resolves.

See the payload
{
  "app_id": "app-fn-7c2",
  "incident": {
    "kind": "function_failures",
    "status": "resolved"
  },
  "executions": [
    {"status": "success"}
  ]
}

Failure thresholds

Incident rules

An incident opens after 3 consecutive failed scheduled runs or health checks. It resolves on the first success. Fix briefs never modify code — an agent (or you) does.

Give your agent a quieter path to production.

Connect once. Deploy, verify, and return to failures with the useful context already gathered.