Connect Sedule to ChatGPT
Bring your team’s scheduling tools into a ChatGPT conversation through a custom MCP connection.
Before you start
Your account and workspace must allow custom MCP connections. Check those controls with your workspace administrator if the option is missing. Have access to your Sedule sign-in email and review how permissions work.
The steps below follow OpenAI’s connection documentation, reviewed on . Account controls and menu wording can change.
Add the connection
Sedule’s public MCP endpoint is:
https://sedule.eu/mcp- Open ChatGPT Plugins. Use the plus control to add a custom MCP server.
- Name it Sedule and enter the endpoint above as the public connection URL.
- Choose OAuth authentication, review ChatGPT’s connection notice and create the plugin.
- Complete Sedule’s sign-in and permission approval when prompted, then inspect the discovered tools.
- Install the resulting connection. In a new conversation, use
@to select it.
Start without changing anything
Use Sedule to list my teams. Show their names and my roles. Do not create or change anything.
A successful tool result should identify the teams your account belongs to. An empty list can mean you have no team yet; it does not mean a new team was created automatically.
Continue to your schedule
Follow team setup if services and providers are missing, then use the first-booking guide. Select the team explicitly, review the timezone and request a write action only when ready.
If the connection fails
- No custom MCP option: check your account and workspace permissions against the linked OpenAI guide.
- Sign-in did not finish: complete the Sedule browser flow and return to ChatGPT.
- Tools are missing: inspect the discovered metadata and refresh the connection after tool changes, then start a new conversation.
- A write is refused: check both the approved scopes and your team role. Seeing tools does not grant permission to every action.
You can revoke the grant in Sedule account security. See the token-expiry explanation before assuming an already-issued token stops immediately.