Skip to main content
Overlap MCP tools are grouped by user goal. The client supplies typed inputs, while the server verifies the signed-in user’s live membership in the requested organization and enforces roles, revisions, and confirmation requirements.

​
Context and discovery

  • overlap.organizations.list — list all current Overlap memberships and their organization IDs
  • overlap.context.get — target organization, current role, and available capabilities
  • overlap.search — paginated search across supported Overlap entities
  • overlap.docs.search — search the current Overlap documentation catalog
Organization listing makes one user-scoped Clerk membership request and does not fan out into one API request per organization. It returns an organizationId, display name, current role, and available tools. Pass that value as organization_id to any organization-scoped tool. If omitted, the tool uses the organization selected during OAuth as the default. Organization IDs are selectors, not credentials; Overlap rechecks membership and validates the company when an organization is actually used.

​
Workflows and runs

  • overlap.workflows.list
  • overlap.workflows.get
  • overlap.workflows.preflight — freezes the workflow revision and reports external effects
  • overlap.workflows.run
  • overlap.runs.get
  • overlap.runs.cancel
At the start of a fresh conversation, the assistant lists your current organizations before its first organization-scoped action unless you have already named and resolved an exact organization. If multiple organizations are available and the target is uncertain, it asks you to choose before continuing. Before preflight or execution, the assistant resolves the request to exactly one workflow. If no workflow or multiple plausible workflows match what you asked for, it lists the candidates and asks you to choose instead of guessing. It also asks for a required source URL or other runtime input when that information is missing, and obtains explicit written consent before starting the run. Workflow execution is available anywhere the connected user has a current organization membership; it does not require MCP to be activated separately for each organization. Every MCP run still uses a one-use start proof bound to the exact organization, workflow revision, and input. A supported workflow with external effects requires confirmation before it runs. Social workflow nodes can create reviewable drafts but cannot authorize publishing. Email, partner-export, and unknown external-effect nodes remain unavailable through MCP until they have equivalent durable dispatch protection.

​
Clips, transcripts, and renders

  • overlap.clips.search
  • overlap.clips.get
  • overlap.clips.update
  • overlap.transcripts.get
  • overlap.transcripts.replace
  • overlap.clips.render
  • overlap.operations.get
Clip and transcript writes use an expected version. If someone edits the clip after it was read, the server returns a conflict instead of overwriting the newer version. Renders are asynchronous and return an operation ID.

​
Social Calendar

  • overlap.social.accounts.list
  • overlap.social.calendar.list
  • overlap.social.posts.get
  • overlap.social.posts.create_draft
  • overlap.social.posts.update
  • overlap.social.posts.authorize — confirm and publish an immediate draft
  • overlap.social.posts.cancel
Draft creation never authorizes publication. Future times may be used for calendar planning, but future scheduled publishing is unavailable during the beta. Set scheduledAt to null before requesting immediate-publish confirmation. The assistant shows the immutable preview and asks for explicit written consent in chat; it never opens a browser for action confirmation. Once a post is scheduled or publishing, cancel its existing work before making a material edit; Overlap will not replace authorized copy in place. Calendar queries are limited to a 93-day range. Times are returned as RFC3339 values and natural-language scheduling uses the organization timezone.

​
Analytics

  • overlap.analytics.summary
  • overlap.analytics.posts.list
  • overlap.analytics.posts.get
  • overlap.analytics.trending
Analytics tools use cached Overlap data and report freshness and platform coverage. They do not trigger live provider refreshes.

​
Pagination and retries

List tools return opaque cursors and at most 100 records per page. Mutations use idempotency receipts so a network retry returns the original operation instead of repeating a workflow, render, or publish action.