X402 Fpl API vs Squiggle
A side-by-side look at the X402 Fpl API and Squiggle MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose X402 Fpl API for sports work as a local process; choose Squiggle for sports as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose X402 Fpl API when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Squiggle when
- You need dedicated capabilities in the Sports domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Sports | Sports |
| Quality signal | 49/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View X402 Fpl API | View Squiggle |
Tools & capabilities
X402 Fpl API tools
No tool names declared yet. Check the project README from the listing page.
Squiggle tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
X402 Fpl API
{
"mcpServers": {
"dohyung1-x402-fpl-api": {
"command": "uvx",
"args": [
"fpl-intelligence"
]
}
}
}
Squiggle
{
"mcpServers": {
"squiggle": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-squiggle"
]
}
}
}
Frequently asked questions
X402 Fpl API is categorized under Sports and uses a local stdio subprocess. Squiggle belongs to Sports and uses a local stdio subprocess. Pick X402 Fpl API for sports work and Squiggle for sports.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
X402 Fpl API is listed as free. Auth: no auth required. Squiggle has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add dohyung1-x402-fpl-api and squiggle as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, X402 Fpl API has a quality signal of 49/100 (Fair) with 4 views, 0 installs and 11 GitHub stars. Squiggle has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.