We've always believed Studio Assistant should be more than a tool you log into. It should be infrastructure your tools can talk to. Today, we're taking a significant step in that direction with our Model Context Protocol (MCP) server.

What is MCP?

MCP is an open standard that lets AI agents connect to external services as tools. Instead of a human clicking through a UI, an AI agent can call those same actions on a user's behalf — searching for studios, checking availability, requesting bookings, sending quotes, and managing projects.

If that sounds abstract, here's what it looks like in practice: you tell Claude "I need a room in Nashville next Tuesday afternoon for a vocal session," and Claude checks availability, presents options, and creates the booking. No tabs. No forms. Just conversation.

Why we built this

The way people interact with software is changing. AI assistants are becoming a primary interface for getting things done. We didn't want to wait for that shift to happen to us — we wanted to make sure Studio Assistant was ready for it.

But more importantly, we believe infrastructure should be accessible. If an AI agent can do what a human can do on our platform, that means our platform is well-structured, well-documented, and well-designed. MCP is a test of that, and we think we passed it.

How it works

Our MCP server exposes twenty-two tools covering the full booking flow:

• Find studios and search by location, equipment, or availability
• Check availability with preferred start and end times
• Request, create, and approve bookings
• Manage projects and sessions
• Send quotes and contact studios
• List organizations and manage session data

Authentication is handled through self-service API tokens, OAuth 2.0 with PKCE, or email code flow — depending on the client. Users generate and manage their own tokens from Account Settings, with optional expiry dates.

Who is this for?

Right now, this is for early adopters. If you're a studio that already uses AI assistants in your workflow, or a builder who scripts custom integrations, this is for you. If you're not sure what MCP is, that's fine — the web app hasn't changed, and everything works the way it always has.

We don't host or manage AI agents for our customers. This is infrastructure you connect to. But the connection is straightforward, and we're here to help if you want to get started.

What's next

The booking form already renders as an interactive widget inside ChatGPT. Other tools return text for now, but we're expanding the interactive surface over time. We're also exploring additional transports and auth flows based on what we hear from early users.

If you're using AI agents in your studio workflow, we'd love to hear from you. The most useful features get prioritized based on real demand.

Want to connect your AI agent to Studio Assistant? Contact us and we'll help you get set up.