This product is not supported for your selected
Datadog site. (
).
このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、
お気軽にご連絡ください。
If you experience issues with the Datadog Code Security MCP Server, use the following solutions to diagnose and resolve common problems.
This MCP server is separate from the
Datadog 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.
Binary not found
If a scan returns an error about a missing binary, install it using the instructions in the Install security binaries section.
Authentication errors
Check that your API and application keys are set:
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 for details.
MCP server not responding
Check that the binary is installed and accessible:
datadog-code-security-mcp version
Check MCP server logs:
tail -f ~/Library/Logs/Claude/mcp*.log
tail -f ~/.claude/logs/mcp*.log
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
When running a comprehensive scan (datadog_code_security_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
