GolfBelek
Product · Open Data

Belek Tee Times Inside Your AI Assistant: Our MCP Server Explained

Ask Claude what you can play in Belek on a Tuesday in October and it now answers from our live booking system rather than from memory. Here is what we built, what it does, and where the line is.

Published 2 September 2026 · 8 min read · By GolfBelek Editorial

The short version

GolfBelek.com now publishes live tee time availability and published prices as an MCP server — a small, read-only endpoint that AI assistants can call directly. Instead of scraping our pages or answering from months-old training data, an assistant asks the booking system and reports what it actually says.

https://www.golfbelek.com/mcp

It is public, needs no account, and carries no customer data. It also cannot book anything — more on that below, because the limit is deliberate.

What it looks like in practice

The difference is easiest to see in a conversation. Before, an assistant could tell you Belek has good golf and roughly what a round costs. Now it can tell you what is free on a particular morning.

“I'm in Belek from 10 to 14 October. What can I play on the 12th before 9am, and what does it cost for two of us?”
The assistant calls search_tee_times for 12 October, reads back the slots that are actually open, and answers with the course, the tee time, the green fee per player, whether a cart is included in that fee or priced separately, and a link to the booking page. Nothing invented, nothing out of date.

What MCP is, briefly

The Model Context Protocol is an open standard for letting an AI assistant call an external system. A business publishes a handful of named tools; the assistant decides when to use them and reads the answer. It is the difference between an assistant that has read about you and one that can ask you.

For a golf trip that matters more than it sounds. Availability changes daily, prices differ by course and by slot, and what a green fee includes is not uniform — on some Belek slots the buggy is in the price, on others it is an extra. Those are exactly the details a language model gets wrong when it is guessing.

The four tools

search_tee_times

Bookable slots for a given date, with the green fee per player, what that fee already includes, the price of a cart or club rental where they are extra, and a booking link. Filters by course, time window and maximum green fee.

list_golf_courses

The Belek courses bookable through the site, with the club and hotel each belongs to. Useful before searching a specific date.

get_transfer_zones

Hotel-to-course transfer prices by pickup area, from Belek itself out to Alanya and Kemer.

get_booking_info

How booking works: the two-day lead time, what a green fee covers, which extras exist, and how payment is handled.

Where the line is, and why

The server reports published unit prices — a green fee per player, each extra priced separately — and stops there. It does not compute a total for your party.

This is a design decision, not an omission. A booking total is calculated in exactly one place: the checkout on this site. Every additional copy of that arithmetic is a chance for the two to disagree, and when they disagree it is a customer who pays the difference. So the assistant tells you the unit prices and sends you to the page that prices the booking.

For the same reason it is strictly read-only. It cannot create, change or look up a reservation, and it never sees a customer record. Slots that are full, under maintenance, or reserved for package guests simply do not appear.

Connecting it

One address, no key, no sign-up, no rate limit to ask for. Paste it wherever your assistant keeps its connectors.

https://www.golfbelek.com/mcp

Below are the two clients most people ask about. Any other MCP-capable tool takes the same address.

Claude — web, desktop or mobile

  1. Open Settings from the menu under your name.
  2. Go to Connectors.
  3. Scroll past the built-in connectors and choose Add custom connector.
  4. Name it GolfBelek and paste https://www.golfbelek.com/mcp as the remote MCP server URL. Leave everything else alone — there is no authentication step.
  5. Save, make sure the toggle beside it is on, then start a new chat.

Existing conversations will not see it. Connectors are loaded when a chat begins, so the first question has to be asked in a fresh one.

ChatGPT — custom connector

ChatGPT reaches MCP servers through its connector system as well, with two extra conditions: it is a paid-plan feature, and custom servers sit behind a setting you have to turn on first.

  1. Open Settings → Connectors.
  2. Under Advanced settings, enable Developer mode. Custom MCP servers stay hidden until you do.
  3. Back on the Connectors page, choose Create to add your own.
  4. Fill in a name (GolfBelek), a short description, and https://www.golfbelek.com/mcp as the MCP server URL. For authentication pick No authentication.
  5. Create it, then in a new chat open the tools menu beside the message box and switch GolfBelek on for that conversation.

If you cannot find it: OpenAI moves these menus around, and on some business or enterprise accounts an administrator has to allow custom connectors before they appear at all. The address never changes, so once you find the right screen the rest is one paste. OpenAI's own connector documentation is the authority on the current menu names.

Try it with these

Whichever client you used, these five are a quick way to see whether it is really reading our data rather than guessing:

The last one is the giveaway. A guessing assistant will say yes; one that is actually talking to us will tell you rounds are bookable from two days out, and name the earliest date you can still take.

For developers

TransportStreamable HTTP, POST only
Protocol versions2026-07-28 (current) through 2025-03-26, including the older initialize handshake
AuthNone
SessionsNone — every call is independent
CurrencyEUR
Lead timeTee times are bookable from two days out

To check it from a terminal before wiring it into anything, the reference inspector speaks to it directly:

npx @modelcontextprotocol/inspector --cli https://www.golfbelek.com/mcp --transport http --method tools/list

The endpoint is also listed in our AGENTS.md and llms.txt, alongside pricing.md, so an agent that lands on the site can find it without being told.

Why we bothered

More and more trips start in a chat window rather than a search box. When someone asks an assistant about golf in Belek, the assistant answers either way — the only question is whether it answers from our live system or from whatever it half-remembers.

Publishing the data is also simply cheaper than being scraped. One clean endpoint, one source of truth, and a booking link at the end of every answer.

Something wrong in an answer? If an assistant quotes a price or an availability that does not match the site, the site is right — and we want to know. Write to [email protected].

Questions we have already been asked

Can it book for me?

No. It is read-only by design. Booking happens on the tee times page, where the total is confirmed and payment is taken.

Do I need an account?

Not for the server. It only serves what is already public on the site. You will need one to book.

Is my data going anywhere?

No customer data passes through it. It answers questions about courses, times and prices, and nothing else.

Will the prices always match the site?

They come from the same system the site reads, so yes for unit prices. Totals are only ever calculated at checkout, which is why the server does not quote one.

Related reads