search_stymie
Search courses, equipment, architects, and Stymie tools from one structured endpoint.
Live MCP server
Golf data AI agents can actually use
Connect to structured course, scorecard, architect, equipment, verified-deal, and golf-trip data across six countries through 12 read-only tools.
https://mcp-production-680d.up.railway.app/mcp26,736
golf courses
11,061
scorecards
12
read-only tools
No key
public access
Ask your AI agent
Paste one of these into ChatGPT, Claude, Codex, or another agent with web access or MCP tools. If your client needs a Stymie connection, use the endpoint above and the setup below. Replace the brackets with your preferences.
Use stymie.golf to plan my golf weekend near the Glen Ellyn Metra station in Illinois. Find two public 18-hole courses, explain your picks, and include their Stymie links.
Plan a golf weekend for me using stymie.golf: I'm near [place or ZIP], I want [public/private] courses with [18/9] holes. Rank a shortlist with distances and Stymie links.
Use stymie.golf to find public 9-hole golf near ZIP 60137. Give me three nearby options with working Stymie links and tell me what I need to confirm before playing.
How the agent plans your trip: Start with
find_nearby_courses using your place, station, or ZIP and preferences. It returns a resolved location and a nearest-first shortlist. Then use build_golf_trip with that center for up to four course picks, or search_courses to look up a course by name. Each result includes a canonical Stymie link; the agent never needs to guess a county slug. Distances are straight-line miles. Confirm tee times, private access, and transit or driving arrangements separately.Connect once
Use Stymie in an MCP client
Add the Streamable HTTP endpoint to any compatible client. Configuration formats vary, but this is the common shape. No Stymie account or API key is required.
MCP configuration
{
"mcpServers": {
"stymie-golf": {
"type": "http",
"url": "https://mcp-production-680d.up.railway.app/mcp"
}
}
}Twelve tools
From course search to complete golf trips
search_courses
Search for a named course or filter the directory by city/state, access, and holes. For a trip near a place, station, address, or ZIP, call find_nearby_courses FIRST; do not put the place name in query (query searches course names). You may also pass location here for a proximity search. Returns canonical Stymie URLs, reusable slugs, access, holes, scorecard availability, and straight-line miles when a location is supplied. Copy returned URLs; never construct county slugs. Next: get_course with a returned URL, or build_golf_trip with the resolved center and preferences.
find_nearby_courses
START HERE to plan golf near a place, transit station, address, or US ZIP: pass the place text as location, plus access (public/private/all) and holes (9/18) if known. Coordinates are optional; no slug knowledge is needed. Resolves the location and returns its labeled center and a nearest-first ranked shortlist with canonical Stymie URLs, reusable slugs, straight-line miles, access, holes, and scorecard availability. If the place is ambiguous, ask the golfer to choose a candidate. NEXT call build_golf_trip with the returned latitude/longitude and the same preferences for 1-4 course picks. Use search_courses only for a specific course name. Copy returned URLs verbatim; distances are not drive/transit times.
get_course
Get course location, access, architect, amenities, ratings, and real tee data.
get_scorecard
Get hole-by-hole par, yardage, stroke index, and tee ratings.
get_architect
Get an architect profile and courses grouped by state.
get_leaderboard
Rank a state's hardest, easiest, or longest courses.
search_equipment
Search current balls, drivers, putters, rangefinders, and launch monitors.
get_deals
Get verified in-stock equipment sales checked within the last 48 hours.
build_golf_trip
AFTER find_nearby_courses, pass its center latitude/longitude, access and holes preferences, and number_of_courses to make a 1-4 course shortlist. You can also start directly with a plain-language location (place, station, address, or US ZIP). Optional tee yardage and slope ranges rank matching tees by fit plus straight-line distance; without tee preferences, courses are nearest-first and missing scorecards are retained. Returns ranked course picks with canonical Stymie URLs, reusable slugs, selection reasons, distance, access, holes, and published tee data when available. Public access excludes unknown/private courses; private picks require the golfer to confirm access. No booking, tee-time availability, transit routing, or drive times are provided. Use returned URLs as citations without inventing slugs.
get_data_coverage
Get current course, scorecard, logo, equipment, architect, and deal counts.
search_tee_times
Get the course and alert destination while live tee-time integrations are in development.
WebMCP progressive enhancement
Structured tools inside the live Stymie tab
Supported in-browser agents can use Stymie's current page and session through the experimental WebMCP API. Browser tools appear only while Stymie is open; unsupported browsers receive the normal site with no fallback script or extra setup.
search_golf_courses
Search course listings by name, area, ZIP code, access, holes, or coordinates.
search_golf_equipment
Search sourced specifications for current golf balls, drivers, and putters.
fit_golf_balls
Rank golf balls by swing speed, handicap band, priority, budget, and shot shape.
compare_golf_balls
Compare two balls and open their canonical Stymie matchup.
recommend_tee_length
Calculate a suitable course-yardage range from driver distance and handicap.
get_current_course
Read the course, tees, amenities, and contact details on the open page.
recommend_current_tee
Choose the closest published tee on the course currently open.
save_course_to_passport
Prepare a visible Passport confirmation; nothing is saved without the golfer.
get_current_product_specs
Read sourced specs for the ball, driver, or putter currently open.
join_tee_time_waitlist
Prefill the visible early-access form and wait for the golfer to submit it.
Passport and tee-time waitlist actions always stop at a visible confirmation. Authentication, validation, and storage rules remain enforced by Stymie's existing server endpoints.
Try asking
Questions grounded in real golf data
1
Find public golf courses within 20 miles of Pinehurst, North Carolina.
2
Show me the scorecard and tee ratings for Bethpage Black.
3
Compare current drivers under $600 and include the source pages.
4
Build a two-course public-access golf trip near Scottsdale for tees around 6,200 yards.
5
What verified golf equipment deals are active right now?
6
Which public courses in Florida have the highest slope ratings?
Technical links
Inspect before you connect
Frequently asked
Stymie MCP questions
What is the Stymie MCP server?
The Stymie MCP server gives compatible AI agents structured, read-only access to Stymie golf course, scorecard, architect, equipment, deal, and golf-trip data.
Does the Stymie MCP server require an API key?
No. The public Streamable HTTP endpoint currently requires no API key or account.
Can an AI agent change data or book a tee time through Stymie MCP?
No. All tools are read-only. Live tee-time inventory and booking are not currently available. The tee-time tool returns relevant Stymie course and alert destinations.
What can an AI agent search through Stymie MCP?
Agents can search courses across the US, Canada, UK, Ireland, Australia and New Zealand, resolve places and transit stations, compare scorecards and equipment, and build public or private course shortlists. Private-course access and live tee times must be confirmed with the course.
How does Stymie handle MCP usage telemetry?
Stymie records privacy-safe operational events such as tool name, success or error outcome, duration, response size, protocol version, and client user agent. It does not log tool arguments, prompts, full IP addresses, database values, or credentials.