Server details
The MCP Server is hosted on its own dedicated subdomain,mcp.eflow.team — 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 | https://mcp.eflow.team |
| Transport | Streamable HTTP |
| Auth header | X-Eflow-API-Key: <your-network-api-key> |
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) |
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.
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.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.
