MCP setup

Connect Arenza to a client that supports remote MCP. Sign in and authorize through OAuth 2.0 (authorization code + PKCE); no API Key is needed.

Server URL: https://mcp.arenza.ai/mcp.

Claude Code

Run in your terminal:

claude mcp add --transport http arenza https://mcp.arenza.ai/mcp

Cursor

Add this to Cursor's MCP configuration:

{
  "mcpServers": {
    "arenza": {
      "url": "https://mcp.arenza.ai/mcp"
    }
  }
}

Other clients

In a client that supports remote MCP, add the server URL above. Claude Desktop support varies by version; follow your client's menus. Do not assume every version can configure a remote URL through a local JSON file.

Sign in and verify

On the first call, a compatible client opens your browser. Sign in to Arenza and approve authorization. Redirects to api.arenza.ai or app.arenza.ai are part of the official authorization flow. Do not paste a Personal Access Token.

After authorization, call only the read-only tool list_brands to view accessible brands. This check does not start scans, generation or writes. Available tools vary with the authorized scope; tool count is not a connection-success check.

Troubleshoot

• 401 response: this is expected before login. Complete OAuth and retry. If it persists, check the client's authorization state.
• No login page: check that the client supports remote HTTP MCP and OAuth, and that the server URL is complete.
• Missing tools or brands: check the signed-in account and authorization scope. Do not test the connection by triggering writes.

Credentials: MCP uses OAuth 2.0 (authorization code + PKCE). After authorization, the client calls the server with an OAuth access token, not an API Key. API Keys (arn_pat_…) are for server events reporting and are a separate credential set — see Quickstart for the difference.