> ## Documentation Index > Fetch the complete documentation index at: https://docs.overlap.ai/llms.txt > Use this file to discover all available pages before exploring further. # Overlap MCP > Use Overlap workflows, clips, Social Calendar, and analytics from an MCP-compatible AI client. Overlap MCP is a user-level connection between Overlap and compatible AI clients. Connect once to use your current role across every Overlap organization you belong to. It lets an assistant discover and run workflows, find clips, make guarded clip or transcript changes, start renders, review the Social Calendar, and analyze published content. Supported clients register automatically, so you do not copy OAuth client IDs or secrets. There is no per-organization AI Agents activation and no subscription-plan requirement. ## Server address Use the remote Streamable HTTP server: ```text theme={null} https://mcp.overlap.ai/mcp ``` The MCP connection uses Clerk OAuth. Existing Overlap REST API keys continue to work with the existing REST API, but they are not used to authenticate MCP clients. ## What it can access The organization selected during OAuth becomes the default, not the access boundary. `overlap.organizations.list` shows all current Overlap memberships and their organization IDs. Organization-scoped tools accept `organization_id` to target another membership without reconnecting. An organization ID only selects where a tool should run; it does not grant access. Overlap rechecks the signed-in user's current Clerk membership and role before targeting another organization, so removing a membership or changing a role takes effect without reconnecting. Depending on your role and the permissions approved during connection, you can: * search workflows, clips, posts, and product documentation * run workflows and follow their progress * read and update clips or transcripts, then request a render * inspect connected social accounts and the Social Calendar * create or edit unapproved social drafts * publish an immediate draft after explicit written consent in the conversation * compare social performance and identify trending posts ## Safety model Read operations happen immediately. Workflow launches require explicit written consent. External actions such as publishing immediately, cancelling authorized work, or running a workflow that creates Social Calendar drafts also require an immutable preview before that consent is accepted. The assistant shows the exact action, destination, copy, media, time, and relevant effects in chat and waits for your written response. It never opens a browser for action confirmation. The write tool requires the matching one-use confirmation ID and your consent text together; a standalone model-generated value such as `confirmed: true` is not accepted. ## Current boundaries Catalog groups can be rolled out or disabled with service-wide kill switches, but customers do not activate MCP separately for each organization. Once a user connects MCP, every current Overlap membership is available subject to that user's role and the tool's normal permission requirements. When workflow access is enabled, social Share nodes can create approval-required drafts only and require both workflow-run and calendar-write scopes. Email, iHeart, BrandLive, and unknown external-effect nodes remain unavailable through MCP. Future scheduled publishing is intentionally unavailable until Overlap can revalidate the exact account and media revision at provider time; scheduled drafts remain unapproved planning items. The beta also does not expose raw internal media workers, API-key management, social-provider credentials, arbitrary binary uploads, bulk calendar clearing, live analytics refreshes, or iHeart mutations. Editing-agent commands will be added after their durable HTTP operation interface completes beta validation.