Skip to main content
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.
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.
This is the Network MCP — it exposes the network operator’s view of your account (your partners, advertisers, offers, and network-wide reporting) and authenticates with a Network API key. It is not a partner- or advertiser-facing tool, and affiliate/advertiser keys are not accepted. A dedicated Affiliate MCP is planned separately.

​
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. 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 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. For querying, use Read Only access — it covers every read tool. Enable the sections that match what you want the agent to query:
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 in the help center for a step-by-step guide on configuring API key permissions.

​
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

​
Read-only

The MCP Server is read-only — it queries your network data but does not change it. It cannot create, update, or delete records. Any data changes must go through the Network API.
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 instead.

Quickstart

Connect Gemini CLI, Claude Desktop, Cursor, or VS Code in under 5 minutes.

Tools Reference

Every tool, parameter, and response field.

Prompt Library

Ready-to-use prompts for common performance marketing workflows.

Agentic Examples

End-to-end multi-step workflows with full agent traces.

Limits & Constraints

Result caps, rate limits, and parameter length constraints.

FAQ

Common questions about access, data scope, and troubleshooting.

Authentication

How to create and manage Network API keys.