MCP server - Default

Default’s MCP server lets an MCP-compatible AI client connect to approved Default data and tools. 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.

MCP access needs the admin or owner role. Every Default MCP tool requires the workspace admin or owner role.Members and viewers do not see MCP tools, even after they connect. If you need access, ask a workspace admin.

Get started

Connect your client to the Default MCP server:

Server URL

https://mcp.default.com/mcp

Every client uses the same two steps: add the server URL, then sign in to Default through the browser-based OAuth prompt as an admin or owner. There is no access-token, bearer-token, or API-key method.

Install the Default MCP server in Cursor

Select 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

{
	"mcpServers": {
		"default": {
			"url": "https://mcp.default.com/mcp"
		}
	}
}

Run this command to add the Default MCP server:

claude mcp add --transport http default https://mcp.default.com/mcp

Then, inside Claude Code, run /mcp and follow the sign-in prompt.

In Claude on the web or in the Claude desktop app:

Open Settings, then Connectors.
Select Add custom connector.
Enter a name, such as Default, and the server URL: https://mcp.default.com/mcp.
Select Add, then complete the sign-in prompt.

Custom connectors require a paid Claude plan.

Add the Default MCP server to ~/.codex/config.toml:

~/.codex/config.toml

[mcp_servers.default]
url = "https://mcp.default.com/mcp"

Then sign in:

codex mcp login default

Select the button to open VS Code and add the Default MCP server, then complete the sign-in prompt. To configure it manually instead, add this to .vscode/mcp.json in your workspace:

.vscode/mcp.json

{
	"servers": {
		"default": {
			"type": "http",
			"url": "https://mcp.default.com/mcp"
		}
	}
}

MCP is an open protocol with many compatible clients. In any client that supports remote MCP servers over Streamable HTTP:

Add a new remote MCP server with the URL https://mcp.default.com/mcp.
Complete the browser-based OAuth sign-in as an admin or owner.
Refresh the tool list.

Many clients accept this common configuration shape:

{
	"mcpServers": {
		"default": {
			"url": "https://mcp.default.com/mcp"
		}
	}
}

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.
Explain why a lead routed to a rep, and manage queue members and routing policies.
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 connected integrations and enabled features. All of them require the admin or owner role.

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.

Tool	Type	What it does
`search_default`	Read	Searches the documentation and returns the relevant pages.
`query_docs_filesystem_default`	Read	Browses the documentation as a read-only file tree.
`submit_feedback`	Write	Reports an incorrect or confusing page to the Default 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

The tools below are available on Default’s MCP server today. All of them require the admin or owner role. There is no member-level MCP access. Read tools return data. Write and run tools change data or start jobs, so treat them accordingly.

The MCP server is in beta. The core tools below are on for every workspace with MCP access. The tool families under Tool families rolling out turn on per workspace, so some of them may not appear in your client’s tool list yet.

System

Tool	Type	What it does
`system_ping`	Read	Confirms the MCP service is reachable and that its authenticated link to Default’s API works.
`calculate`	Read	Evaluates an arithmetic expression and returns the exact result, such as percentages, ratios, and sums.

calculate details

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.

Tool	Type	What it does
`data_schema`	Read	Returns the field descriptors for `person` or `company` records so you know what you can filter on.
`data_count`	Read	Returns an aggregate count of `person` or `company` records, with optional schema-backed filters.
`data_query`	Read	Returns `person` or `company` rows with required pagination and a schema-backed field allowlist.

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.

Tool	Type	What it does
`crm_schema`	Read	Returns provider-aware field descriptors for a Salesforce or HubSpot object.
`crm_count`	Read	Returns an aggregate count for a CRM object, with optional schema-backed filters.
`crm_query`	Read	Returns CRM rows with required pagination and a schema-backed field allowlist.
`crm_actor`	Read	Returns the signed-in user’s own Salesforce / HubSpot user IDs, for owner-filtered queries.
`integration_user_mappings_list`	Read	Lists CRM user mappings for the org. Filter by email or name to resolve a teammate before an owner filter.
`crm_write`	Write	Updates fields on a single CRM record. Two-step: preview first, then re-call with `confirm: true` to commit.

How crm_write confirmation works

crm_write never changes data on the first call.

Call it without confirm, or with confirm: false, to get a pending_confirmation preview of the resolved change.
Show that preview to the operator.
After the operator approves, re-call with confirm: true.

Default validates field ids against crm_schema.

Tool families rolling out

The families below ship on the MCP server but turn on per workspace. If your workspace does not have a family enabled yet, its tools do not appear in your client’s tool list. Ask your Default contact to enable a family you need. The routing write 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

Tool	Type	What it does
`enrichment_run`	Run	Starts an enrichment job for records in a table view or workflow, using a provider or waterfall.

enrichment_run details

You have two 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

Read tools over your booked meetings, event types, booking links, and each rep’s availability setup.

Tool	Type	What it does
`meetings_list`	Read	Browses booked meetings with hosts, attendees, the event, and the queue that booked each one.
`meeting_get`	Read	Reads one meeting: full host set, attendees, conferencing type, and cancellation reason.
`events_list`	Read	Lists bookable event types with duration, conferencing type, and active state.
`event_get`	Read	Reads one event type’s booking config, host lineup, booking-form questions, and linked workflows.
`host_options_list`	Read	Lists members who can host meetings, with calendar health. Resolves a rep name to a user ID.
`scheduling_links_list`	Read	Lists one event type’s recent booking links with their `active`, `expired`, or `revoked` state.
`availability_get`	Read	Reads a rep’s configured buffers, notice period, working hours, and out-of-office blocks.
`work_schedule_get`	Read	Reads a rep’s working hours and the timezone they are expressed in.
`ooo_list`	Read	Lists a rep’s out-of-office blocks, optionally within a date window.

Queues & routing

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

Tool	Type	What it does
`list_queues`	Read	Lists routing queues with active state, policy, distribution rule, and assignment totals.
`get_queue`	Read	Reads one queue’s members with weights, paused state, and the live up-next ranking.
`list_routing_policies`	Read	Lists routing policies with distribution rule, tiebreaker, and reset frequency.
`get_routing_policy`	Read	Reads one policy’s active configuration and the queues that use it.
`explain_assignment`	Read	Returns the full decision record for one assignment: winner, scores, and excluded members.
`lookup_assignments_by_email`	Read	Finds a lead’s routing history by email, including failed routing requests.
`list_assignments`	Read	Browses the assignment log: which lead went to which rep in which queue, and when.
`list_routing_activity`	Read	Browses the routing configuration changelog: who changed what, when, and why.

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.

Tool	Type	What it does
`queue_member_update`	Write	Pauses or unpauses a queue member, or changes their routing weight.
`queue_member_calibrate`	Write	Credits or debits a member’s effective assignment count, with a required reason.
`queue_member_add`	Write	Adds members to a routing queue.
`queue_member_remove`	Write	Removes members from a routing queue. Their historical assignments stay.
`routing_policy_update`	Write	Updates a policy’s rules. The change applies to every queue using the policy.
`routing_policy_reset`	Write	Resets a policy’s assignment counters to zero across all of its queues.

Workflows

Tool	Type	What it does
`list_workflows`	Read	Lists workflows with enabled state, published version, trigger types, and run counts.
`list_workflow_runs`	Read	Lists workflow runs, filtered by workflow, status, person email, company domain, trigger, or time.
`get_workflow_logs`	Read	Returns diagnostics, node visits, and a classified timeline for one workflow run.

Integrations & users

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

Tool	Type	What it does
`integration_health`	Read	Reports whether each integration is `connected`, `broken`, or `not_connected`.
`mapping_coverage`	Read	Counts members with and without a CRM user mapping, per provider.
`mapping_validate`	Read	Checks a mapping value against the live provider to confirm the user ID actually exists.
`provider_people_list`	Read	Lists the users or owners that exist at a provider, with the value a mapping needs.
`calendar_connections_get`	Read	Reads a rep’s connected calendars, primary calendar, and conferencing provider.
`users_list`	Read	Lists workspace members with role, status, and the user ID the per-user tools take.
`user_me`	Read	Reads your own member record: ID, email, name, and roles.

Identity graph

Tool	Type	What it does
`identity_resolve`	Read	Resolves an email, domain, anonymous ID, or CRM record ID to its canonical identity and record.
`crm_duplicates_scan`	Read	Finds exact-key CRM duplicates: contacts sharing one email, or companies sharing one domain.

Data import & segments

Upload a CSV, map its columns to Default fields, and work with segments (saved table views).

Tool	Type	What it does
`upload_file`	Write	Starts a CSV upload. Returns a secure link a human opens to upload the file in their browser.
`get_upload_status`	Read	Polls an upload until the human completes it in their browser.
`upload_file_content`	Write	Uploads a small CSV inline in one call, for automated flows without a human.
`list_uploads`	Read	Lists CSV uploads with status and row and column counts.
`objects_map`	Write	Proposes a column-to-field mapping for a parsed CSV, with confidence and warnings.
`objects_update`	Write	Re-runs a proposed mapping with corrections before you confirm it.
`objects_confirm`	Write	Freezes a reviewed mapping proposal into an immutable confirmed version.
`segment_list`	Read	Lists the segments (saved table views) you can access, including CSV-backed ones.
`segment_get`	Read	Reads one segment’s columns, saved filters, and data source.
`segment_query`	Read	Reads rows from a segment with pagination. The segment’s saved filters always apply.
`segment_create`	Write	Creates a segment over data-model records or over an uploaded CSV.
`segment_update`	Write	Updates a segment’s name, sharing, saved filters, or columns.
`segment_delete`	Write	Removes a segment definition. The underlying records or CSV are not touched.

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 ten 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

“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?”

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.”

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.

Access layer	What it controls
Workspace enablement	Whether MCP access is available for your workspace.
Authentication	Whether the request comes from a Default user signed in through browser-based OAuth.
Role	MCP tools require the admin or owner role. Members and viewers cannot use them.
Enabled features	Feature-gated tool families appear only while enabled for your workspace.
Connected integrations	Which external systems and records Default can use to answer (for example CRM queries).

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.

Troubleshooting

No tools appear after I connect

Confirm that your workspace has MCP access enabled. Confirm that you are signed in as an admin or owner, because members and viewers do not see MCP tools.Then refresh the tool list in your client. Available tools also depend on your connected integrations.

A newly enabled tool does not appear

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.

A listed tool says disabled or not found

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.

My client says the server is unauthorized

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 as an admin or owner.

A tool appears but cannot answer my question

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.

A browser-based client gets an origin error

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.

Connect to the endpoint

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

Complete the browser-based OAuth sign-in as an admin or owner user. There is no access-token or service-token flow.

Initialize the session

Send initialize. Then send notifications/initialized.

Open the notification stream

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

Discover the tools

Call tools/list to discover available tools.

Handle tool-list changes

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

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

{
	"jsonrpc": "2.0",
	"id": 1,
	"method": "tools/call",
	"params": {
		"name": "data_count",
		"arguments": {
			"object": "company"
		}
	}
}

The response includes MCP content and, when available, structured output. Your client can render the output as text, tables, or another UI.

​Get started

​What you can do

​Docs MCP server

​Available tools

​System

​Company & person data

​CRM (Salesforce & HubSpot)

​Tool families rolling out

​Enrichment

​Meetings & scheduling

​Queues & routing

​Routing writes

​Workflows

​Integrations & users

​Identity graph

​Data import & segments

​Example prompts

​How access works

​Troubleshooting

​For custom client builders

Get started

What you can do

Docs MCP server

Available tools

System

Company & person data

CRM (Salesforce & HubSpot)

Tool families rolling out

Enrichment

Meetings & scheduling

Queues & routing

Routing writes

Workflows

Integrations & users

Identity graph

Data import & segments

Example prompts

How access works

Troubleshooting

For custom client builders