---
title: Troubleshooting
description: Common issues and solutions for the Datadog Code Security MCP Server.
breadcrumbs: >-
  Docs > Datadog Security > Code Security > Developer Tool Integrations > Code
  Security MCP Server > Troubleshooting
---

# Troubleshooting

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site). ().
{% /alert %}

{% /callout %}

If you experience issues with the [Datadog Code Security MCP Server](https://docs.datadoghq.com/security/code_security/dev_tool_int/mcp_server/), use the following solutions to diagnose and resolve common problems.

{% alert level="info" %}
This MCP server is separate from the [Datadog MCP Server](https://docs.datadoghq.com/bits_ai/mcp_server), which provides cloud-based access to Datadog features and data. The Code Security MCP Server runs locally and focuses on code-level security scanning.
{% /alert %}

## Binary not found{% #binary-not-found %}

If a scan returns an error about a missing binary, install it using the instructions in the [Install security binaries](https://docs.datadoghq.com/security/code_security/dev_tool_int/mcp_server/#install-security-binaries) section.

## Authentication errors{% #authentication-errors %}

Check that your API and application keys are set:

```shell
echo $DD_API_KEY
echo $DD_APP_KEY
echo $DD_SITE
```

If the values are set but scans still fail, verify your keys have the correct permissions. See [API and Application Keys](https://docs.datadoghq.com/account_management/api-app-keys/) for details.

## MCP server not responding{% #mcp-server-not-responding %}

1. Check that the binary is installed and accessible:

   ```shell
   datadog-code-security-mcp version
   ```

1. Check MCP server logs:

   ```shell
   tail -f ~/Library/Logs/Claude/mcp*.log
   tail -f ~/.claude/logs/mcp*.log
   ```

1. Verify your client configuration points to the correct binary path. If installed through Homebrew, the binary should be on your `PATH`. Otherwise, use an absolute path in your configuration.

## Partial results{% #partial-results %}

When running a comprehensive scan, some scan types may succeed while others fail (for example, if only some binaries are installed). The server returns:

- Results from all successful scanners.
- Error messages with installation instructions for any scanners that failed.

This is expected behavior. Install the missing binaries and re-run to get complete results.

## Further Reading{% #further-reading %}

- [Code Security MCP Server overview and setup](https://docs.datadoghq.com/security/code_security/dev_tool_int/mcp_server/)
- [Tools Reference](https://docs.datadoghq.com/security/code_security/dev_tool_int/mcp_server/tools_reference/)