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

# Overview

> Connect AI agents directly to your Everflow network data using the Model Context Protocol. Currently in early access.

<Warning>
  **MCP access must be enabled for your network.** Email [support@everflow.io](mailto:support@everflow.io) to request access. Until enabled, all connection attempts will be rejected regardless of your API key.
</Warning>

<Note>
  **EU-Hosted Accounts:** If your account is hosted on the European cluster (`api-eu.eflow.team`), please use the European MCP server URL: `https://mcp-eu.eflow.team`. All setup and integration steps are identical, just swap the server URL.
</Note>

The Everflow MCP Server lets AI agents query your network data through natural language — no code, no API calls, no prompt engineering around raw JSON. Instead of building scripts against the REST API, you connect an MCP-compatible client (Claude, Cursor, VS Code Copilot) directly to Everflow and ask questions in plain English.

## Server details

The MCP Server is hosted on its own dedicated subdomain, **`mcp.eflow.team`** (or **`mcp-eu.eflow.team`** for EU-hosted accounts) — separate from the main `api.eflow.team` REST API. All MCP traffic (session init, tool calls, streaming responses) goes through a single streamable HTTP endpoint.

|                     |                                           |
| ------------------- | ----------------------------------------- |
| **Server URL (US)** | `https://mcp.eflow.team`                  |
| **Server URL (EU)** | `https://mcp-eu.eflow.team`               |
| **Transport**       | Streamable HTTP                           |
| **Auth header**     | `X-Eflow-API-Key: <your-network-api-key>` |

MCP uses your existing **Network API key** — the same one used for REST API calls, no separate credential. Affiliate and advertiser keys are **not** accepted. Create or manage keys under **Control Center → Security**; see [Authentication](/user-guide/authentication) for details.

## Permissions

The agent can only access data your API key has permission to see — the same boundaries that apply in the portal apply here.

Since the MCP Server is read-only, always use **Read Only** access when configuring your key. Full Access is unnecessary and not recommended.

Enable the sections that match what you want the agent to query:

| To query…                                  | Enable in Control Center → Security                      |
| ------------------------------------------ | -------------------------------------------------------- |
| Offers, tracking domains                   | **Offer → Manage** (Read Only)                           |
| Affiliates, pixels, invoices, coupon codes | **Partner** (Read Only)                                  |
| Advertisers                                | **Advertiser** (Read Only)                               |
| Clicks, conversions, performance reports   | **Reporting** (Read Only)                                |
| Creatives                                  | **Offer → Creative** (Read Only)                         |
| Offer groups                               | **Offer → Offer Group** (Read Only)                      |
| Smart links / campaigns                    | **Offer → Smart Link** (Read Only)                       |
| Account and network info                   | **Control Center → Accounts & History Logs** (Read Only) |

<Note>
  Tools your key cannot access are hidden from the agent's tool list automatically — if a tool isn't showing up in your client, your key likely needs the corresponding permission above enabled. See [Security Settings](https://helpdesk.everflow.io/customer/how-to-best-utilize-security-settings) in the help center for a step-by-step guide on configuring API key permissions.
</Note>

## What you can do

Once connected, an AI agent can:

* Pull performance metrics and summaries for any date range
* Look up offer details, affiliate profiles, clicks, and conversions
* Diagnose tracking issues by transaction ID
* Search across your platform data using natural language filters
* Run multi-step workflows — for example, finding underperforming affiliates, checking their activity, and drafting a summary — without writing a single line of code

## What it cannot do

The MCP Server is **read-only**. It cannot create, update, or delete any data. All write operations — creating offers, updating affiliate status, adjusting payouts — must go through the [Network API](/api-reference/network-overview).

<Note>
  **The MCP Server is a query interface, not an event system.** It does not push data to you, fire webhooks, or trigger on activity in your network. If you ask "tell me when a new affiliate signs up" — that is not something MCP can do. For event-driven workflows, use [Webhooks](/webhooks/overview) instead.
</Note>

<CardGroup cols={2}>
  <Card title="Quickstart" icon="bolt" href="/ai-automation/mcp/quickstart">
    Connect Gemini CLI, Claude Desktop, Cursor, or VS Code in under 5 minutes.
  </Card>

  <Card title="Tools Reference" icon="wrench" href="/ai-automation/mcp/tools">
    Every tool, parameter, and response field.
  </Card>

  <Card title="Prompt Library" icon="message-lines" href="/ai-automation/mcp/prompts">
    Ready-to-use prompts for common performance marketing workflows.
  </Card>

  <Card title="Agentic Examples" icon="wand-magic-sparkles" href="/ai-automation/mcp/examples">
    End-to-end multi-step workflows with full agent traces.
  </Card>

  <Card title="Limits & Constraints" icon="gauge" href="/ai-automation/mcp/limits">
    Result caps, rate limits, and parameter length constraints.
  </Card>

  <Card title="FAQ" icon="circle-question" href="/ai-automation/mcp/faq">
    Common questions about access, data scope, and troubleshooting.
  </Card>

  <Card title="Authentication" icon="key" href="/user-guide/authentication">
    How to create and manage Network API keys.
  </Card>
</CardGroup>