Quickstart - Everflow API

MCP must be enabled for your network before any connection attempt will succeed. Email support@everflow.io to request access. See the Overview for full availability details.

Prerequisites

A Network API key with access to your network. See Authentication.
MCP access enabled for your network (see the Overview for server URL, transport, and availability details).

Connect your client

Each setup takes under 5 minutes. All clients connect to the same server URL (https://mcp.eflow.team) using the same X-Eflow-API-Key header — only the config file format varies. If you’re unsure where to start, use Claude Desktop — it has the most straightforward setup and the best out-of-the-box MCP experience.

Claude Desktop
Cursor
Gemini CLI
VS Code

Open your Claude Desktop config file

macOS

open ~/Library/Application\ Support/Claude/claude_desktop_config.json

Windows

notepad %APPDATA%\Claude\claude_desktop_config.json

Add the Everflow server to the mcpServers block

{
  "mcpServers": {
    "everflow": {
      "url": "https://mcp.eflow.team",
      "headers": {
        "X-Eflow-API-Key": "your-network-api-key"
      }
    }
  }
}

Save the file and restart Claude Desktop

Quit and reopen the app so it picks up the new MCP server.

Test the connection

Open a new conversation. You should see an Everflow tools indicator in the input area. Ask:

“What is my network’s name and default currency?”

Open Cursor's MCP settings

Go to Cursor Settings → MCP, or press Cmd+Shift+P → MCP: Edit Configuration.

Add the Everflow server

{
  "mcpServers": {
    "everflow": {
      "url": "https://mcp.eflow.team",
      "headers": {
        "X-Eflow-API-Key": "your-network-api-key"
      }
    }
  }
}

Save and reload the window

The Everflow tools will appear in the Cursor Agent chat.

Gemini CLI is Google’s open-source terminal agent with native MCP support.

Install Gemini CLI

npm install -g @google/gemini-cli

Open the Gemini CLI config file

open ~/.gemini/settings.json

Create the file if it doesn’t exist yet.

Add the Everflow server

{
  "mcpServers": {
    "everflow": {
      "httpUrl": "https://mcp.eflow.team",
      "headers": {
        "X-Eflow-API-Key": "your-network-api-key"
      }
    }
  }
}

Start a session and verify the connection

gemini

“Call get_account_info and tell me my network name and default currency.”

VS Code requires an active GitHub Copilot Chat subscription and the Copilot Chat extension. The config format also differs from the other clients — note the servers key instead of mcpServers.

Install the GitHub Copilot Chat extension

Install it from the VS Code marketplace if you don’t have it already.

Open your MCP configuration

Open VS Code settings (Cmd+,) and search for MCP Servers, or edit .vscode/mcp.json directly in your workspace:

{
  "servers": {
    "everflow": {
      "url": "https://mcp.eflow.team",
      "headers": {
        "X-Eflow-API-Key": "your-network-api-key"
      }
    }
  }
}

Open Copilot Chat in Agent mode

The Everflow tools will appear in the tool picker.

Verify the connection

Once connected in any client, run this prompt to confirm everything is working:

“Call get_account_info and tell me my network name, default timezone, and default currency.”

A successful response confirms your API key is valid, your network has MCP access enabled, and the MCP server is reachable.

Debug with MCP Inspector

If a client isn’t connecting or tools aren’t appearing, the MCP Inspector lets you test the server directly — independent of any AI client config.

Run the inspector

No install required:

npx @modelcontextprotocol/inspector

Configure the connection in the inspector UI

Field	Value
Transport	Streamable HTTP
URL	`https://mcp.eflow.team`
Header name	`X-Eflow-API-Key`
Header value	`your-network-api-key`

Connect and call a test tool

Click Connect, then call get_account_info from the Tools tab. A valid response confirms the server is reachable and your key is accepted. If this works but your AI client still can’t connect, the issue is in your client config, not the server.

Troubleshooting

Symptom	Likely cause	Fix
Connection refused or timeout	MCP not enabled for your network	Email support@everflow.io to request access
`401 Unauthorized`	Invalid or missing API key	Verify the key in Control Center → Security
`403 Forbidden`	Key is not a Network key	Affiliate and advertiser keys are not accepted
Tools not appearing in client	Config file syntax error	Validate your JSON — trailing commas are invalid
Partial data returned	Limited affiliate scope on your key	Employees with scoped access only see their assigned affiliates

MCP Server

​Prerequisites

​Connect your client

​Verify the connection

​Debug with MCP Inspector

​Troubleshooting

Prerequisites

Connect your client

Verify the connection

Debug with MCP Inspector

Troubleshooting