datadome

The DataDome MCP server exposes a set of management API driven tools that interact with the DataDome dashboard. It implements endpoints to fetch account settings, list and filter endpoints, retrieve custom protection rules, create new custom rules, and obtain account usage metrics. You can access these tools through MCP clients or inspectors that communicate over the MCP protocol using the provided server configuration. Tools include: get_account_settings, get_all_endpoints, get_custom_rules, create_custom_rule, and get_account_usage. These enable integration with customer dashboards and automation pipelines to monitor and manage DataDome protections.

To use the server in your MCP-enabled application, configure the mcpServers entry with the path to the running server (via node) and supply your DataDome management API key in the DD_MGMT_KEY environment variable. Once running, MCP-enabled clients can invoke the available tools to perform tasks such as retrieving account quotas and endpoint configurations, or creating and retrieving custom rules for protection.

Prerequisites:

• Node.js and npm installed
• Access to the DataDome Management API and a valid DD_MGMT_KEY

Install and set up:

1. Clone the repository and navigate to the project directory.
2. Install dependencies:

npm install

3. Copy the example environment file and set your DataDome management API key:

cp .env.example .env

4. Build the server:

npm run build

5. Run the MCP server (example):

node dist/main.js

6. Configure the MCP client with the server details and your key as described in the documentation.

Notes and tips:

• Ensure DD_MGMT_KEY is kept secret and not checked into version control.
• The MCP server uses the DataDome Management API; rate limits and permissions apply as per your DataDome plan.
• When configuring in MCP clients, specify the absolute path to dist/main.js as shown in the example configuration.
• If you modify environment variables or server startup, restart the MCP server to apply changes.
• For debugging, you can test tools via MCP Inspector as mentioned in the README.
• If you encounter issues launching the server, verify that the build step completed successfully and that the dist/main.js path is correct.