Agentic platform · MCP

Your revenue data,
in the agent you already use.

Dopia is an MCP server. Point Claude Code, the Claude app, Codex or anything else that speaks MCP at one URL, approve what it may do, and it can look things up in your workspace, write records back, and publish what it finds as a page you can send.

https://mcp.dopia.ai/mcp?via=website

Want a ready-made skill that finds prospects, not just the connection? Get the plugin.

Three permissions, and you pick which.

They are not a checklist for a security page. They decide which tools the agent is even told about.

crm:read

Read the workspace

Look up a company, pull a record, count what is in the pipeline — with the same table schema the product uses, not a flattened export.

  • search_crm
  • search_records
  • get_record
  • get_table_schema
  • aggregate_records
crm:write

Write records back

Create and update records. Identity resolution is the same code path the product runs, so an agent cannot quietly mint a duplicate company.

  • create_record
  • update_record
artifacts:write

Publish a page

Turn a finished analysis into a page with its own URL that you can send to someone who has no account. Held apart from crm:write on purpose — publishing and record-writing are different consents.

  • create_artifact

One URL. Whatever you already have open.

The same workspace answers every client, so research started in a terminal is on the record by the time you open the app.

Claude Code

Add the server.

claude mcp add --transport http dopia "https://mcp.dopia.ai/mcp?via=website"

Run /mcp, pick dopia, and approve it in the browser.

/mcp

The Claude app

Settings → Connectors → Add custom connector, and paste the URL. “Sign in now” and “Register automatically” are detected for you.

https://mcp.dopia.ai/mcp?via=website

Codex

Add the server, then sign in.

codex mcp add dopia --url "https://mcp.dopia.ai/mcp?via=website"codex mcp login dopia

Any MCP client

Streamable HTTP, with OAuth. Nothing to install on our side and no API key to paste.

https://mcp.dopia.ai/mcp?via=website

An agent with your CRM is a security question.

So here is the answer, before you ask it.

OAuth, not a pasted key

You approve the connection in the browser and see, in plain words, what it is being allowed to do before you approve it.

Two gates, not one

A credential’s scopes decide which tools are advertised, and every call is re-checked at execution. An out-of-scope call never runs, even if the model invents it.

One implementation

MCP tools are the same code the in-product agent uses. There is no second, thinner copy of your CRM logic to drift out of sync.

Connect it to the agent you already trust.

One URL, permissions you approve in the browser, and a workspace that keeps what your agents find instead of losing it with the conversation.

MCP over streamable HTTP · OAuth · revoke any time