--- title: Other MCP Clients | Flyweel Docs description: Connect Flyweel MCP to any MCP-compatible client url: "https://www.flyweel.co/docs/mcp/other" type: static generatedAt: "2026-09-18T05:57:35.771Z" --- ![Documentation hero background](https://astro-flyweel-docs.vercel.app/vision-hero.webp) # Other MCP Clients Any tool that supports the Model Context Protocol (MCP) can connect to Flyweel. This guide covers the universal configuration. --- ## Connection Details[Link to this section](#connection-details) Use these settings in any MCP-compatible client: | Setting | Value | | --- | --- | | **Server URL** | `https://api.flyweel.co/functions/v1/mcp-server/mcp` | | **Authentication** | Header-based | | **Header Name** | `X-API-Key` | | **Header Value** | Your `fwl_*` token | --- ## Get Your Token[Link to this section](#get-your-token) 1. Go to [app.flyweel.co](https://app.flyweel.co) 1. Click **Settings** → **API & MCP** 1. Under **Advanced: use an API key instead**, click **Generate API key** (or **Create Token** to name your own, e.g., “My App - MacBook”) 1. Copy it once — it won’t be shown again Your token format: `fwl_` + 64 hex characters Example: ** ``` fwl_a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2 ``` --- ## Standard JSON Configuration[Link to this section](#standard-json-configuration) Most MCP clients use a JSON config file. Here’s the universal format: ** ``` { "mcpServers": { "flyweel-mcp-server": { "url": "https://api.flyweel.co/functions/v1/mcp-server/mcp", "headers": { "X-API-Key": "fwl_YOUR_TOKEN_HERE" } } }} ``` Replace `fwl_YOUR_TOKEN_HERE` with your actual token. --- ## Alternative: Query Parameter Auth[Link to this section](#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/functions/v1/mcp-server/mcp?token=fwl_YOUR_TOKEN_HERE ``` Query parameter auth is less secure. Use header-based auth when possible. --- ## Protocol Details[Link to this section](#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[Link to this section](#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[Link to this section](#what-you-can-ask) Once connected, just ask in natural language. Here are examples: ### See Your Ad Accounts[Link to this section](#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[Link to this section](#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[Link to this section](#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[Link to this section](#testing-your-connection) To verify your token works, use cURL to check the server: *Terminal window* ``` curl -X POST https://api.flyweel.co/functions/v1/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[Link to this section](#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[Link to this section](#troubleshooting) ### ”Authentication Error” or Code -32001[Link to this section](#authentication-error-or-code--32001) Your token is missing, invalid, or deleted. **Fix:** Generate a new token at [app.flyweel.co](https://app.flyweel.co) → Settings → API & MCP. ### ”No accounts found”[Link to this section](#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[Link to this section](#connection-timeout) The request is taking too long. **Fix:** 1. Check your internet connection 1. Try again in a few seconds 1. Contact support if it persists --- ## stdio-only clients: use the mcp-remote shim[Link to this section](#stdio-only-clients-use-the-mcp-remote-shim) Some MCP clients only support stdio transport (Codex CLI, early versions of Windsurf, a handful of JetBrains AI builds). For those, use [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) to bridge Flyweel’s HTTP endpoint to stdio. Run it once to test: *Terminal window* ``` npx -y mcp-remote https://api.flyweel.co/functions/v1/mcp-server/mcp \ --header "X-API-Key: fwl_YOUR_TOKEN_HERE" ``` Wrap that command in your client’s stdio server config. Generic shape: ** ``` { "mcpServers": { "flyweel-mcp-server": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.flyweel.co/functions/v1/mcp-server/mcp", "--header", "X-API-Key: fwl_YOUR_TOKEN_HERE" ] } }} ``` The shim runs on the user’s machine, opens an HTTP connection to Flyweel, and speaks stdio to the client. --- ## Need Help?[Link to this section](#need-help) If you’re building a custom MCP integration or having trouble with a specific client: - Email: **[team@flyweel.co](mailto:team@flyweel.co)** - Include: Client name, error message, config snippet (without token) --- ## Next Steps[Link to this section](#next-steps) - [Technical reference](/docs/mcp/setup#technical-reference) - [Request a feature](/docs/mcp/setup#request-a-feature) ### Ready to get started? Start optimizing your ad spend today with Flyweel. [Start Free](https://signup.flyweel.co/?variant=control)