MCP Setup
Connect an AI assistant to the hosted Padelful MCP server.
The hosted Padelful MCP server is live at https://www.padelful.com/api/mcp. It uses the
Streamable HTTP transport. It needs no key for the public tools.
Hosted MCP server
Add the server URL to your client as a remote MCP server (a custom connector):
https://www.padelful.com/api/mcp{
"mcpServers": {
"padelful": {
"type": "http",
"url": "https://www.padelful.com/api/mcp"
}
}
}Tiers
- Public tier (no key). The public tools give the rating, the sub-ratings, a short summary, the image, store prices as information and the review URL. The limit is 60 requests each minute.
- Partner key. Send your partner key in
Authorization: Bearer <key>orX-Api-Key: <key>. The key adds the keyed tools, with the fields of your tier. To get a key, send an email to partners@padelful.com.
Each racket in a result has an attribution text and a reviewUrl. When you use the
data, show the attribution with a link to the review. The
Data Terms of Use apply.
Available tools
All tools are read-only.
| Tool | Tier | What it gives |
|---|---|---|
search_rackets | Public | Rackets by text, brand, shape and minimum rating, sorted by rating (10 at most) |
get_racket_summary | Public | The summary of one racket by slug |
get_racket | Partner key | The full data of one racket, as your tier allows |
get_lab_data | Partner key | The lab measurements of one racket: the summary, and all rows for the paid tier |
Each tool accepts locale (en or es).
Quick prompts
- "Find round rackets with a rating above 8.0"
- "What is the Padelful rating of the Bullpadel Hack 04 2025?"
- "Show the best control rackets from Babolat"
Run locally via npm
The npm package @padelful/mcp-server runs a local server for package development. It
calls the partner API with no key, so the live API answers 401 to it. Set
PADELFUL_API_URL to your local app, for example http://localhost:3000. Use the hosted
server for all other uses.
Troubleshooting
401: your partner key is wrong or revoked. Remove the key to use the public tier.429: you sent too many requests. Wait for the number of seconds inRetry-After.405on GET: the server sends no event stream. Your client must use POST.