> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.pixalate.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.pixalate.com/_mcp/server.

# Access and limits

> Sign-in, access, account scoping, result sizes, the 60-day query range, exports, throttling and usage for Pixalate's MCP connectors.

## Sign-in

There are two ways to sign in. Use one or the other, not both.

### Browser sign-in (recommended)

Pixalate's MCP connectors use OAuth. You add the server URL to your assistant, your assistant opens the Pixalate sign-in page in a browser, and you sign in with your Pixalate account and approve access. Your assistant stores the credential it gets back. You don't paste a key or token anywhere.

You'll be asked to sign in again from time to time. Your assistant prompts you when it's needed.

### Sign in with an API key

If your assistant can't complete a browser sign-in, for example in an automated or headless setup, send your Pixalate API key in an `x-api-key` header instead. It's the same key you use for Pixalate's REST APIs; see [Authentication and API keys](/apis/authentication).

#### Claude Code

```bash
claude mcp add --transport http pixalate-mcp https://mcp.pixalate.com/mcp \
  --header "x-api-key: YOUR_API_KEY"
```

#### JSON config

For clients that read an `mcpServers` file and support custom headers, such as Cursor:

```json
{
  "mcpServers": {
    "pixalate-mcp": {
      "url": "https://mcp.pixalate.com/mcp",
      "headers": { "x-api-key": "YOUR_API_KEY" }
    }
  }
}
```

* **Send the key or the browser sign-in, not both.** A request that carries both is rejected.
* **A key takes precedence.** When an `x-api-key` header is present, the server uses it and doesn't start the browser sign-in. If you meant to use browser sign-in, remove the header.
* **Protect the key.** Don't put it in config files you share or commit to source control.

## Access

Access to each Pixalate MCP connector is part of your Pixalate agreement. There's no self-serve sign-up. To get access, or to add a product, contact your Pixalate account manager.

Signing in and having access are separate. Tools are enabled for your account per product, so you can sign in successfully and still see no tools, or see Analytics MCP tools but not Enrichment MCP tools. If that happens, tell your account manager which product you need.

## What your account can reach

* **Your own credentials.** Queries run with your own account's credentials. There's no client ID to pass.
* **Your reports and columns.** Which reports, columns and enrichment widgets you can use depends on your account. Ask your assistant "What Pixalate reports can I run?" before you start.
* **Columns are checked before a report runs.** Default columns your account isn't entitled to are left out and listed in `truncated_columns`. That applies to exports too, so an export never contains a column your account can't see.

## Limits on a request

| Limit                          | Value                                                                                                   |
| ------------------------------ | ------------------------------------------------------------------------------------------------------- |
| Analytics date range           | At most 60 days per query, counting both the start and end dates. For a longer period, run it in parts. |
| Analytics rows per page        | 40 by default, up to 100. Ask for the next page to continue.                                            |
| Analytics exports              | One CSV link for the full result set. Paging doesn't apply.                                             |
| Enrichment IDs per request     | 1 to 50.                                                                                                |
| Enrichment widgets per request | At least one. Ask only for the widgets you need.                                                        |

### Reports that take longer

Analytics reports run in the background. If a report isn't finished when the query returns, you get `status: "IN_PROGRESS"` and a `request_id`. Your assistant collects the result with `analytics_status` after a short wait. Nothing is lost and you don't need to run the query again unless the request ID has expired. See [analytics_status](/mcp/tools#analytics_status).

## Throttling

The Pixalate MCP server doesn't set its own request limit. The Pixalate services behind it can still ask you to slow down when they're busy, or when too many of your reports are running at once. When that happens the tool returns a `rate_limited` code with a message such as "Too many analytics requests at once. Wait a few seconds and try again." Most assistants wait and retry on their own.

If you see this often, look at the shape of the question. Asking about a long list of items one at a time sends one request per item. For enrichment, send up to 50 IDs in one request instead.

## Quota

Your analytics report quota is separate from throttling. If it's used up, the message says your quota is exhausted, and it may say when it resets. Waiting a few seconds won't fix it. Contact your Pixalate account manager about your allowance.

## Usage and pricing

Usage is measured and charged according to your Pixalate agreement. Pricing isn't published. For your allowance, contact your Pixalate account manager.

## Related

* [Tool reference](/mcp/tools)
* [FAQ and troubleshooting](/mcp/faq)