How to Connect Claude Code to DAVE over MCP

Summary

The steps

1. 1

   Navigate to MCP key management

   MCP keys in DAVE are per-user credentials. Each user generates their own key, scoped to their account and the capability preset they choose. An Admin can also generate and manage MCP keys on behalf of other users. The key management interface is inside the API Management section of the Admin panel.

   Do this

   • In the sidebar, click Admin.
   • Click API Management.
   • Locate the MCP Keys tab or section within API Management.
   • Confirm you can see a list of existing MCP keys (or an empty state if none have been created yet).

   Example

   If the Admin option is not visible in your sidebar, your account does not have the Admin role. For non-Admin users who need to generate their own MCP key, check whether a self-service key generation option is available under your account settings. If not, ask an Admin to generate a key on your behalf.

   Best practice

   Generate one MCP key per person and per AI assistant. Do not share MCP keys between users or between Claude Code and other AI assistants such as Claude Desktop or VS Code. Per-user keys mean the audit log records which person's assistant performed each action, not just that an MCP action occurred. Shared keys make the audit trail ambiguous.

2. 2

   Choose a capability preset and generate the key

   DAVE's MCP integration exposes 34 tools across four capability presets. When you generate an MCP key, you select a preset that determines which tools the key grants access to. The preset is set at key creation and cannot be changed afterward: to change the preset, generate a new key.

   The four presets follow a least-privilege model. Each preset grants access to a defined subset of the 34 available tools, matched to a specific use case. Selecting the narrowest preset that covers your intended use is the recommended approach: it limits what Claude Code can do through MCP to exactly what you need, and nothing more.

   The preset options and the tool categories they cover are sourced from the DAVE MCP documentation. The specific preset names and their exact tool lists are not detailed in the feature summary document: see the dedicated MCP help documentation for the full preset-to-tool mapping. The key facts are: four presets exist, each grants a subset of the 34 total tools, and the preset is locked at key creation.

   After selecting a preset, click the button to generate the key. DAVE displays the key value once, in full, immediately after generation. Copy it now: it will not be shown again. Store it in a secure location such as a password manager before closing the dialog.

   Do this

   • Click Generate New MCP Key (or the equivalent button in the MCP Keys section).
   • Review the four capability preset options and select the one that matches your intended use for Claude Code.
   • Optionally, give the key a descriptive name (for example: "Claude Code - [your name]") so it is identifiable in the audit log and key list.
   • Click Generate (or Create).
   • When the key value is displayed, copy it immediately to a secure location. It will not be shown again.
   • Close the dialog. The key now appears in the MCP Keys list with its preset, creation date, and last-used timestamp.

   Example

   A developer who wants Claude Code to be able to read workflow definitions and run instances but not modify agent configurations would select the preset that covers workflow and instance tools, rather than the full-access preset. This limits the blast radius if the key is ever compromised: Claude Code can only do what the preset allows.

   Best practice

   Name every MCP key clearly at creation. A key named "Claude Code - Jane Smith" is immediately identifiable in the audit log and key list. A key named "key-1" is not. If you need to revoke a key later, a clear name makes it easy to find the right one without guessing. Revocation takes effect within minutes, even on open sessions.

3. 3

   Find your DAVE MCP server URL

   DAVE hosts the MCP server over HTTPS. There is nothing to install locally: Claude Code connects to DAVE's hosted endpoint over the internet using your MCP key for authentication. The MCP server URL is specific to your DAVE workspace (tenant).

   The exact format of the MCP server URL and where it is displayed in the platform are not detailed in the feature summary document. The URL is typically displayed alongside the generated key, or in the MCP Keys section of API Management. Look for a field labelled MCP Server URL, Endpoint, or Server in the key detail view.

   The URL will be an HTTPS address specific to your tenant. Copy it exactly as shown: it is case-sensitive and must be used without modification in the Claude Code configuration step that follows.

   Do this

   • In the MCP Keys section of API Management, locate the MCP Server URL or equivalent field.
   • Copy the full HTTPS URL. It is specific to your DAVE workspace.
   • Keep both the MCP key value (copied in Step 2) and the server URL ready for the next step.

   Example

   The MCP server URL will look something like https://your-workspace.hellodave.ai/mcp or a similar HTTPS address. The exact format depends on your tenant configuration. Use the URL shown in the platform, not a guessed or constructed one.

   Best practice

   Do not construct the MCP server URL manually. Use the URL shown in the platform. If the URL is not visible in the MCP Keys section, check the MCP documentation or ask your DAVE Admin. An incorrect URL will cause Claude Code to fail to connect, with a connection refused or not found error.

4. 4

   Add the MCP server to Claude Code

   Claude Code supports MCP servers through its configuration file or through the claude mcp add command. The connection requires two values: the MCP server URL (from Step 3) and your MCP key (from Step 2). Claude Code sends the key as an authorization header on every MCP request.

   Claude Code's MCP configuration accepts servers in the following shape, added to the mcpServers object in your Claude Code configuration:

   {
    "mcpServers": {
    "dave": {
    "type": "http",
    "url": "YOUR_DAVE_MCP_SERVER_URL",
    "headers": {
    "Authorization": "Bearer YOUR_MCP_KEY"
    }
    }
    }
   }

   Replace YOUR_DAVE_MCP_SERVER_URL with the URL copied in Step 3, and YOUR_MCP_KEY with the key value copied in Step 2.

   Alternatively, if Claude Code supports the claude mcp add CLI command in your version, you can add the server from the terminal. Consult the Claude Code documentation for the exact CLI syntax for HTTP MCP servers with authorization headers, as the syntax varies by version.

   Do this

   • Open your Claude Code configuration file (typically ~/.claude/claude_desktop_config.json or the equivalent for your installation).
   • Add a new entry to the mcpServers object using the shape shown above, substituting your DAVE MCP server URL and key.
   • Save the configuration file.
   • Restart Claude Code (or reload the MCP server list if Claude Code supports hot-reload).
   • Confirm the DAVE MCP server appears in Claude Code's connected servers list.

   Example

   After adding the configuration and restarting Claude Code, type a prompt such as: "List the active workflows in my DAVE workspace." If the connection is working, Claude Code will use the DAVE MCP tools to fetch and return the list. If it returns an error or says it cannot access DAVE, check that the URL and key are correct and that the key has not been revoked.

   Best practice

   Store the MCP key in the configuration file using your operating system's secret management where possible (for example, macOS Keychain or a secrets manager), rather than as a plaintext string in the config file. The key grants access to your DAVE workspace: treat it with the same care as a password. If you suspect the key has been exposed, revoke it immediately in DAVE's MCP Keys section and generate a new one.

5. 5

   Verify the connection and confirm audit logging

   After adding the MCP server to Claude Code and restarting, verify that the connection is working and that Claude Code's actions are appearing in the DAVE audit log. Both checks together confirm that the integration is working correctly and that governance is active.

   The audit log records every MCP action with the same context as any other user action: the acting key, the tool called, the parameters, and the timestamp. Because MCP keys are per-user, the audit log entry identifies which user's Claude Code instance performed the action. This is the governance guarantee: Claude Code works inside your DAVE audit boundary, not outside it.

   Do this

   • In Claude Code, send a simple prompt that uses a DAVE MCP tool, such as asking Claude Code to list your DAVE workflows or describe a specific agent.
   • Confirm Claude Code returns a response that reflects real data from your DAVE workspace.
   • In DAVE, navigate to Admin, then Settings and click the Audit Log tab.
   • Look for a recent event with an event type related to the MCP action you just performed (for example, a workflow list read or an agent read).
   • Expand the event row and confirm the Actor field shows your MCP key identifier.
   • Confirm the event timestamp matches the time of your Claude Code prompt.

   Example

   A developer asks Claude Code: "What workflows are active in my DAVE workspace?" Claude Code calls the DAVE MCP tool for listing workflows and returns the results. The developer then checks the DAVE Audit Log and finds a read event timestamped to within seconds of the prompt, with the MCP key as the actor. The integration is confirmed working and audit-logged.

   Best practice

   Run this verification step immediately after connecting Claude Code, not days later. If the audit log shows no MCP events after a successful Claude Code response, check whether your tenant's compliance standards are configured to log read-access events (SOC 2 or GDPR mode in Admin, then Settings, then System Parameters). Without those standards enabled, read-only MCP actions may not generate audit events. Mutating actions (creating or updating records) are always logged regardless of compliance mode.

What MCP gives Claude Code access to

The security model: keys, presets, and the audit trail

What MCP is not: common misconceptions

Frequently asked questions