Ask GoMeddo Anything: Connecting Claude to Your Salesforce Scheduling

Somewhere in your Salesforce org, GoMeddo already knows which rooms are free tomorrow afternoon, how busy the sports hall was last month, and whether Dr. Jansen has a slot open this week. It's always known. Getting it to actually tell you meant opening Salesforce, picking the right view, setting a date filter, and reading a calendar.

‍

Now you can just ask.

‍

‍

What's Actually New Here

‍

GoMeddo now connects directly to Claude through the Model Context Protocol (MCP), an open standard that lets an AI assistant use external tools instead of just guessing at answers. Claude gets a small set of tools that reach into your Salesforce org, each one mapped to something GoMeddo already knows how to do: find available resources, calculate occupancy, create a reservation.

Ask a question in plain language, Claude picks the right tool, calls it, and turns the result into an answer. Your data never leaves Salesforce. Nothing gets copied anywhere. Salesforce hosts the endpoint, so there's no server for anyone to run and no integration for anyone to babysit.

‍

‍

How a Question Becomes an Answer

‍

Someone asks a question, say, "Which meeting rooms are free tomorrow between 10 and 11?" Claude picks a tool to answer it, not by searching a database, but by choosing between a handful of well-defined actions, each with a clear description of when it applies.

‍

That tool call runs the same GoMeddo automation your team already relies on: availability rules, opening hours, conflict rules, resource hierarchies, all of it applying exactly as it would in the calendar view. The result comes back as data, and Claude turns it into a sentence, a list, or a chart.

‍

Here's the part that actually matters: Claude isn't reasoning about your booking rules. GoMeddo is. If a room's blocked because a combined space above it is already reserved, the answer reflects that, not because Claude figured it out, but because it asked GoMeddo and GoMeddo said no. That's what makes the answers trustworthy enough to act on, not just plausible enough to sound right.

‍

‍

What It Can Do Today

‍

Right now, that means checking availability for a specific window while applying conflict rules, returning occupancy and utilisation for a resource over a period, proposing candidate time slots for a booking of a given length, looking up records so names resolve to the right resource, and creating a reservation, confirmation email included, exactly as the UI would.

‍

Which of these you switch on is entirely your call.

‍

‍

What You'll Need

‍

The short version: a Salesforce org on Enterprise Edition or above (Salesforce's hosted MCP servers went generally available in April 2026, Enterprise and up, Developer Edition included), GoMeddo installed alongside the GoMeddo Agentforce package, since it already contains the flow actions these tools are built on, no Agentforce licence required.

‍

You'll also need a connected app for authentication, a one-time setup that lets the assistant sign in; users authorise it themselves, and Salesforce handles auth and permissions, so the assistant reaches your data through your existing security model rather than a separate copy of it.

‍

From there, it's a server definition in Setup, where you choose which GoMeddo actions become tools and activate them, no code involved, plus a Claude plan that supports custom connectors: Pro, Max, Team, or Enterprise.

‍

Realistically, that's a short afternoon for someone who already knows their way around the Salesforce Setup, most of it spent on the authentication step.

‍

‍

What This Isn't

‍

It's not a chatbot bolted onto your calendar: there's no separate booking engine and no second copy of your availability rules, every answer comes from the same automation your staff already trusts. It's not an unrestricted query interface either.

‍

Claude can only do what the tools allow, and adding a capability is a deliberate configuration change, not something the model decides on its own. And it's not a replacement for the GoMeddo interface. Great for a quick question or a one-off booking, but managing a full term's timetable is still very much a job for the calendar.

‍

‍

Where This Is Heading

‍

Two things worth knowing right now: the server configuration currently happens per org, since Salesforce doesn't yet support shipping this wiring inside a managed package.

Salesforce has signalled that partner-packaged MCP servers are coming, which would remove that step entirely.

‍

And this isn't a bet on one assistant. The protocol is open, and the same tools work for any MCP client, not just Claude. The number of tools that speak this language is only growing.

‍

Getting Started

‍

1. Confirm your org is Enterprise Edition or above, with GoMeddo and GoMeddo Agentforce installed
2. Ask your Salesforce administrator to create the connected app and the MCP server
3. Connect it in Claude and try a question you'd normally answer by opening the calendar

‍

That's it. No migration, no rebuild, just a faster way to get an answer you already had.