Ask your AI Assistant about your Production
You can connect AI assistants such as Claude and ChatGPT directly to Yamdu. Once connected, your assistant answers questions about your productions using live data from Yamdu - shooting schedules, call sheets, script breakdown, crew, time cards, budgets and more. You ask in plain language and the assistant looks the answer up in Yamdu for you.
The connection is strictly read-only: Your assistant can look things up in Yamdu, but it can never create, change or delete anything.
What you Need
Your company's Yamdu subscription must include the MCP Server (AI Connections). If you are unsure that this is activated, ask your Yamdu company admin or contact us.
A company admin has switched on Allow MCP server connections in the Yamdu company settings (this is off by default).
An AI assistant plan that supports connectors. For Claude: Pro, Max, Team or Enterprise. For ChatGPT: Plus, Pro, Business, Enterprise or Edu.
Your normal Yamdu login information as you will need to sign in with it during setup.
Connect with Claude
You can find a guide for creating custom connectors with Claude here:
When adding a custom connector, enter Yamdu as the name and this URL:
https://api.yamdu.com/ai/mcp
Connect with ChatGPT
You can find a guide to setting up an MCP with ChatGPT here:
When adding a plugin, enter Yamdu as the name and this URL:
https://api.yamdu.com/ai/mcp
What your Assistant Can See
Depending on what your company admin has enabled, your assistant can read the following areas of your productions:
Area | What the assistant can look up |
Projects | Your company's projects and their key facts — the starting point for every question |
Script breakdown | Scenes, characters, sets, props and scene attributes, costumes, VFX, stunts, sound — including a search across the whole breakdown |
Scheduling | Shooting schedules (day by day), shoot days, production calendars |
Call sheets | Complete call sheets including individual call times, locations and weather |
People | Project crew list, cast, your company's actor and location databases |
Time cards | Daily time cards, aggregated totals, labor agreements |
Budget | Budget scenarios from topsheet down to individual entries |
Three boundaries always apply:
Read-only: The assistant can never change anything in Yamdu.
Your company's rules: Admins decide which data areas, which projects, and whether sensitive personal data may be read at all. These limits apply to every connection in the company.
Your consent: The assistant only gets what you approved on the permission screen, and only sees data your own Yamdu account can access.
Example Prompts to Try
"Which productions do we currently have in Yamdu?"
"When do we shoot next week, and which scenes are planned on each day?"
"On which shooting days do we need the prop 'Old Map'?"
"What's my call time on Thursday, and where do I need to be?"
"Summarize last week's time-card hours by department."
"Walk me through the topsheet of our current budget scenario."
Tip: name the production in your first question ("…in the project Love at Sunset") — after that, the assistant remembers the context.
Managing and Revoking Access
As a user: open your Yamdu User Settings → Connected AI apps. You see every AI app you have connected, when it was connected and last used, and what it may read. Click an app and choose Disconnect to revoke its access at any time (it may keep working for up to 10 minutes until its current session expires).
As a company admin: the MCP server section in the company settings controls all connections of your company: switch them on or off entirely, restrict them to specific projects, choose the readable data areas, and decide whether sensitive personal data is included. Every change to these settings is recorded in the activity log.
Security and Privacy
You sign in on Yamdu's own login page (OAuth 2.1). Your Yamdu password is never shared with Anthropic, OpenAI or any other AI provider. Single sign-on and two-factor authentication apply as usual.
All access is read-only: There is no way for an assistant to modify production data.
Access is limited twice over: By your company's MCP settings and by your own account's permissions.
You can disconnect any app at any time, and admins can switch off all connections centrally.
What the AI provider does with data you retrieve is governed by its own terms; what Yamdu does is described in our privacy policy.
Troubleshooting
Problem | What to do |
Connecting fails right after adding Yamdu | Your company's subscription may not include MCP Server (AI Connections), or an admin hasn't switched on Allow MCP server connections yet. Ask your Yamdu company admin. |
The assistant says it isn't allowed to read something | That data area isn't enabled in your company's MCP settings — an admin can enable it there. |
A project is missing from the answers | Either the project isn't on your company's allowed list for AI connections, or your own Yamdu account doesn't have access to it. |
You're asked to sign in to Yamdu again | Connections expire after about two weeks without use. Just sign in again — nothing else changes. |
ChatGPT: you can't create a custom connector | Developer mode isn't enabled, or (on Business/Enterprise) your workspace admin hasn't allowed custom connectors yet. |
Times in answers look off | The assistant receives exact times including time zones. Ask it to state times in your local time zone or in the shooting location's time zone. |
For Developers and other AI Tools
The Yamdu MCP server is a standard remote MCP server (Streamable HTTP, OAuth 2.1 with dynamic client registration) at https://api.yamdu.com/ai/mcp. Any MCP-capable client — Claude Code, Cursor, VS Code with GitHub Copilot and others — can connect the same way: add the URL, simply by signing in with your Yamdu account. The underlying REST API and its reference documentation are described in the Yamdu Third-Party API documentation.
Tools
Area | Tool | What it returns |
Connection | whoAmI | Which account and company the connection belongs to, and which permissions were granted |
Company | projectsOfTheCompany | All projects of the company — the entry point for everything else |
Company | creativeWorksOfTheCompany | The accessible projects as Creative Works (OMC entry point) |
Company | locationsOfTheCompany | The company's real-world location database (addresses, geo data, time zones) |
Company | actorsOfTheCompany | The company's cast and extras database |
Scheduling | allShootingSchedulesOfAProject | The shooting-schedule versions of a project |
Scheduling | specificShootingSchedule | One schedule version as the full day-by-day plan |
Scheduling | shootingDaysOfAProject | Shoot days with their scheduled scenes |
Scheduling | allProductionCalendarsOfAProject | The production-calendar versions (prep/shoot/post timeline) |
Scheduling | specificProductionCalendar | The steps and phases of one production calendar |
Call sheets | allCallSheetsOfAProject | The call sheets of a project |
Call sheets | specificCallSheet | One complete call sheet incl. individual call times, locations and weather |
People | crewListOfAProject | The project crew list (team members and external contacts) |
People | participantsOfAProject | Cast members and production units of a project |
Time cards | timeCardsOfAProject | Daily time cards (hours, meals, penalties, approval state) |
Time cards | aggregatedTimeCardTotalsOfAProject | Rolled-up time-card totals per person, week or month |
Time cards | laborAgreementsOfAProject | The time-card calculation rules per crew or cast member |
Budget | allBudgetScenariosOfAProject | The budget scenarios of a project |
Budget | specificBudgetScenario | One budget scenario from topsheet down to individual entries |
Script breakdown | narrativeScenesOfAProject | Script scenes with slugline, description and referenced elements |
Script breakdown | charactersOfAProject | Characters, who plays them, and the scenes they appear in |
Script breakdown | narrativeLocationsOfAProject | Story locations (sets) with their scenes |
Script breakdown | narrativeWardrobesOfAProject | Costumes with the scenes they feature in |
Script breakdown | narrativeObjectsAndSceneAttributesOfAProject | Props and scene attributes with their scenes |
Script breakdown | effectsOfAProject | Visual and special effects |
Script breakdown | specialActionsOfAProject | Stunts and special actions |
Script breakdown | narrativeAudioItemsOfAProject | Narrative audio and sound items |
Script breakdown | productionLocationsOfAProject | The real-world shooting locations linked to a project |
Script breakdown | productionScenesOfAProject | Production scenes and shots — the bridge between scenes and shoot days |
Script breakdown | crossEntitySearchOverTheScriptBreakdownOfAProject | Search across characters, locations, wardrobe, props, scene attributes and scenes |