Access & setup
How do I get access to the MCP Server? The MCP Server is in early access. Email support@everflow.io to request access for your network. Once enabled, any network user with a valid Network API key can connect. Which AI clients are supported? Any client that implements the MCP specification. This includes Gemini CLI, Claude Desktop, Cursor, VS Code with Copilot, and others. See the MCP clients directory for a full list. Setup instructions for the most common clients are in the Quickstart. Can affiliate or advertiser users connect? No. Only Network API keys are accepted. Affiliate and advertiser keys will receive a403 Forbidden response. This is by design — the MCP Server exposes network-level data that is not appropriate for affiliate or advertiser access.
Does the MCP Server require a separate login or OAuth flow?
No. Authentication is handled by the X-Eflow-API-Key header, the same credential you use for the REST API. There is no browser-based OAuth or additional login step.
Permissions & data scope
Why am I not seeing all affiliates? If your account has limited affiliate scope, the MCP Server enforces that scope — you will only see affiliates assigned to you. This is the same restriction that applies in the Everflow UI and REST API. Callget_account_info and check current_user.is_limited_affiliate_scope to confirm. To see all affiliates, ask a network admin to update your scope in Control Center → Security.
Can the agent access data from other networks?
No. Every tool call is scoped to the network associated with your API key. The MCP Server has no cross-network access.
What data can the agent never access?
The MCP Server does not expose: passwords or credentials of any kind, raw payment or banking details, other networks’ data, or any data your API key does not have permission to view through the standard REST API.
Does my employee permission level affect what the agent can do?
Yes. The agent operates with the exact same permissions as the API key you provide. If your key belongs to an employee with restricted advertiser or affiliate scope, the agent inherits those restrictions automatically. See Permissions for the full breakdown.
Capabilities & limits
Can the agent create, update, or delete data? No. The MCP Server is strictly read-only. All write operations — creating offers, updating affiliate status, adjusting payouts, approving conversions — must go through the Network API. How current is the data? Reporting data (clicks, conversions, performance reports) reflects the same latency as the REST API — typically near real-time for tracking events and a short processing delay for aggregated metrics. Entity data (offers, affiliates, advertisers) is fetched live on each request. Are there limits on how much data I can retrieve? Yes. See Limits & Constraints for the full breakdown. The main constraints are:search_clicks returns up to 1,000 records over a maximum 14-day window; search_conversions returns up to 500 records with no enforced date range limit. Performance reports are paginated with a maximum of 100 rows per page.
Can I run reports for any date range?
Performance reports (run_performance_report, run_network_summary) have no enforced date range limit beyond what the underlying data supports. search_clicks is limited to a 14-day window per query. search_conversions has no enforced date range limit but is capped at 500 records per call.
Is there a rate limit?
The MCP Server applies the same rate limits as the Network REST API. See Rate Limiting for details. Each tool call counts as one or more API requests depending on the data it fetches.
Troubleshooting
The agent says it can’t find a tool or the tools list is empty. Restart your MCP client after adding the Everflow server config. If the problem persists, verify your config file has valid JSON (no trailing commas) and that theX-Eflow-API-Key header is set correctly.
I’m getting a 401 Unauthorized error.
Your API key is missing or invalid. Verify the key in Control Center → Security and make sure it is copied correctly into your client config with no extra spaces.
I’m getting a 403 Forbidden error.
This usually means either your network does not have MCP access enabled (email support@everflow.io to request access) or you are using an affiliate or advertiser key instead of a Network key.
The agent returns results, but they seem incomplete.
Check whether your account has limited affiliate scope — get_account_info will confirm this. If your scope is correct and data still seems missing, the relevant records may not exist or may be outside the date range you specified.
The session times out after a period of inactivity.
This is expected behavior. Sessions idle for more than 10 minutes are automatically closed server-side. MCP clients that implement the Streamable HTTP spec will negotiate a new session transparently on the next request. If your client does not recover automatically, restart it.
Performance reports return 0 results for a date range I expect to have data.
Check that the timezone parameter matches your network’s reporting timezone. A mismatch can cause date boundaries to shift and return empty results. Use get_account_info to confirm your network’s default timezone before running reports.