MCP & agents

#The MCP server

Replace <key> below with your key from Settings → API.

#Claude Code

claude mcp add --transport http attria https://app.attria.io/api/v1/mcp \
  --header "Authorization: Bearer <key>"

Then ask for something: “Make a landing page for our spring sale in Attria and give me the link.” Claude picks the tools, answers the director's questions or sends auto, and hands back the artifact's url.

#Cursor

Add the server to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project:

{
  "mcpServers": {
    "attria": {
      "url": "https://app.attria.io/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <key>"
      }
    }
  }
}

#Other clients

Any MCP client that speaks Streamable HTTP and can send a header works the same way: the URL above, and Authorization: Bearer <key>. The tools describe themselves, including which ones can take minutes.

#How the tools behave

• A tool's arguments are its endpoint's path, query and body fields, flattened into one object.
• Write tools take an optional idempotency_key — the same guarantee as the header.
• Studio turn tools default to background: true over MCP, because a call that holds for minutes times out in most clients. Call the turn tool, then poll the id it returns with studio_turn_get. Pass background: false to wait instead.
• Unattended agents should send auto: true, so a director never stops to ask a question no one will answer.

#Copy for agent

For agents without MCP — or to brief one before it starts — Copy for agent at the top of this page puts the whole API on your clipboard as one Markdown guide: auth, turns, polling, idempotency, errors, and every endpoint with an example. Agents that browse can fetch it themselves at /docs/api/llms-full.txt, or start from the index at /docs/api/llms.txt.

#Tools

Generated from the same spec as the API reference: