Does this config work in other editors?

Yes. This is the standard `mcpServers` shape, so the same block works in most MCP clients that read a JSON config — the entry is named for Cursor because that is the client people search for.

What does the server return?

run_exposure_audit(domain) starts an audit on first call for a domain and returns the finished result when you call it again a couple of minutes later.

Free & unauthenticated

Cursor MCP: competitive research from inside Cursor

Cursor reads MCP servers from a JSON config file, using the same shape most MCP clients accept. Pull competitive context into the editor while you are working on the page that competes — no separate tab, no separate account.

One tool, run_exposure_audit(domain): the first call starts the audit (about 2–3 minutes), and calling it again with the same domain returns the results. No account, no API key. Free usage is capped per day.

Set it up in Cursor

Add this entry to your client's MCP server config:

{
  "mcpServers": {
    "dozier": {
      "url": "https://dozier.io/backend/mcp",
      "type": "http"
    }
  }
}

The server speaks MCP over Streamable HTTP at https://dozier.io/backend/mcp, with no authentication.

Questions

Does this config work in other editors?: Yes. This is the standard `mcpServers` shape, so the same block works in most MCP clients that read a JSON config — the entry is named for Cursor because that is the client people search for.
What does the server return?: run_exposure_audit(domain) starts an audit on first call for a domain and returns the finished result when you call it again a couple of minutes later.

Other clients

Or see the Dozier MCP server overview for every client in one place.

Want continuous monitoring, not just one audit?

The MCP server exposes the free Exposure Audit only. See the full product or pricing for cited Dossiers and tracked rivals.

See the product

Set it up in Cursor

Questions

Other clients

Want continuous monitoring, not just one audit?

Ask an AI about Dozier