New widgets, Extend schedule and AI agents in YOGO
Three new things have landed in YOGO, and they all point the same way: the system should feel more like your own. Your booking widgets can now be styled even further to match your brand, you can extend entire schedules into the future in one go, and with YOGO's new MCP server you can query your own data in plain language and build agents on top of it.
The short version
- Widgets v2. Brand colours, corners, shadows, text size, spacing and images are all controlled in YOGO admin under Design.
- Extend schedule. Selected classes are created forward in time in one go, with a preview that shows conflicts before you save.
- YOGO MCP server. Query your data in plain language through an AI client, and build agents that act on a trigger.
Booking widgets that match your brand
Widgets v2 lets you style YOGO's booking widgets to match your studio brand: colours, corners, shadows, text size, spacing and images are set in YOGO admin under Design.
When you pick a yoga studio booking system, the widget is the part customers actually see. It is often the first thing a new customer meets on your website. When it looks like a foreign box dropped into the middle of the page, you lose some of the trust the rest of the site has built. Widgets v2 removes that jump. YOGO is a yoga studio booking system and membership system for yoga studios, pilates studios, gyms, saunas and wellness businesses, and the widget should look like yours, whichever of those you run.
What you can style
Widgets v2 gives you five groups of settings, covering the things that usually make a widget stand out from the page.
- Brand colours. Accent, links, buttons, background and text are set separately.
- Corners and cards. Sharp, soft or fully rounded corners. Cards with a shadow, with a border, or completely flat.
- Text and spacing. Text size plus density and padding, so the layout gets as compact as you want it.
- Images per widget. Bleed, where the image fills all the way to the edge, or inset with a margin around it.
- Transparent background. Your own page background can show through, so the widget sits in the surface of the page instead of on top of it.
The settings live in YOGO admin under Design. Same widget, same data — you decide how it looks.
Bonus: hide cancelled classes
The schedule widget has a new setting that hides cancelled classes, so the schedule on your website only shows what people can actually book.
Cancelled classes belong in your own overview, not on your front page. With the setting on, the schedule gets shorter and easier to read for someone who just needs a slot tomorrow. In admin, cancelled classes stay where they have always been.
How to get v2
New YOGO customers get widgets v2 automatically from the start, and existing customers switch over whenever it suits them.
- New customers. V2 is on from day one, so there is nothing to do.
- The WordPress plugin. V2 is activated when you update the plugin. Then tick "Switch to modern widgets".
- Other setups. Write to YOGO at yo@yogo.dk and we will open the new widgets on your account.
The script code is ready in YOGO admin under Design, so you can drop it into your website right away. The old widgets keep working and there is no deadline. If you need class booking software on several pages, you can set up different widgets with their own look, for example one for yoga, one for pilates and one for fitness. See also all features in YOGO.
Extend schedule, instead of copying class by class
Extend schedule creates selected classes forward in time in one go, instead of you copying them one at a time. The feature sits in the schedule menu in YOGO.
What the problem was
A fixed weekly schedule that needs another season used to mean a long series of manual copies. Fifteen classes a week times twelve weeks is 180 repetitions of the same action, and that is the kind of work where a class gets dropped and nobody notices until a customer asks. Extend schedule turns it into one action: pick the classes, pick how far forward, save.
What the preview shows
The preview in Extend schedule shows four things before you save: what will be created, what already exists, what would land in the past, and where conflicts would appear.
The preview flags every class before you save: what gets created, what already exists, where it overlaps, and what would land in the past.
The last one is where the time usually goes. A conflict you catch in the preview is two clicks. The same conflict, caught by a teacher standing in the wrong room, is a phone call and an apology to a full class.
AI agents and YOGO's MCP server
YOGO's MCP server gives an AI client access to your studio data in YOGO, so you can ask questions in plain language and get answers straight away. On top of that same access you can build agents that act on their own from a scenario you define.
What an MCP server is
MCP stands for Model Context Protocol and is the standard AI clients use to reach tools and data. YOGO's MCP server runs on mcp.yogobooking.com/mcp and exposes every REST endpoint in the YOGO API as an MCP tool. In practice that means the client works out for itself which data it needs to fetch. You do not need to know the API, and you do not need to find the right report first.
Data is pulled across YOGO: customers, bookings, memberships, classes and orders.
What you can ask
You can ask YOGO's MCP server about anything held in your data, phrased the way you would say it to a colleague.
list_bookings · list_customers142 customers above 100 bookings. Want me to find the ones who have not booked in the last 30 days?
The client finds the relevant data in YOGO by itself. You write the question in plain language.
From question to agent
An agent is the difference between asking and getting something done. It connects to the API, runs on a trigger or a schedule, and acts on its own from the scenario you have defined — without anyone typing a question each time.
If the agent has access to tools beyond YOGO, your data can feed into larger workflows. A weekly summary that lands in your own system, for example, or loyal customers passed automatically to email marketing.
For example: push your most loyal customers to your CRM or email marketing, or pull numbers into your BI tool every morning.
Three questions studios tend to ask first:
- "Which members have not booked a class in the last 60 days?"
- "Which classes had the highest occupancy over the last three months?"
- "Show me customers with an active membership who have not booked in the last month."
These are questions that used to need a report, an export and some time in a spreadsheet. Now they are one sentence.
What it costs
The YOGO API and the MCP server are an add-on at 79 EUR per month on the Studio and Studio+App plans.
The server is EU-hosted and GDPR-compliant, and the API key can be switched off again with one click. If you are unsure which plan you are on, you can check it in YOGO admin under Settings. See also prices and plans. The guides live in the help centre.
Frequently asked questions
What is YOGO's MCP server?
YOGO's MCP server is a server that gives an AI agent access to your data in YOGO through the Model Context Protocol. It runs on mcp.yogobooking.com/mcp and exposes every REST endpoint in the YOGO API as an MCP tool. The agent works out which data it needs on its own, so you can ask in plain language instead of knowing the API.
Can you use AI to analyse data from your booking system?
Yes. With YOGO's MCP server an AI client can pull data on customers, bookings, memberships, classes and orders and answer questions straight away. A typical question is "Which classes had the highest occupancy over the last three months?". If the agent has access to other tools, YOGO data can feed into larger workflows.
Which AI clients work with YOGO?
YOGO supports Claude Desktop, Claude Code and Gemini CLI today. ChatGPT and Claude.ai in the browser are not supported yet, as they require OAuth 2.1, which YOGO is working on. The client connects to mcp.yogobooking.com/mcp using an API key from YOGO admin.
What does the YOGO API cost?
The YOGO API is an add on at 79 EUR per month on the Studio and Studio+App plans. The price covers both the REST API and the MCP server, which use the same API key. The key is created in YOGO admin under Settings and can be switched off again with one click.
How do you customise booking widgets to your own brand?
In YOGO admin under Design you set brand colours for accent, links, buttons, background and text, choose sharp, soft or rounded corners, decide whether cards have a shadow, a border or are completely flat, and adjust text size, density and padding. Images can be shown as bleed or inset per widget, and the background can be made transparent.
How do you extend a whole schedule forward in time?
Use Extend schedule in the schedule menu in YOGO. You pick the classes to extend and how far forward they should be created. The preview shows which classes will be created, which already exist, which would land in the past, and where conflicts such as a double booked room or teacher would appear.
Do you need to be a developer to use the YOGO API?
No. If you use the MCP server you ask questions in plain language, and the client works out which data to fetch. Setup is an API key from YOGO admin plus a supported client. Building a full integration against the REST API does require developer help.
Is the YOGO API GDPR compliant?
Yes. The YOGO API and MCP server are EU hosted and GDPR compliant. All writes are recorded in an audit log, so you can see what changed and when. The API key is created in YOGO admin under Settings and can be deactivated with one click.
Try it today
All three features are live in YOGO now. If you do not have an account yet, create a free one and look at the widgets, the schedule and the rest from the inside. Questions about the API or MCP go to yo@yogo.dk.