Skip to main content
The Default MCP server connects an MCP-compatible AI client to approved data and tools in your Default workspace. MCP, the Model Context Protocol, is a standard way for AI clients to call external tools. Use it when you want an external assistant or custom agent to ask questions about your workspace. It goes through the same permissioned access layer that Default uses for agent workflows.
Admins and owners can use the enabled MCP tools. Members and editors can also use the booking-link tools.Booking tools use the member’s existing event and queue access. They do not grant access to more events or queues. Routing changes need a separate MCP routing-write grant and the same queue or policy permissions as the app. Viewers cannot use booking tools.

Get started

Connect your client to the Default MCP server:
Server URL
Every client uses the same 2 steps: add the server URL, then sign in to Default through the browser-based OAuth prompt with your Default account. There is no access-token, bearer-token, or API-key method.
Install the Default MCP server in CursorSelect Install MCP Server to open Cursor and add the Default MCP server, then complete the sign-in prompt. To configure it manually instead, add this to ~/.cursor/mcp.json:
~/.cursor/mcp.json
After you connect, ask your client to list or refresh MCP tools, then start with a specific question: “What company fields can I query?” or “How many companies match this filter?” Your role, connected integrations, and enabled workspace features filter the tool list.

What you can do

Common use cases include:
  • Inspect your company and person schema before you ask a data question.
  • Count or query company and person records in your Default data model.
  • Count or query Salesforce and HubSpot records through your connected CRM.
  • Resolve a teammate to their CRM user ID so you can filter records by owner.
  • Update a single CRM record through a confirm-before-write flow.
  • Start an enrichment run for records in a table view or workflow.
  • Browse booked meetings, event types, and each rep’s availability setup. Check open slots and create or revoke booking links.
  • Explain why a lead routed to a rep, and manage queue members and routing policies.
  • Build, check, and publish workflows, with a preview you approve before each save. See Build workflows with an AI agent.
  • Inspect workflow runs and read the logs for one run.
  • Check integration health and find reps missing a CRM mapping or a calendar.
  • Upload a CSV, map its columns to Default fields, and query it as a segment.
  • Give external AI workflows a standard way to talk to Default without copying data out of your workspace.
The exact tools you see depend on your role, grants, connected integrations, and enabled features.

Docs MCP server

Default also runs a second, separate MCP server for this documentation site: https://docs.os.default.com/mcp. It searches and reads the published docs, so your assistant can answer “how do I” questions with current product documentation instead of stale training data. It is public: it needs no sign-in and no workspace role, and it never reads or changes your workspace data. Its only write tool sends feedback to the docs team.
Add both servers to your client. The docs server answers questions about how Default works. The workspace server, described on the rest of this page, answers questions about your data.

Available tools

Most tools below require the admin or owner role. Members and editors can use events_list, event_get, host_options_list, scheduling_links_list, scheduling_link_create, scheduling_link_revoke, scheduling_link_update, my_booking_link, suggest_times, meetings_list, meeting_get, meeting_cancel, meeting_mark_no_show, meeting_reschedule, meeting_reassign, meeting_add_guests, and meeting_mark_held. Routing write tools require a separate MCP routing-write grant and app permissions. Other tool families keep their existing restrictions. Read tools return data. Write and run tools change data or start jobs, so treat them accordingly.
The MCP server is in beta. The tools below are on for every workspace with MCP access, except the three noted under More tool families: enrichment, data import and segments, and run_workflow. Those turn on per workspace.

System

Supports + - * / % ^, parentheses, unary minus, and the functions abs, round, floor, ceil, sqrt, min, max, and pow. It accepts numbers and operators only, not variables.Example: (150000 * 0.85) / 12.

Company & person data

These tools read your Default data model. The data model holds the company and person records that fill your Tables.
Call data_schema first so your client knows which fields exist before it filters or sorts with data_count or data_query.

CRM (Salesforce & HubSpot)

These tools read and write through your connected CRM integration. Connect and sync the relevant integration, Salesforce or HubSpot, first.
crm_write never changes data on the first call.
  1. Call it without confirm, or with confirm: false, to get a pending_confirmation preview of the resolved change.
  2. Show that preview to the operator.
  3. After the operator approves, re-call with confirm: true.
Default validates field ids against crm_schema.

More tool families

The families below are on for every workspace with MCP access, with three exceptions that turn on per workspace: enrichment, data import and segments, and run_workflow under Workflows. If one of those is not enabled for your workspace, its tools do not appear in your client’s tool list. Ask your Default contact to enable it. The routing write tools and the booking link tools use the same preview-then-confirm pattern as crm_write: the first call returns a preview and changes nothing, and only a re-call with confirm: true commits. The data import tools use their own review step instead, described in that section.

Enrichment

Call enrichment_options with object_type first. Pass providers[].provider_id as provider_id, or waterfalls[].waterfall_id as waterfall_id. Use nextCursor to page through waterfalls in stable ID order. Both tools require the Admin role, and Default turns them on per workspace. The providers you can use are the ones enabled for your workspace, whether or not they are in a waterfall. Waterfalls retain their saved provider order.You have 2 ways to select records:
  • Pass explicit record_ids.
  • Omit them and set a mode, for example all or all_empty_cells, to resolve the record set from the view.
For AI-research providers, also pass a prompt or an output_schema that describes the research ask.This starts a job and spends enrichment credits. It does not return enriched values inline.

Meetings & scheduling

Tools over your booked meetings, event types, booking links, open slots, and each rep’s availability setup. Admin example: “Find duplicate booking links on the ‘Sales intro’ event and revoke the extras.” The audit compares host identities and flags, case-sensitive trimmed names, visibility, identifiers, enabled and disabled saved URL parameters, and expiry days in the requested timeZone. Pass your browser’s IANA timezone to match the app’s local-day comparison; when omitted, the server’s local timezone is used and returned in the result. Links with fallback hosts are excluded from duplicate groups. The keeper is the oldest link with a non-canceled booking, or the oldest link if none has bookings. Example: “Show me my booking links.”

Queues & routing

Read tools that answer “why did this lead go to this rep” and “who is up next”.

Routing writes

Write tools that change live routing behavior. They roll out separately from the routing read tools, and every one of them previews first and commits only on confirm: true.

Rules of Engagement

A ruleset decides where a lead goes (a queue, a person, or no one) from its input values. These tools read a ruleset in plain words, test it with sample leads, and change it.
A ruleset has a draft and a live version. roe_ruleset_create, roe_ruleset_update, and roe_ruleset_edit_rules change the draft only. Leads keep routing by the live version until roe_ruleset_publish.Every write previews first and commits only on confirm: true. The preview shows each rule before and after, with queue and person names. The publish preview also shows changes to inputs and the fields they read.Before a publish, run roe_ruleset_test with compare: true. It runs each sample lead on the live version and on the draft and returns only the leads that would go somewhere else.roe_ruleset_test never assigns a lead, never writes to the evaluation log, and never moves a queue’s order.

Workflows

For the build order, prompts that work, and rules to give your agent, see Build workflows with an AI agent.

Integrations & users

Read tools for checking whether your integrations and reps are set up correctly.

Identity graph

Data import & segments

Upload a CSV, map its columns to Default fields, and work with segments (saved table views). This family turns on per workspace.

Example prompts

Concrete, specific prompts help the client pick the right tools. Name the object, the fields, and any filter, owner, or timeframe you care about. Explore what’s there
  • “Which company fields can I filter and sort on?”
  • “Show me the schema for person records, then list the 10 most recently created.”
Count and segment
  • “How many companies were created in the last 30 days?”
  • “How many person records are missing a job title?”
Query your CRM
  • “List Salesforce opportunities in the ‘Negotiation’ stage, sorted by amount, and page through them.”
  • “Count HubSpot companies in the technology industry with more than 500 employees.”
Filter by owner
  • “Find my Salesforce user ID, then list the accounts I own.”
  • “Look up Jordan Lee’s HubSpot owner ID and count the deals they own.”
Run enrichment
  • “Enrich every person in my ‘Inbound leads’ view that’s missing a company name.”
Inspect meetings and routing
  • “Rename my Q4 outbound booking link to Q4 EMEA outbound.”
  • “Delete the revoked q4-promo link so I can reuse its identifier.”
  • “Give me a booking link for the Sales intro event with me and Jordan Lee.”
  • “List my upcoming meetings this week and who is hosting each one.”
  • “Why did this lead go to Jordan? Explain the assignment.”
  • “Who is up next in the ‘Inbound AE’ queue?”
  • “What slots are open for the ‘Intro call’ event next week? Then create a booking link hosted by Jordan Lee that expires Friday.”
Check setup health
  • “Is our Salesforce integration healthy? Which reps are missing a CRM mapping?”
  • “Does Jordan Lee have a connected calendar and working hours set?”
Debug a workflow run
  • “Find the last failed run of the ‘Inbound router’ workflow and show me its logs.”
Build a workflow
  • “In the ‘Inbound router’ workflow, add a branch for companies with more than 1,000 employees that goes to the ‘Enterprise AE’ queue. Show me each change before you save it, then ask me before you publish.”
Do the math
  • “For companies in that view, what’s the average deal size? Use the calculator for the exact number.”
Update a record (with confirmation)
  • “Set the lifecycle stage to ‘Customer’ on this HubSpot company. Show me the change to approve before writing.”

How access works

Default only exposes tools that your account is allowed to discover and call. If a tool is not allowed for your account, it may not appear in your client’s tool list. For feature-gated tools, Default re-checks your workspace’s current feature access on each tool call. When a feature turns off, a client cannot use the cached tool.

Give a member booking access

Every member and editor can use the booking tools. What they can book is bounded by their existing access:
  1. Give the person edit access to the required events through the existing event sharing controls.
  2. Give the person access to any required queues, or add them as an active queue member.
  3. Ask the person to refresh or reconnect their MCP client.
The booking tools can read permitted events, find people and visible queues, list booking links, and create or revoke links. Each write still requires confirmation. Access checks also apply when an agent supplies an event or queue ID directly. Meeting reads show only meetings the person can see in the app. meeting_cancel previews a meeting, then cancels it after confirmation if the person can manage it. Guests receive the normal cancellation email. meeting_mark_no_show works the same way: the calendar event is removed, the event’s no-show messages are sent, and hosts picked from a queue get their spot back when the queue’s policy returns no-show meetings. meeting_reschedule moves a meeting to a new start the way a host does from the calendar: minimum notice and working hours do not apply, and busy time is shown as a warning only. meeting_reassign hands a meeting to another person or to a queue. A queue picks its member when the change is confirmed, and the result names that person. The new host sends a new calendar invite and the old invite is cancelled. meeting_add_guests adds up to 10 guests to a meeting. A person who can manage the meeting can add guests even when the event does not let guests invite others. meeting_mark_held marks a meeting as held once it has started. The calendar event stays, no message is sent, and workflows that start when a meeting is held run. Held is final. Booking tools do not enable personal availability settings, open-slot checks, event editing, or workflow tools. Changing a person’s role to viewer removes the booking tools within 60 seconds.

Troubleshooting

Confirm that your workspace has MCP access enabled. Confirm that you are signed in with the correct account. Viewers see no booking tools, and routing writes need the required separate grants.Then refresh the tool list in your client. Available tools also depend on your connected integrations.
Refresh the MCP server in your client. Default sends the standard notifications/tools/list_changed notification when the client opens its update channel.Some clients keep an older tool cache or do not implement automatic list refresh. If a refresh does not send a new tool-list request, disconnect and reconnect the MCP server.
Your client likely cached a tool that is no longer enabled. Default enforces current feature access at execution time even when the client’s display is stale.Refresh the MCP tool list to remove it.
Sign in again to refresh your session.If the error continues, confirm that your client points at the Default MCP server URL. Also confirm that you completed the browser-based sign-in with the account that received access.
Add more context to your prompt. Include the object, field, timeframe, owner, or filter you want the tool to use.If the data comes from an integration, confirm that integration is connected and synced.
Ask your Default admin or implementation team to confirm the client origin is allowed for your workspace’s MCP configuration.

For custom client builders

Connect your custom client to Default’s remote MCP endpoint over Streamable HTTP. Then use standard MCP requests to discover and call tools.
1

Connect to the endpoint

Connect to the Default MCP endpoint: https://mcp.default.com/mcp.
2

Sign in with OAuth

Complete the browser-based OAuth sign-in with your Default account. There is no access-token or service-token flow.
3

Initialize the session

Send initialize. Then send notifications/initialized.
4

Open the notification stream

Open authenticated GET /mcp with Accept: text/event-stream to receive server notifications.
5

Discover the tools

Call tools/list to discover available tools.
6

Handle tool-list changes

When notifications/tools/list_changed arrives, call tools/list again. Replace the cached tool schemas.
7

Call a tool

Call tools/call with the selected tool name and arguments. Include the bearer credential on every request.Default’s MCP endpoint does not require worker-affine session state.
Default’s MCP server currently exposes tools. Resources and prompts may not be available from this endpoint unless your workspace has been explicitly configured for them.
Example tools/call request
The response includes MCP content and, when available, structured output. Your client can render the output as text, tables, or another UI.
Last modified on November 18, 2026