The Floppydata MCP server gives an agent a small set of safe, job-focused tools for Client API v2. Instead of asking the agent to remember endpoint paths, headers, and request bodies, you give it one API key and it can fetch Web Data, build proxy connections, check proxies, and read account usage.
Install
Create or copy a Client API key from API keys.
Add this server to your MCP client:
That is all the configuration. The server runs locally through stdio and talks to the production Client API at https://api.floppydata.net.
Keep API keys in your MCP client environment config. Do not paste real keys into prompts, docs, or shared logs.
What the Agent Can Do
The proxy tools return connection.connectionString where a connection is involved. Use that value directly in HTTP clients, browser profiles, or automation tools.
Try It
After adding the server, ask your agent:
Then try a rotating proxy flow:
For Web Data:
How It Maps to Client API v2
The MCP server is a thin customer-facing wrapper over the public v2 API:
- Web Data fetch:
POST /v2/web-data/fetch
- Rotating connection:
POST /v2/proxy/rotating/connections
- Rotating locations:
GET /v2/proxy/rotating/locations
- Proxy check:
POST /v2/proxy/check
- Static proxies:
GET /v2/proxy/static
- Account balances:
GET /v2/account/balances
- Account usage:
GET /v2/account/usage
It only exposes customer-facing tools. If an agent needs several proxy connections, ask it to create them one at a time.
Package
The package is public on npm:
Source code is available on GitHub:
github.com/Floppydata/floppydata-mcp