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=websiteIn Claude, skip the URL: add Dopia from the Claude directory. Want a ready-made skill that finds prospects, not just the connection? Get the plugin.
They are not a checklist for a security page. They decide which tools the agent is even told about.
crm:readLook up a company, pull a record, count what is in the pipeline — with the same table schema the product uses, not a flattened export.
crm:writeCreate and update records. Identity resolution is the same code path the product runs, so an agent cannot quietly mint a duplicate company.
artifacts:readOpen a page saved in an earlier session and list what the workspace has. This is what lets a list produced last week become records today, instead of being run again from scratch.
artifacts:writeTurn 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, and reading pages back is a third.
The same workspace answers every client, so research started in a terminal is on the record by the time you open the app. Step by step for Claude, with what each permission allows: Connect Dopia to Claude.
Dopia is in Anthropic’s directory: open the listing, press Connect, and approve it in the browser. In the app it is under Customize → Connectors — search for Dopia.
Open Dopia in ClaudeOr add it by hand: Settings → Connectors → Add custom connector, and paste the URL.
https://mcp.dopia.ai/mcp?via=websiteSigned in with your Claude account, a connector you added in the Claude app is already here. Otherwise 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.
/mcpAdd the server, then sign in.
codex mcp add dopia --url "https://mcp.dopia.ai/mcp?via=website"codex mcp login dopiaStreamable HTTP, with OAuth. Nothing to install on our side and no API key to paste.
https://mcp.dopia.ai/mcp?via=websiteSo here is the answer, before you ask it.
You approve the connection in the browser and see, in plain words, what it is being allowed to do before you approve it.
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.
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.
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