01 / Choose a remote MCP client
Look for support for Streamable HTTP and the authorization method you intend to use. Codex, ChatGPT, Claude Code, Claude and Cursor have different configuration flows and account requirements.
Read Dovod’s MCP Client Guide02 / Add the server address
For the hosted service, use this endpoint. For a self-hosted instance, use the address of that instance instead. The client must be able to reach it.
https://dovod.app/mcp
03 / Authorize your connection
Sign in when your client supports Dovod’s OAuth flow. Otherwise, create an API key in Dovod Settings → API Keys and configure it as a bearer token if the client supports custom headers.
A public endpoint does not mean public project access. Your team role still governs which operations you may perform. Keep credentials in your client’s secret configuration, not in shared prompts.
04 / Give your assistant the instructions
The MCP connection exposes tools. The documentation explains the project structure and research workflow.
Read https://dovod.app/llms.txt, then the linked MCP Client Guide and Conducting Research guide. Use the Dovod connection I have configured. List my projects, ask what decision I need to make, and help me save a first finding with its source. Do not invent evidence.
Check a useful result.
Ask for your project list, then create a project and save a first finding through your configured client. Open Dovod to check the material. An empty project list is normal for a new account.
Reading the public documentation alone does not connect the assistant or grant access to your projects.
If it does not connect
Check the transport, reachable server address, account permissions and credential. A login failure, unsupported client feature and an empty project list are different conditions.
Existing SSE clients may use the legacy transport; use the current MCP guide to check that setup instead of substituting a different endpoint by guesswork.