> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aiola.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Aiola to Claude, ChatGPT, and Cursor

> Add Aiola's hosted MCP connector so Claude, ChatGPT, Cursor, Codex, and other AI agents can read your analytics, app logs, feedback, and Search Console data across every project.

Aiola's hosted MCP server lets any MCP-compatible AI client work with the data from all your Aiola projects in one connection. Server URL: `https://aiola.app/api/mcp` — transport is Streamable HTTP, authentication is OAuth 2.1. It is separate from, and does not affect, the local MCP server the Aiola desktop app runs.

## Before you start

* An Aiola account with an active Pro subscription or free trial. GUI Lifetime does not include hosted connector access.
* Analytics, app logs, or feedback set up for at least one project — the tools read the data those surfaces collect.

## Connect Claude

<Steps>
  <Step title="Open connector settings">
    In Claude, go to **Settings → Connectors** and select **Add custom connector**.
  </Step>

  <Step title="Enter connector details">
    Name the connector `Aiola` and set the URL to `https://aiola.app/api/mcp`.
  </Step>

  <Step title="Configure authentication settings">
    Leave the two auto-detected options as Claude sets them:

    * **Authentication:** `Always required`
    * **OAuth client:** `No client ID — register one automatically`

    Do not pick **Use Anthropic's hosted client metadata** — Aiola's authorization server does not support client ID metadata documents.
  </Step>

  <Step title="Add and approve">
    Add the connector, then approve access on the `aiola.app` consent screen that opens.

    <Warning>
      The consent request expires after 10 minutes. If approval fails, remove the connector and add it again.
    </Warning>
  </Step>
</Steps>

## Connect other clients

<Tabs>
  <Tab title="Claude Code">
    ```bash theme={null}
    claude mcp add --transport http aiola https://aiola.app/api/mcp
    ```
  </Tab>

  <Tab title="Codex CLI">
    ```bash theme={null}
    codex mcp add aiola --url https://aiola.app/api/mcp
    ```
  </Tab>

  <Tab title="Cursor">
    Add the server to `~/.cursor/mcp.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "aiola": {
          "url": "https://aiola.app/api/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="VS Code">
    Add the server to `.vscode/mcp.json`:

    ```json theme={null}
    {
      "servers": {
        "aiola": {
          "type": "http",
          "url": "https://aiola.app/api/mcp"
        }
      }
    }
    ```
  </Tab>

  <Tab title="ChatGPT">
    Go to **Settings → Connectors**, then add a custom MCP connector with the URL `https://aiola.app/api/mcp`.
  </Tab>
</Tabs>

<Note>
  Each client opens a browser once for OAuth sign-in.
</Note>

## Available tools

| Tool                        | What it does                                                 | Access |
| --------------------------- | ------------------------------------------------------------ | ------ |
| `list_projects`             | Lists your Aiola projects                                    | Read   |
| `get_analytics_overview`    | A full traffic and behaviour summary for a date range        | Read   |
| `get_analytics`             | A single analytics pipe, such as top pages or referrers      | Read   |
| `get_analytics_definitions` | Explains what each analytics pipe and metric means           | Read   |
| `get_search_keywords`       | Google Search Console queries, clicks, impressions, position | Read   |
| `get_indexing_issues`       | Indexing and coverage state for your URLs                    | Read   |
| `get_app_logs`              | Grouped production errors and warnings                       | Read   |
| `get_app_log_events`        | Individual events for one log group                          | Read   |
| `update_app_log_status`     | Marks a log group resolved or ignored                        | Write  |
| `get_feedback`              | In-app user feedback                                         | Read   |
| `update_feedback`           | Marks feedback resolved or ignored                           | Write  |

Every tool takes an optional `project` argument naming an Aiola project. Omit it and the tool uses your only project automatically, or returns the list of project names to choose from when you have several.

## Privacy and limits

* Nothing can be deleted and account settings cannot be changed. The only writes are the two status updates above.
* `get_app_log_events` strips request headers, request body, request query, user IP, and user email by default and reports what it removed in a `_redacted` field. Pass `include_request_data: true` only when raw request context is needed; those fields can contain secrets.
* Connected clients get read-only access scoped to your own projects, enforced by row-level security.
* Shared budget of 120 units per minute per user; heavier tools cost more units than light ones.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Approval fails or returns an error">
    The 10-minute consent window expired; remove the connector and add it again.
  </Accordion>

  <Accordion title="Tools return a subscription error">
    The account has no active Pro subscription or trial, or is on GUI Lifetime.
  </Accordion>

  <Accordion title="A tool says it cannot find your project">
    Pass the exact project name in the `project` argument; run `list_projects` to see the available names.
  </Accordion>
</AccordionGroup>