Agent setup

For AI agents. Aura manages a WordPress agency's hosting, Cloudflare and sites from one place, and exposes them to you through one MCP server. Follow these steps to connect and to onboard your human.

1. Add the Aura MCP server

Your human creates your token at https://app.my-aura.app/onboarding and gives it to you. Replace <YOUR_TOKEN> with it. In Claude Code:

claude mcp add --transport http aura-fleet https://app.my-aura.app/api/mcp/fleet --header "Authorization: Bearer <YOUR_TOKEN>"

Other agents — add this to the MCP configuration (for example .mcp.json):

{
  "mcpServers": {
    "aura-fleet": {
      "type": "http",
      "url": "https://app.my-aura.app/api/mcp/fleet",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

2. Follow the checklist

Call aura__onboarding_status and do its nextStep. Repeat until it reports complete: true. The required steps are a hosting provider and one WordPress site connected with SiteAgent; Cloudflare is optional but recommended.

3. Rules

• Credentials never pass through you. Never ask your human to paste an API key, password or token into the conversation. The tools return a link; your human opens it and enters the key in Aura.
• Ask before you open a browser. Give your human the link and ask whether to open it.
• Changes to a live site still go through Aura's approval queue — your human approves them.

Onboarding tools

• aura__onboarding_status — The checklist for your client: each step's done/required state and the next step. Call it first, and again after each step.
• aura__request_provider_connection — Returns a one-time link (60 minutes) where the human enters the hosting provider's or Cloudflare's API key in Aura. Never takes credentials.
• aura__get_connection_request — Polls a request: pending, connected, failed or expired.
• aura__request_site_connection — Returns the steps for the human to connect one WordPress site with the SiteAgent plugin, and a request id to poll.