Daily
Daily provides WebRTC video and audio APIs for creating rooms, meetings, recordings, live streams, transcriptions, and telephony experiences.
Verdict
Common use cases
- Spin up client demo rooms on demand
- Issue expiring tokens for external guests
- Check who's in the standup call
- Batch-create breakout rooms for workshops
- Delete old rooms after project wrap
Integration
- Vendor
- Daily
- Category
- other
- Auth
- API_KEY
- Tools
- 11
- Composio slug
daily
Tools
- Batch Create Rooms
Create 1 to 1,000 Daily rooms in one atomic request. If any room fails, Daily creates none of the rooms. Paid media, telephony, storage, and callback settings are intentionally not exposed.
- Create Meeting Token
Issue a time-bounded meeting token for one Daily room and participant. The returned token grants room access and must be handled as a secret.
- Create Room
Create a named Daily room with privacy and optional safe meeting defaults. Paid media, telephony, storage, and callback settings are intentionally not exposed.
- Delete Roomdestructive
Permanently delete one Daily room by name. Use only after confirming the target; active participants may be disconnected.
- Get Domain Config
Return the connected Daily domain identity and stable account capability signals. Use this before attempting features that may be disabled or entitlement-gated.
- Get Room
Return a Daily room's current privacy and configuration by room name.
- Get Room Presence
Return the current participants visible in one Daily room, optionally filtered by user ID or display name.
- List Meetings
Return one page of Daily meeting-session analytics, filtered by room, time range, or session state. Pass next_cursor unchanged to continue.
- List Rooms
Return one reverse-chronological page of Daily rooms. Pass next_cursor unchanged to continue with the same filters.
- Update Room
Update a Daily room's privacy or safe meeting defaults. Only supplied fields change; paid media, telephony, storage, and callbacks are not exposed.
- Validate Meeting Token
Validate a Daily meeting token and return its effective room and participant settings without joining a call.
Setup
Setup guide
- 11. Open your Switchy workspace settings and click Integrations. 2. Find Daily in the MCP catalog and click Connect. 3. You'll be prompted to paste a Daily API key — generate one at dashboard.daily.co under Developers > API Keys with full read-write scope. 4. Paste the key and click Save; Switchy validates it by fetching your domain config. 5. Open any Project and type '@Daily get domain config' to confirm the connection returns your account details. 6. Try '@Daily create room name=test-room privacy=public' to create a room; you'll see the room URL in the response. 7. If the test succeeds, you're ready to invoke any of Daily's 11 tools by @mentioning Daily and naming the tool.
What teammates see: by default, memories from Daily are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Client Room
@Daily create a room named client-kickoff-2024 with privacy set to private, then show me the room URL
Issue Guest Token
@Daily create a meeting token for room client-kickoff-2024 that expires in 2 hours and allows the user to join as a guest
Check Room Presence
@Daily get the presence for room daily-standup and show me the display names of everyone in the call right now
Batch Create Breakouts
@Daily batch create 5 rooms named workshop-breakout-1 through workshop-breakout-5, all with public privacy
List Recent Meetings
@Daily list meetings for room client-kickoff-2024 from the last 7 days and show me the session start times and participant counts
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Daily list all participants currently in the 'standup-2024' room and show their connection status
The 'standup-2024' room currently has 3 active participants: Alice Chen (connected 4m ago, audio/video enabled), Bob Martinez (connected 2m ago, audio only), and Chris Park (connected 30s ago, joining). No participants are in a disconnected or error state. This snapshot reflects presence at query time and may change as participants join or leave.
This example uses Get Room Presence to surface real-time participant state. Useful for monitoring live meetings or debugging connection issues. Requires the room to exist and the API key to have read access to presence data. Presence is eventually consistent; rapid joins/leaves may show stale data for 1-2 seconds.
@Daily create a new private room called 'client-demo-jan15' with a 2-hour expiration and generate a meeting token for presenter@example.com
Created private room 'client-demo-jan15' with a 2-hour expiration starting now. The room will auto-delete at 3:45 PM UTC. Generated meeting token for presenter@example.com valid until room expiration. Token: mtk_abc123xyz... (handle as secret). Participants without a token cannot join this private room. Share the token securely with the intended presenter.
This example chains Create Room and Create Meeting Token to provision a secure, time-limited meeting space. Demonstrates access control via privacy settings and token-based auth. The token is sensitive and should never be logged or shared publicly. Expiration enforcement depends on Daily's server clock; client-side time drift won't extend access.
@Daily pull the last 7 days of meeting analytics for rooms starting with 'team-' and summarize total session count and average duration
Retrieved 42 meeting sessions across 8 rooms matching 'team-*' prefix from Jan 8-15. Total session count: 42. Average duration: 28 minutes. Longest session: 'team-planning' at 1h 47m on Jan 12. Shortest: 'team-coffee' at 3m on Jan 10. Note: Analytics reflect completed sessions only; in-progress meetings are excluded. Use next_cursor if more than one page of results exists.
This example uses List Meetings with time and room filters, then applies AI reasoning to compute summary stats. Showcases how the MCP's structured analytics pair with Switchy's synthesis layer. Pagination is manual—if Daily returns next_cursor, you must explicitly request the next page. Session data may lag by 5-10 minutes after a meeting ends.
Use-case deep-dives
When Daily wins for scheduled 1:1 customer calls
A 6-person customer success team runs 40-60 onboarding calls per week, each scheduled in Calendly and delivered through a unique video link. Daily's batch room creation and meeting token tools let you pre-provision rooms in one request and issue time-bounded tokens at schedule time, so each customer gets a single-use link that expires after their slot. The Get Room Presence tool surfaces who joined and when, feeding your CRM without manual logging. This setup works cleanly until you hit 200+ calls per week—at that scale, you'll want Daily's webhook callbacks for real-time join events, which this MCP intentionally omits. If your onboarding flow is already in Switchy and you need programmatic room control without standing up a webhook listener, Daily is the right call.
Daily for recurring team standups with rotating hosts
A 12-person engineering org runs daily standups across three squads, each with a rotating facilitator who needs host privileges. Daily's Create Meeting Token tool lets you issue a host-level token to today's facilitator and participant tokens to everyone else, all pointing to the same persistent room. The Get Domain Config tool confirms your account supports the privacy and recording settings you need before the first standup. The List Meetings tool pulls session analytics after the fact, so you can track attendance trends without asking people to self-report. This pattern breaks down if you need mid-call recording control or live transcription—those features require Daily's paid tiers and aren't exposed in this MCP's simplified toolset. If your standup cadence is stable and you're fine with post-call analytics, Daily handles the access control cleanly.
When Daily fits ad-hoc support video escalations
A 4-person support team escalates 10-15 tickets per week to live video when async chat stalls. Daily's Create Room and Create Meeting Token tools let you spin up a room and send the customer a time-bounded link in under 5 seconds, no pre-scheduling required. The Delete Room tool cleans up after the call so your room list doesn't bloat. The Get Room Presence tool confirms the customer joined before your agent hops in, avoiding the awkward empty-room wait. This works until your ticket volume crosses 50 escalations per week—at that point, you'll want Daily's SIP or PSTN integrations for customers who can't join browser video, and this MCP doesn't expose telephony config. If your escalations are browser-only and you need instant room provisioning tied to your ticket workflow, Daily is the move.
Frequently asked
What does the Daily MCP let me do in Switchy?
It creates and manages Daily video rooms, issues meeting tokens for participants, and checks who's currently in a call. You can batch-create up to 1,000 rooms at once, delete rooms, and pull meeting-session analytics filtered by time or room. It doesn't expose paid features like telephony or recording storage—those stay in Daily's dashboard.
Do I need a Daily paid plan to use this MCP?
You need a Daily account and an API key with room-creation permissions. The MCP works on free and paid Daily plans, but some features—like certain privacy settings or domain capabilities—depend on your Daily entitlement tier. Run Get Domain Config first to see what your account supports before trying gated features.
Can the Daily MCP start or record a meeting for me?
No. It creates rooms and tokens, but it doesn't join calls, start recordings, or manage in-meeting features like screen-sharing. To record or access telephony, you configure those in Daily's dashboard, then the MCP can create rooms that inherit those settings. For live meeting control, use Daily's client SDKs directly.
How is this different from calling Daily's REST API myself?
The MCP wraps Daily's API in natural-language tools, so you describe what you want instead of writing HTTP requests. You get batch operations and presence checks without parsing JSON responses. If you already have Daily API scripts or need webhook callbacks, keep using the API—the MCP is for conversational room management, not automation pipelines.
Who on my team should connect the Daily MCP?
Whoever holds your Daily API key and creates rooms for customer demos, support calls, or internal standups. The key grants room-creation and deletion rights, so treat it like admin access. If multiple people need to spin up rooms, share one Switchy connection or issue separate Daily keys and connect each individually.