Bringing AI to Your Golf Game: Fairway Goose

I teased a golf platform a while back — here it is. Fairway Goose is a golf bag management tool built MCP-native from day one, so your AI assistant can actually talk to your bag.

Carter HolmesPosted on April 15, 2026·7 min read
AI
Golf
MCP
Model Context Protocol
Development
Bringing AI to Your Golf Game: Fairway Goose

Meet Fairway Goose

I teased this one a while back — here it is.

A while back I teased a golf platform I was building. I kept it vague on purpose — I wasn't sure what it was going to be yet. Now I do.

Meet Fairway Goose.


What Is Fairway Goose?

Not a new app. A caddie inside the ones you already use.

Here's what I want to be clear about upfront: I didn't build a platform.

I didn't build another app for you to download, create an account on, learn the UI of, and eventually forget about. There are enough of those. What I built is a caddie — one that lives inside Claude, ChatGPT, and any other AI assistant that supports MCP.

Fairway Goose is a golf management tool built entirely around MCP — the Model Context Protocol. Your bag setup, your clubs, your yardages, your rounds — all of it lives in Fairway Goose, and all of it plugs directly into the AI tools you're already using. Your assistant can read it, reason about it, and act on it — in plain conversation.

If you're already talking to Claude or ChatGPT every day, Fairway Goose just makes your caddie smarter. You don't go anywhere new. You just ask.


What Is MCP and Why Should You Care?

USB for AI — and your bag is the device.

If you missed my last article on MCP, the short version is this: MCP is a standard that lets AI models connect to external tools and data sources. Your devices don't care what brand of cable you use — they just need a standard port. MCP is that port for AI assistants.

Before MCP, AI chatbots were essentially isolated. You could ask them questions, but they had no way to reach out and interact with real systems in a consistent, trustworthy way. MCP changes that. Now, a properly connected assistant can read your data, take actions on your behalf, and respond in context — all from a natural conversation.

Fairway Goose was designed from the start to be MCP-native. That's not an add-on or an afterthought. It's the whole point.


How It Actually Works

You connect it once. Then you just talk.

Open Claude or ChatGPT. Connect the Fairway Goose MCP server. That's the setup — it takes about two minutes and you don't touch it again.

From there, your AI assistant knows your bags and your rounds. You can ask things like:

Your bag:

  • "What clubs are in my Rollout bag?"
  • "From 155 yards with a slight headwind, what should I hit?"
  • "How does my 4-hybrid gap compare to my 5-iron?"

Your rounds:

  • "I shot 88 yesterday — can you pull up that round and summarize how I played?"
  • "Help me plan a practice session based on the clubs I carry most."

And the assistant just… handles it. No navigating menus. No hunting for the right screen. No switching apps. You're already in Claude or ChatGPT — now those tools know your equipment and your game.

That's the whole idea. The caddie comes to you.


Who Is This For?

Any golfer who already uses AI — and a few who don't yet.

You don't need to be a scratch golfer. You don't need to be a developer. If you have more than one setup — a walking bag and a cart bag, a travel set, clubs you rotate in and out — Fairway Goose gives you something useful to ask about.

For golfers who are already living in Claude or ChatGPT daily, this is a natural fit. It's a tool that meets you exactly where you already are. And for golfers who haven't gotten into AI assistants yet, this is a pretty low-stakes reason to try.


Where It's Headed

The caddie gets smarter over time.

Right now, Fairway Goose is in active development. The core bag management is live, the MCP integration works, and I've been using it myself to manage my own setups. It's not finished — there's a lot I still want to build — but the foundation is solid.

A few things on the roadmap:

  • Round tracking and performance notes tied to specific loadouts
  • Club recommendations based on what's in your bag and what's missing
  • Sharing setups with other golfers

As the AI ecosystem matures, the caddie gets smarter. More tools, more context, more usefulness — without ever asking you to open a new tab.


MCPs Aren't Just for Work

The protocol doesn't care what you point it at.

Most of the MCP conversation lately is dominated by productivity. Connect your GitHub. Query your database. Summarize your emails. Pull your Jira tickets into context. That stuff is genuinely useful — I use it myself.

But there's an assumption baked into that framing: that MCPs are a work thing. A serious-person tool for serious-person problems.

Fairway Goose is my pushback on that.

The protocol doesn't care what you point it at. You can point it at your Jira board or you can point it at your golf bag — the standard works either way. And honestly? Connecting an AI assistant to something you actually enjoy — a hobby, a game, something with zero stakes — is a great way to understand what MCP actually feels like in practice. There's no pressure. If your caddie gives you a weird answer, you laugh and move on.

I think that's worth something. Not every use of AI has to be optimizing a workflow or shaving time off a task. Sometimes it's just building a smarter environment around the things you love doing.

Golf happens to be one of mine — and this was a chance to make it a little more interesting.


Come Try It

I'm looking for real golfers to kick the tires.

If you play golf and you already use Claude or ChatGPT — or you're curious what an MCP-powered tool actually feels like in the wild — I want you involved.

I'm opening up early access to a small group of testers right now. No commitment, no pressure. Bring your setup, connect your bag, and tell me what works, what's confusing, and what you wish it could do. The feedback from this early group will shape what Fairway Goose becomes.

Head to fairwaygoose.com to check it out and get a feel for what it is. But if you actually want to try it, reach out to me directly — through the site, LinkedIn, wherever you find me — and I'll get you in.

And if you're a developer who thinks this kind of MCP-native approach is interesting — for golf or for something else entirely — I'd love to talk about that too.

More to come.

CH

Written by

Carter Holmes

Software Developer • 7 years of experience