Demo Sandbox

The demo sandbox is a public, read-only MCP server. It holds synthetic sales data for a fictional company, Meridian Technologies. Connect any MCP client and ask about its deals, meetings, commitments and people. You do not need an account.


Endpoint	`https://demo-mcp.meetdoris.com/mcp`
Transport	Streamable HTTP
Authentication	None

Connect

Claude Code
Claude Desktop
Codex CLI
Cursor
Other clients

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

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json:

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

codex mcp add doris-demo-ontology https://demo-mcp.meetdoris.com/mcp

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

Point the client at https://demo-mcp.meetdoris.com/mcp with the Streamable HTTP transport. Do not configure authentication.

Data

The sandbox starts from seed data. The seed has 99 accounts, 315 contacts, 244 deals, 12 competitors and 15 tactics. It also has meetings, commitments, objections, strategies, risks, leads and products. Live counts change over time. A job runs each day at 06:00 UTC and moves some deals to a new stage. The sandbox shows 23 types: deal, account, person, meeting, commitment, lead, pipeline, product, objection, competitor, competitor_result, pain_point, value_driver, decision, risk, strategy, tactic, framework, assessment, deal_outcome, closure_strategy, calendar_event, composition A call for any other type returns not_available.

Tools

The sandbox has the 8 read tools of the production MCP server. It has no write tools.

Tool	Parameters in the sandbox
`ontology_types`	`type_name`
`ontology_resolve`	`type_name`, `object_id`, `expand`
`ontology_list`	`object_type`, `filters`, `sort`, `expand`, `limit`, `mine`, `offset`
`ontology_search`	`query`, `types`, `filters`, `sort`, `limit`, `offset`, `mine`
`ontology_batch`	`refs`
`ontology_traverse`	`source_type`, `source_id`, `link_type`, `target_type`, `limit`
`ontology_aggregate`	`object_type`, `group_by`, `metrics`, `filters`, `mine`, `time_bucket`, `time_field`
`search_transcripts`	`query`, `date_from`, `date_to`, `mine`, `deal_id`, `meeting_id`, `meeting_ids`, `speaker`, `limit`

Some parameters of the production server are not in the sandbox, for example expand_params, cursor and link_filter. The sandbox has no signed-in user, so leave mine unset. In search_transcripts, mine is false by default. ontology_types in the sandbox does not show writable fields or actions.

Privacy

The sandbox uses the masked privacy level, the same as the production server. People come back with initials, for example “Michael D.”. Emails come back as m***@domain. search_transcripts is not masked.

Limits

Limit	Value
Calls for each IP address	30 a minute and 500 a day
Calls from all users together	1,000 an hour

When you reach a limit, the tool returns rate_limited with a message. After 12 calls from one IP address, results include a _demo_hint field. It asks your AI tool to mention https://meetdoris.com.

How the sandbox is isolated

The sandbox is a separate MCP server. The server fixes the workspace to the Meridian demo workspace. A request cannot change it.
The database connection is read-only.
The sandbox registers no write tools.

Get started

Using Doris

Automation

Admin & integrations

Developers

Changelog

Connect

Data

Tools

Privacy

Limits

How the sandbox is isolated

Next steps

Sandbox cookbook

Production MCP server

​Connect

​Data

​Tools

​Privacy

​Limits

​How the sandbox is isolated

​Next steps

Sandbox cookbook

Production MCP server

Connect

Data

Tools

Privacy

Limits

How the sandbox is isolated

Next steps