Skip to content

MCP quickstart for agents

Server: aetelier-mcp · Transport: Streamable HTTP at https://aetelier.xyz/mcp, or stdio · Full reference: Connect · Tools · Examples

This is the short path. For the capability map, preconditions, error table, and canonical identifiers, read Aetelier for agents; for per-client config and every tool's parameters, follow the reference links above.

Connect

Register the aetelier-mcp server with your MCP client. The minimum is your API key from the webapp (Settings → Security) and one of:

  • The hosted endpoint https://aetelier.xyz/mcp, with the key sent as Authorization: Bearer <key> on every request.
  • The local aetelier-mcp binary from the latest release, launched with the key as AETELIER_API_KEY.

Per-client config files (Claude Desktop, Claude Code, Cursor, VS Code) and the full field map are in Connect a client.

Operate

The tool reference covers seven domains — platform, collectors, deploy-prep, colocation, governance, fit-and-serve, and Clarion — with full parameters and example results. The rules that keep a run correct:

  • Call platform_health first; act only against a reachable platform.
  • deploy_collector is bring-your-own: it registers the service and mints an agent JWT, and the caller runs the agent container with that JWT. Confirm data with collector_health.
  • Collectors and fits draw prepaid units. A collector draws data units once per UTC day; a fit draws compute units only when it converges. Read the fit price with fit_pricing before fit_hawkes.
  • A 402 is a refusal, not a charge. If units are short, report the shortfall to the human and do not retry unchanged. Top-ups are not open yet (status), and the MCP server has no balance or top-up tool yet.
  • Backend failures return as data — {"ok": false, "error": "..."}, plus code and docs_url when the backend sends them — not protocol errors. Branch on code (the error-code index catalogs all of them), or on error when there is none, and adapt in the same loop. Reading a 402 sorts every 402.

Worked examples show these as full ask → tool-sequence → result flows, including recovering a non-converged fit.