Any tool that supports the Model Context Protocol (MCP) can connect to Flyweel. This guide covers the universal configuration.
Connection Details
Use these settings in any MCP-compatible client:
| Setting | Value |
|---|---|
| Server URL | https://api.flyweel.co/mcp-server/mcp |
| Authentication | Header-based |
| Header Name | X-API-Key |
| Header Value | Your fwl_* token |
Get Your Token
- Go to app.flyweel.co
- Click Settings → API Tokens
- Click Create New Token
- Name it descriptively (e.g., “My App - MacBook”)
- Click Generate and copy it immediately
Your token format: fwl_ + 64 hex characters
Example:
fwl_a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2Standard JSON Configuration
Most MCP clients use a JSON config file. Here’s the universal format:
{ "mcpServers": { "flyweel": { "url": "https://api.flyweel.co/mcp-server/mcp", "headers": { "X-API-Key": "fwl_YOUR_TOKEN_HERE" } } }}Replace fwl_YOUR_TOKEN_HERE with your actual token.
Alternative: Query Parameter Auth
For clients that don’t support custom headers (SSE/GET requests), you can pass the token as a query parameter:
https://api.flyweel.co/mcp-server/mcp?token=fwl_YOUR_TOKEN_HEREQuery parameter auth is less secure. Use header-based auth when possible.
Protocol Details
| Property | Value |
|---|---|
| Protocol | MCP (Model Context Protocol) |
| Transport | HTTP with StreamableHttpTransport |
| Message Format | JSON-RPC 2.0 |
| Timeout | 30 seconds |
| Max Response | 6MB |
Rate Limits
Flyweel MCP allows 20 requests per second per API token. This is more than enough for normal conversation—you’d have to ask questions faster than humanly possible to hit this limit.
If you’re building an automated system, keep this in mind.
What You Can Ask
Once connected, just ask in natural language. Here are examples:
See Your Ad Accounts
“What Google Ads accounts do I have connected?”
“Show me all my Meta ad accounts”
“List my connected advertising accounts”
Get Performance Metrics
“How did my Google Ads perform last month?”
“Show me Meta Ads metrics for January 2025”
“What’s my ad spend across all platforms this week?”
“Give me a breakdown of campaign performance for account X”
View Campaigns
“What campaigns are running in my Google Ads account?”
“List all Meta campaigns for [account name]”
“Show me active campaigns”
You don’t need to know the exact tool names or parameters. Just describe what you want in plain English and the AI will figure out the right calls.
Testing Your Connection
To verify your token works, use cURL to check the server:
curl -X POST https://api.flyweel.co/mcp-server/mcp \ -H "Content-Type: application/json" \ -H "X-API-Key: fwl_YOUR_TOKEN_HERE" \ -d '{"jsonrpc": "2.0", "id": 1, "method": "initialize"}'A successful response confirms your token is valid and the connection is working.
Error Codes
| Code | Meaning |
|---|---|
| -32700 | Bad JSON |
| -32600 | Invalid request |
| -32601 | Method doesn’t exist |
| -32602 | Bad parameters |
| -32000 | Server error |
| -32001 | Auth error (token missing or wrong) |
Troubleshooting
”Authentication Error” or Code -32001
Your token is missing, invalid, or deleted.
Fix: Generate a new token at app.flyweel.co → Settings → API Tokens.
”No accounts found”
You haven’t connected ad accounts to Flyweel.
Fix: Go to Settings → Connections in Flyweel and connect your Google Ads or Meta Ads.
Connection timeout
The request is taking too long.
Fix:
- Check your internet connection
- Try again in a few seconds
- Contact support if it persists
Need Help?
If you’re building a custom MCP integration or having trouble with a specific client:
- Email: team@flyweel.co
- Include: Client name, error message, config snippet (without token)