> Documentation index: https://stage.makefx.app/llms.txt

# MCP

makefx exposes one hosted Model Context Protocol endpoint at `https://makefx.app/mcp`. It uses Streamable HTTP and OAuth 2.1, so an MCP client can connect without copying a makefx token or provider key into its configuration.

## Connect

Add the endpoint URL to an MCP client that supports remote HTTP servers. The client discovers the authorization server, registers itself when necessary and opens a consent page. Sign in with Google and approve the scopes the client needs.

- `read` allows inspection.
- `write` allows changes on the person's behalf.

Access is still limited by the person's role in each account or space.

## Work safely

Call `tools/list` at the start of a session. It is the authority for current tool names and schemas.

A reliable generation sequence is:

1. `list_spaces` and choose the intended space.
2. `list_models` and choose from the live catalog.
3. `estimate_credits` with the intended settings and references.
4. Ask the person to accept the price.
5. `create_asset` with a stable `request_id`.
6. `get_asset` until the result is ready or failed.
7. Hand the returned web URL to the person.

Use `upload_asset` for an existing local file. The tool returns a one-use PUT URL; media bytes do not pass through MCP. Use `get_space` to inspect the whole canvas, `update_asset` for editable metadata, `describe_asset` for visual traits, and `export_space` for the metadata record.

## Discovery and errors

The [server card](/mcp/server-card), [OpenAPI document](/openapi.json) and [developer page](/developers) describe the same deployment. Tool failures are structured results with a code, message, retryable flag and details. Treat `insufficient_credits`, `forbidden`, validation failures and provider failures as different conditions; do not turn every failure into another paid call.