A side-by-side look at the Buzzr Sports Engine and X402 Fpl API MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Buzzr Sports Engine for sports work as a local process; choose X402 Fpl API 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 Buzzr Sports Engine when
You need dedicated capabilities in the Sports domain.
No tool names declared yet. Check the project README from the listing page.
X402 Fpl API 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.
Buzzr Sports Engine is categorized under Sports and uses a local stdio subprocess. X402 Fpl API belongs to Sports and uses a local stdio subprocess. Pick Buzzr Sports Engine for sports work and X402 Fpl API 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.
Buzzr Sports Engine has no declared pricing — check the project's own site. X402 Fpl API is listed as free. Auth: no auth required. 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 buzzr-sports-engine and dohyung1-x402-fpl-api as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Buzzr Sports Engine has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. X402 Fpl API has 49/100 (Fair) with 4 views, 0 installs and 11 GitHub stars.