For AI assistants · MCP
Ask your AI for a heart route. It'll find one in Paris.
CityHeart exposes its catalogue of 3,000+ heart-shaped routes as a Model Context Protocol server. Plug it into Claude Desktop, Cursor or any MCP-compatible client, and ask your AI for a heart route mid-conversation. Read-only and free to query.
- premium heart routes ready to query
- 3,000+
- tools exposed via JSON-RPC
- 7
- compatible clients (Claude, Cursor, Goose…)
- 5+
- auth, no key, public read-only catalogue
- €0
premium heart routes ready to query
tools exposed via JSON-RPC
compatible clients (Claude, Cursor, Goose…)
auth, no key, public read-only catalogue
What you get today
Any MCP-compatible AI client (Claude Desktop, Cursor, Goose, Continue, the upcoming OpenAI Apps SDK) can search and fetch CityHeart routes through the tools below. The actual generation of a personalised heart still happens on cityheart.run/app , payment runs through Stripe there. The MCP server is the discovery + preview surface, not the payment surface.
MCP URL
https://qsbuptcxbntjyirktkcf.supabase.co/functions/v1/mcp- 01 Open the config file at
~/Library/Application Support/Claude/claude_desktop_config.json(macOS) or%APPDATA%\Claude\claude_desktop_config.json(Windows). - 02 Paste the config below into the
mcpServersblock. - 03 Restart Claude Desktop.
- 04 Ask "find me a heart-shaped running route in Lyon", Claude invokes the tool and shows matches.
claude_desktop_config.json
{ "mcpServers": { "cityheart": { "url": "https://qsbuptcxbntjyirktkcf.supabase.co/functions/v1/mcp" } } }Cursor → Settings → MCP → Add new MCP server. Or edit ~/.cursor/mcp.json:
.cursor/mcp.json
{ "mcp": { "servers": { "cityheart": { "url": "https://qsbuptcxbntjyirktkcf.supabase.co/functions/v1/mcp" } } } }find_heart_route_in_city
Find an existing premium heart route in a given city. Returns up to 5 matches.
city: stringmax_distance_km?: numberprefer_gold?: boolean
get_route_details
Full route metadata + image URL + share URL + structured pricing (€9.90 one-time).
slug: string
list_supported_cities
List cities with at least one heart route available, sorted by inventory size.
limit?: number (default 25, max 100)
generate_heart_route
Start a new heart for a city: returns existing matches + a deep-link to the live builder with city / distance / dedication / cause pre-filled.
city: stringdistance_km?: numberdedication?: stringin_memory?: booleancause_url?: string
add_dedication
Compose a builder URL with a dedication pre-filled, name appears on the runner's watch + Strava activity title.
name: stringin_memory?: booleancity?: string
add_cause
Compose a builder URL with a fundraising link pre-filled, embedded in the GPX so it surfaces in the Strava activity description after sync.
fundraising_url: stringcity?: string
export_gpx
Return the GPX download / Stripe checkout URL for a specific public route. €9.90 one-time. Payment happens on cityheart.run, never through the chat.
slug: string
From a terminal, send a tools/list JSON-RPC request. You should see the seven tools above.
terminal
curl -X POST https://qsbuptcxbntjyirktkcf.supabase.co/functions/v1/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'The server is a Deno edge function on Supabase, stateless, JSON-RPC 2.0 over HTTP. Source is in the public repo under supabase/functions/mcp/. It reads from public_routes (the same dataset that powers the Wall of Hearts), no auth, no PII, public read-only.
Pricing surfaced through get_route_details is structured (price, currency, one_time, refund_policy), so AI clients can quote it accurately in conversation. €9.90 one-time per route, no subscription.
If you ship an integration that uses this server, drop us a note at hello@cityheart.run.
Not using an AI client yet? You can still build a heart the normal way.
Build your heart route