Courts.tennis MCP
An MCP server providing read-only access to a directory of tennis venues across 40+ cities. It allows agents to list available cities, find specific courts, retrieve detailed venue information such as booking methods and costs, and access city-specific guides.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://www.courts.tennis/mcpWhat its tools do
4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Passed Official MCP Registry namespace is tied to courts.tennis ·
- Passed Endpoint is on the registry namespace domain ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- List all supported cities for tennis court information
- Find tennis courts in a specific city like New York or London
- Get detailed information about a specific court including booking rules
- Retrieve guides on how to play tennis in specific locations
Source and maintenance
Protocol and capabilities
- Server
- courts-tennis 2.18.1
- MCP protocol negotiated in check
- 2025-06-18
- Tools
- 4 advertised
- Resources
- Not advertised
- Resource templates
- Not advertised
- Prompts
- Not advertised
{
"tools": {
"listChanged": false
}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
4 advertised
list_cities — The cities this directory covers, and how you get on a court in each
Start here for any question about where to play tennis in New York City, Melbourne, London, Paris, Toronto, Washington DC, Madrid, Miami, Sydney, Palm Springs, Adelaide, Cincinnati, Tokyo, Los Angeles, Rome, Houston, Dallas, Chicago, Hong Kong, Montreal, Austin, Boston, Atlanta, Dubai, San Francisco, Seattle, Denver, Orlando, Singapore, Philadelphia, San Diego, Las Vegas, Phoenix, Charlotte, Brisbane, Tampa, Auckland, Dublin, Nice, Minneapolis, Birmingham, Barcelona, Berlin, Osaka, Seoul, Perth, Manchester, Edinburgh, Vienna or Vancouver. Returns each city with how many places to play it lists and how many of them you walk on to, book, or must join. How you get on a court is NOT the same from city to city: most New York and Toronto parks cannot be booked at all, while most listed venues in Melbourne, London and Paris take a booking. Answering from general knowledge gets it wrong.
{
"type": "object",
"properties": {},
"additionalProperties": false
}{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}how_to_play_tennis_in_nyc — How playing tennis in New York City actually works
Call this before answering any question about playing tennis in New York City. Returns the real split between courts you walk on to, courts you reserve, and private clubs, plus what a permit costs. Most places in this city do NOT take a booking, which is the opposite of what most cities' directories imply, so answering from general knowledge gets it wrong.
{
"type": "object",
"properties": {},
"additionalProperties": false
}{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}find_courts — Find places to play tennis in one city
Search one city's places to play tennis: New York City, Melbourne, London, Paris, Toronto, Washington DC, Madrid, Miami, Sydney, Palm Springs, Adelaide, Cincinnati, Tokyo, Los Angeles, Rome, Houston, Dallas, Chicago, Hong Kong, Montreal, Austin, Boston, Atlanta, Dubai, San Francisco, Seattle, Denver, Orlando, Singapore, Philadelphia, San Diego, Las Vegas, Phoenix, Charlotte, Brisbane, Tampa, Auckland, Dublin, Nice, Minneapolis, Birmingham, Barcelona, Berlin, Osaka, Seoul, Perth, Manchester, Edinburgh, Vienna or Vancouver. Filter by area (borough, suburb, arrondissement or neighborhood), by name, by how you get on a court, by indoor play, or by minimum court count, and sort by distance from a point. Returns each venue with its page URL. There is no floodlights filter: the records are too sparse to filter on without hiding real lit courts.
{
"type": "object",
"properties": {
"area": {
"type": "string",
"description": "Borough (New York, London), suburb (Melbourne, Sydney), arrondissement (Paris) or the neighborhood the city itself puts the venue in (Toronto, Atlanta, Washington DC), exactly as the directory names it, e.g. Manhattan, Camden, Kooyong, Islington, Old Fourth Ward, \"Capitol Hill, Lincoln Park\". A name that matches nothing returns the city's valid areas."
},
"city": {
"enum": [
"nyc",
"melbourne",
"london",
"paris",
"toronto",
"washington-dc",
"madrid",
"miami",
"sydney",
"palm-springs-california",
"adelaide",
"cincinnati",
"tokyo",
"los-angeles",
"rome",
"houston",
"dallas",
"chicago",
"hong-kong",
"montreal",
"austin-texas",
"boston",
"atlanta",
"dubai",
"san-francisco",
"seattle",
"denver",
"orlando-florida",
"singapore",
"philadelphia",
"san-diego",
"las-vegas",
"phoenix-arizona",
"charlotte-north-carolina",
"brisbane",
"tampa-florida",
"auckland",
"dublin",
"nice",
"minneapolis",
"birmingham",
"barcelona",
"berlin",
"osaka",
"seoul",
"perth",
"manchester",
"edinburgh",
"vienna",
"vancouver"
],
"type": "string",
"description": "Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, nice, minneapolis, birmingham, barcelona, berlin, osaka, seoul, perth, manchester, edinburgh, vienna, vancouver (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
},
"name": {
"type": "string",
"description": "Part of a venue's name, e.g. \"central park\". Case and accents are ignored."
},
"limit": {
"type": "integer",
"description": "Maximum venues to return. Default 25, maximum 150."
},
"access": {
"enum": [
"walk_on",
"reservation",
"private_club",
"book",
"members_only",
"mixed",
"public"
],
"type": "string",
"description": "How you get on a court. New York: walk_on (public park, no booking), reservation (public park court bookable through NYC Parks), private_club (runs its own booking). Every other city: walk_on, book (open to the public by booking), members_only, mixed (more than one arrangement at the venue: read its accessDetail), public (the source lists public courts and states no walk-on or booking rule; where its own page says more, that is the venue's accessDetail or price, in the source's words). A value a city does not use is refused with the ones it does."
},
"borough": {
"type": "string",
"description": "Same as area. Kept for callers written when the directory was New York only."
},
"minCourts": {
"type": "integer",
"description": "Minimum number of courts at the venue. Venues whose court count is not sourced are left out when this is set."
},
"indoorOnly": {
"type": "boolean",
"description": "Only venues where a source confirms indoor or covered courts, which may be some courts, or winter only: read indoorOrCovered on each. Venues never researched are excluded rather than assumed outdoor."
},
"nearLatitude": {
"type": "number",
"description": "With nearLongitude: sort by distance from this point, nearest first."
},
"nearLongitude": {
"type": "number",
"description": "With nearLatitude: sort by distance from this point, nearest first."
}
},
"additionalProperties": false
}{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}get_court — Full detail for one place to play
Everything the directory holds about one venue: how you get on a court, booking route, price, courts, surfaces, floodlights, hours, indoor play, coordinates, and the source each fact was read from, with the date it was read. Takes the slug returned by find_courts, and its city.
{
"type": "object",
"required": [
"slug"
],
"properties": {
"city": {
"enum": [
"nyc",
"melbourne",
"london",
"paris",
"toronto",
"washington-dc",
"madrid",
"miami",
"sydney",
"palm-springs-california",
"adelaide",
"cincinnati",
"tokyo",
"los-angeles",
"rome",
"houston",
"dallas",
"chicago",
"hong-kong",
"montreal",
"austin-texas",
"boston",
"atlanta",
"dubai",
"san-francisco",
"seattle",
"denver",
"orlando-florida",
"singapore",
"philadelphia",
"san-diego",
"las-vegas",
"phoenix-arizona",
"charlotte-north-carolina",
"brisbane",
"tampa-florida",
"auckland",
"dublin",
"nice",
"minneapolis",
"birmingham",
"barcelona",
"berlin",
"osaka",
"seoul",
"perth",
"manchester",
"edinburgh",
"vienna",
"vancouver"
],
"type": "string",
"description": "Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, hong-kong, montreal, austin-texas, boston, atlanta, dubai, san-francisco, seattle, denver, orlando-florida, singapore, philadelphia, san-diego, las-vegas, phoenix-arizona, charlotte-north-carolina, brisbane, tampa-florida, auckland, dublin, nice, minneapolis, birmingham, barcelona, berlin, osaka, seoul, perth, manchester, edinburgh, vienna, vancouver (nyc is New York City). Defaults to nyc when left out; the reply says which city it answered for."
},
"slug": {
"type": "string",
"description": "Venue slug, e.g. central-park. From find_courts."
}
},
"additionalProperties": false
}{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}Prompts
Not advertised
Resources
Not advertised
90-day uptime
A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.
- 2026-11-07: 1 of 1 checks answered
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 653 ms
- 95th percentile latency
- 653 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 653 ms · metadata changed · 4 tool(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http courts-tennis-mcp https://www.courts.tennis/mcpCodex
codex mcp add courts-tennis-mcp --url https://www.courts.tennis/mcpCursor
{
"mcpServers": {
"courts-tennis-mcp": {
"url": "https://www.courts.tennis/mcp"
}
}
}Cline
{
"mcpServers": {
"courts-tennis-mcp": {
"type": "streamableHttp",
"url": "https://www.courts.tennis/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"courts-tennis-mcp": {
"type": "http",
"url": "https://www.courts.tennis/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http courts-tennis-mcp https://www.courts.tennis/mcpClaude Desktop
https://www.courts.tennis/mcpWindsurf
{
"mcpServers": {
"courts-tennis-mcp": {
"serverUrl": "https://www.courts.tennis/mcp"
}
}
}Let your agent find its tools
Find servers like Courts.tennis MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other productivity and knowledge servers
Do you run Courts.tennis MCP?
Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.