MCP Server

The Doris MCP server gives an AI tool access to the ontology of your workspace. The tool reads deals, accounts, people, meetings and commitments. It can also make a small set of writes.


Endpoint	`https://mcp.meetdoris.com/mcp`
Transport	Streamable HTTP
Authentication	OAuth 2.1 with PKCE and dynamic client registration
Scope	`ontology:read`

When you connect for the first time, your MCP client opens a browser window. Sign in with your Doris login. The client then gets a token for your user in your workspace.

To try the tools without an account, use the demo sandbox.

Connect a client

Menu names in other apps can change. Any client that supports Streamable HTTP and OAuth can use the endpoint.

claude mcp add --transport http doris https://mcp.meetdoris.com/mcp

Open Settings > Connectors > Add Connector. Paste the endpoint URL and sign in.You can also add the server to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "doris": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.meetdoris.com/mcp"]
    }
  }
}

codex mcp add doris https://mcp.meetdoris.com/mcp

Open Settings > Features > MCP > Add New MCP Server. Select Streamable HTTP and enter the endpoint URL. Or add this to your MCP configuration:

{
  "mcpServers": {
    "doris": {
      "url": "https://mcp.meetdoris.com/mcp"
    }
  }
}

Add this to .vscode/mcp.json:

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

Tools

The server has 12 tools. Eight tools read. Four tools write.

Tool	Kind	What it does
`ontology_types`	read	Lists the types, or returns the schema of one type
`ontology_resolve`	read	Returns one object, with optional expand keys
`ontology_list`	read	Returns a page of objects of one type
`ontology_search`	read	Searches across types
`ontology_batch`	read	Returns several objects in one call
`ontology_traverse`	read	Returns the objects linked to one object
`ontology_aggregate`	read	Counts objects or computes measures, grouped
`search_transcripts`	read	Searches what people said in meeting transcripts
`ontology_update`	write	Writes typed fields on one object
`ontology_action`	write	Runs a named action on one object
`create_composition`	write	Creates a document that you own
`edit_composition`	write	Edits the title or text of a document

The same data is available through the Ontology API. The API and the MCP server apply the same tenant scope.

ontology_types

Parameter	Type	Required	Description
`type_name`	string	No	The type to describe.

Without type_name, the tool returns a directory: each type name and its expand keys. With type_name, it returns the full schema. The schema includes properties, expand keys, writable fields, actions with their params_schema, measures and dataset capabilities.

ontology_resolve

Parameter	Type	Required	Description
`type_name`	string	Yes	The type, for example `deal`.
`object_id`	string	Yes	The object ID.
`expand`	string[]	No	Expand keys to add related data.
`expand_params`	object	No	Options for each expand key, for example `{"transcript": {"query": "pricing", "limit": 5}}`.

Some expand keys on deal are stakeholders, commitments, meetings, risks, next_step and similar_deals. Call ontology_types with type_name="deal" for the full list. For type_name="teammate", the ID me returns your own user.

ontology_list

Parameter	Type	Required	Description
`object_type`	string	Yes	The type to list.
`filters`	object	No	Field filters, for example `{"stage": "Negotiation"}`.
`sort`	string	No	Sort field and direction, for example `amount:desc`.
`expand`	string[]	No	Expand keys for each result.
`limit`	integer	No	1 to 100. The default is 25.
`offset`	integer	No	The number of results to skip.
`mine`	boolean	No	Return only objects that you own.
`include_links`	boolean	No	Add relationship counts to each result.
`changes_since`	string	No	An ISO-8601 time. Return only objects whose indexed content changed after it.
`cursor`	string	No	The `next_cursor` of the previous page. When you send it, the server ignores `offset`.

A limit above 100 returns validation_error.

ontology_search

Parameter	Type	Required	Description
`query`	string	No	Search text, 500 characters at most. Supports `"quoted phrases"`, `AND`, and `-word` to exclude a word.
`types`	string[]	No	Limit the search to these types.
`filters`	object	No	Field filters.
`sort`	string	No	Sort field and direction.
`limit`	integer	No	1 to 100. The default is 25.
`offset`	integer	No	The number of results to skip.
`mine`	boolean	No	Return only objects that you own.
`search_fields`	string[]	No	Search only these zones: `title`, `content` or `body`.
`include_links`	boolean	No	Add relationship counts to each result.
`changes_since`	string	No	An ISO-8601 time. Return only objects whose indexed content changed after it.
`cursor`	string	No	The `next_cursor` of the previous page. Works only with `sort="updated_at"`.

ontology_batch

Parameter	Type	Required	Description
`refs`	object[]	Yes	A list of `{"type": "...", "id": "..."}` references.

The result has results and errors, both keyed by type:id. One failed reference does not stop the others.

ontology_traverse

Parameter	Type	Required	Description
`source_type`	string	Yes	The type of the start object.
`source_id`	string	Yes	The ID of the start object.
`link_type`	string	No	Return only this link type.
`target_type`	string	No	Return only linked objects of this type.
`limit`	integer	No	The default is 50. Values above 200 become 200.
`link_filter`	object	No	Filter on link properties, for example `{"role": "decision_maker"}`.

ontology_aggregate

Parameter	Type	Required	Description
`object_type`	string	Yes	The type to aggregate, for example `deal`.
`group_by`	string	No	A declared dimension, for example `stage`.
`metrics`	string[]	No	Declared measure names, for example `deal_count` or `pipeline_amount`. Without this, the tool uses the count measure of the type.
`filters`	object	No	Field filters, applied before the aggregation.
`mine`	boolean	No	Aggregate only objects that you own.
`time_bucket`	string	No	`week`, `month` or `quarter`.
`time_field`	string	No	The date property to bucket on. You must set it when you set `time_bucket`.

ontology_types lists the measures and dimensions of each type.

search_transcripts

Parameter	Type	Required	Description
`query`	string	Yes	The words to find, 500 characters at most. The search matches words and meaning.
`date_from`	string	No	ISO-8601 lower limit on the meeting start time.
`date_to`	string	No	ISO-8601 upper limit on the meeting start time.
`mine`	boolean	No	Search only your own meetings. The default is `true`.
`deal_id`	string	No	Search only meetings linked to this deal.
`meeting_id`	string	No	Search only this meeting.
`meeting_ids`	string[]	No	Search only these meetings.
`speaker`	string	No	Return only turns whose speaker name contains this text.
`limit`	integer	No	The number of turns. The default is 25. The server can reduce it.

The result has transcript_turns and meetings_matched. Each turn has its meeting ID, start time in milliseconds, speaker and snippet. If a search with mine=true finds nothing, the server searches the whole workspace. It then sets widened_beyond_mine to true.

Writes

MCP tokens have only the ontology:read scope. There is no write scope. The server authorizes each write by its type and action. Every MCP call counts as an agent call, not a person’s call. Some actions accept only a person’s call. From MCP, these actions return an error and change nothing.

Type	Write	From MCP
`commitment`	`ontology_update` with `description`, `owner_type` (`rep` or `buyer`), `due_date` (`YYYY-MM-DD`)	Yes
`commitment`	`reopen`	Yes
`commitment`	`complete`	No. Returns `evidence_required`.
`commitment`	`cancel`, `wait_on_buyer`, `resume`, `reject_evidence`	No. Returns `human_required`.
`composition`	`ontology_update` with `title`, `body`	Yes
`composition`	`restore`	Yes
`deal_concern`	`mark_handled`, `reopen`	No
`calendar_event`	`ontology_update` with `join_requested`	No

ontology_types shows the current actions of each type and their params_schema. It does not list update. Use ontology_update for field writes, not ontology_action.

ontology_update

Parameter	Type	Required	Description
`type_name`	string	Yes	The type.
`object_id`	string	Yes	The object ID.
`patch`	object	Yes	A map of field to value. Only the `writable_fields` of the type are accepted.

A field that is not in writable_fields returns invalid_request. Nothing is written.

ontology_action

Parameter	Type	Required	Description
`type_name`	string	Yes	The type.
`object_id`	string	Yes	The object ID.
`action`	string	Yes	The action name, for example `reopen`.
`params`	object	No	Parameters that match the `params_schema` of the action.

The commitment actions take two optional parameters: operation_id (a UUID) and reason (1 to 4,000 characters). reject_evidence needs occurrence_id and reason. Send the same operation_id again to repeat a call safely. An action that can reach a buyer returns forbidden from MCP. Only a person can start it.

create_composition

Parameter	Type	Required	Description
`title`	string	Yes	The document title.
`sections`	object[]	Yes	Ordered sections. Each section is `{key, heading, blocks, sources?}`.
`deal_id`	string	No	Attach the document to this deal.

The document belongs to you. The result has composition_id and a link to the document in Doris.

edit_composition

Parameter	Type	Required	Description
`composition_id`	string	Yes	The document to edit.
`title`	string	No	A new title.
`body`	object	No	The full new body, `{"sections": [...]}`.

Send title, body or both. The body must keep the same sections, in the same order, with the same keys. You can change prose, callout and key-point blocks. The server keeps all other blocks, such as tables and charts. To get the current body, call ontology_resolve with type_name="composition" and expand=["body"].

Privacy

The MCP server always uses the masked privacy level. You cannot change it.

Tool	Masked
`ontology_resolve`, `ontology_list`, `ontology_search`, `ontology_batch`, `ontology_traverse`	Yes
`ontology_aggregate`	Returns counts and measures. It does not apply a privacy level.
`search_transcripts`	No. Speaker names and transcript text come back as recorded.

At masked, owner_name and owner_email stay visible on deals only. On other types, the server masks them. Internal calls follow the same rule as in the app. A member sees an internal meeting only if they were on it. An admin sees all meetings.

Rate limits

10,000 calls a day for each workspace. The MCP server and the Ontology API share this quota.
MCP has no per-minute limit. The per-minute limits in the API reference apply to REST routes only.
10 client registrations an hour for each IP address.

When the quota is used up, calls fail with rate_limited.

Example prompts

“Show me the Acme deal with its stakeholders and open commitments.”
“How many deals are in each stage, and what is the pipeline amount of each?”
“Every time security came up in the Acme calls this quarter, what was said?”
“Push the due date of this commitment to next Friday.”

Get started

Using Doris

Automation

Admin & integrations

Developers

Changelog

Connect a client

Tools

ontology_types

ontology_resolve

ontology_list

ontology_search

ontology_batch

ontology_traverse

ontology_aggregate

search_transcripts

Writes

ontology_update

ontology_action

create_composition

edit_composition

Privacy

Rate limits

Example prompts

​Connect a client

​Tools

​ontology_types

​ontology_resolve

​ontology_list

​ontology_search

​ontology_batch

​ontology_traverse

​ontology_aggregate

​search_transcripts

​Writes

​ontology_update

​ontology_action

​create_composition

​edit_composition

​Privacy

​Rate limits

​Example prompts

Connect a client

Tools

ontology_types

ontology_resolve

ontology_list

ontology_search

ontology_batch

ontology_traverse

ontology_aggregate

search_transcripts

Writes

ontology_update

ontology_action

create_composition

edit_composition

Privacy

Rate limits

Example prompts