Partle Marketplace MCP Server

Model Context Protocol server for the Partle marketplace — let your AI shop here: search products and stores, get prices and purchase links, or ask it to add a listing for you, all without leaving your assistant.

130,000+ products across ~16,000 stores. Reads need no auth. Writes need a pk_… API key.

Two ways to run it

Remote (recommended — zero setup)

Point your MCP client at:

https://partle.rubenayla.xyz/mcp/

That's it. Streamable HTTP transport, MCP spec 2025-06-18. Per-client install instructions: /documentation/mcp-setup/.

Local stdio (for clients that prefer installable servers, or for Glama / Smithery scoring)

pip install partle-mcp
partle-mcp

Or with uvx (no install):

uvx partle-mcp

Or with Docker:

docker run --rm -i ghcr.io/rubenayla/partle-mcp

The stdio package proxies to the public REST API at https://partle.rubenayla.xyz, so you don't need a database or local backend.

Claude Desktop / Claude Code (stdio)

{
  "mcpServers": {
    "partle": {
      "command": "uvx",
      "args": ["partle-mcp"]
    }
  }
}

Related MCP server: Google Maps Places MCP

Tools (20 total)

Read (no auth)

Write (authenticated)

Two ways to authenticate, in preference order:

1. OAuth (recommended) — when you add Partle as a custom connector in claude.ai or any MCP client that supports OAuth, the client walks you through a one-click consent screen and attaches a bearer token automatically. Scopes: products:read, products:write, inventory:read, inventory:write. Revoke at /account → Connected apps. RFC 9728 metadata at /.well-known/oauth-protected-resource; RFC 7591 dynamic client registration at /oauth/register.

2. API key (fallback) — pass an api_key parameter to any write tool. Generate at /account → API Keys. Use this when your client doesn't support OAuth (raw scripts, programmatic agents).

Products — public catalog listings.

The remote HTTP server also offers get_upload_url (re-fetches a signed upload URL for an existing product). Not exposed in this stdio package — use the remote server if you need it.

Inventory — private workshop tracking (owned / wanted / for_sale / sold / discarded). Private to the owner; does not appear on the public /wanted feed.

Buy requests — public demand-side posts on /wanted. Independent of personal inventory.

Feedback

Public REST API

Same data, also reachable as plain HTTP for clients without MCP support:

• GET /v1/public/products?q=cerrojo&limit=10 — search products

• GET /v1/public/stores?q=Madrid&limit=10 — search stores

• GET /v1/public/wanted?q=bolt&limit=10 — list open public buy requests

• GET /v1/public/stats — platform totals

• POST /v1/public/feedback — submit feedback

Base URL: https://partle.rubenayla.xyz. Rate-limited to 100 req/hour per IP.

Full docs: /documentation/ · OpenAPI: /openapi.json · Discovery: /.well-known/mcp.json.

Example

You: "Use Partle to find a drill under €50."

Claude: (calls search_products(query="drill", max_price=50))

Returns Blackspur 13pc High Speed Drill Bit Set at €4.99 (Lenehans, IE), Flotec Drill Pump 225 GPH at €17.14 (Kooyman Megastore, NL), and a few more — each with a partle_url to view the listing.

More examples in the setup guide.

License

Apache-2.0 — see LICENSE.