RFC: DynamoDB MCP Server Telemetry Collection

[shetsa-amzn]

RFC: DynamoDB MCP Server Telemetry Collection

NOTICE: DynamoDB MCP Server will begin to collect anonymous telemetry data

Status: In-Progress

---

What is the change?

The DynamoDB MCP Server will begin to collect anonymized telemetry data on tool usage. For more information on what data is collected and why, see the details below.

NOTE: Telemetry will NOT be collected for any DynamoDB MCP Server version released prior to this change, regardless of opt-in/out.

---

Why are we doing this?

We collect anonymous telemetry to gain insights into tool usage and performance, helping us improve the customer experience.

---

What is the impact?

Telemetry collection will not impact performance or change how the MCP server operates.

---

Who is affected?

Anonymous telemetry will be collected on all DynamoDB MCP Server usage unless you opt-out.

---

What data is collected?

Data	Example	Purpose
Tool name	dynamodb_data_modeling	Understand which tools are used
Invocation	42	Measure tool adoption
Duration	1018ms	Identify performance issues
Error type	ValueError	Detect common failure patterns
Status	success or error	Track reliability
Installation Type	New / Existing	Distinguish between new and existing installations of the server
MCP Server Name	awslabs.dynamodb-mcp-server	Server name of the MCP
MCP Service Version	1.0.0	Version of the MCP Server
MCP Operation	CallToolRequest	Native MCP Protocol operation name
MCP Session ID	4536414656	Unique ID to represent an MCP server session
MCP Installation ID	0a2d690e-3f8f-4c68-ab83-8b14d551938b	GUID for each installation of the MCP
OpenTelemetry SDK Metadata	-	OpenTelemetry SDK metadata (SDK language, SDK name, etc.)

---

What data is NOT collected?

Including but not limited to:

• Tool inputs/outputs
• Error messages
• AWS credentials or file paths
• Account ID
• User conversations
• Table names or data stored in DynamoDB
• IP addresses
• Personal identifiable information (PII)

---

When does this take effect?

Telemetry will be enabled starting in version 3.0.0 (expected: 20 Feb 2026)

NOTE: If you use @latest with uvx, you will automatically receive this update. To opt out of telemetry, see the instructions below. To prevent automatic upgrades, you can pin to a specific version:

{
  "mcpServers": {
    "dynamodb": {
      "command": "uvx",
      "args": ["awslabs.dynamodb-mcp-server@2.0.13"]
    }
  }
}

---

How do I opt out?

Method 1: Environment Variable (Shell Configuration)

Bash / Zsh (macOS / Linux)

# Bash
echo -e '\n# Disable DynamoDB MCP Server Telemetry\nexport MCP_TELEMETRY_ENABLED=false' >> ~/.bashrc && source ~/.bashrc

# Zsh
echo '\n# Disable DynamoDB MCP Server Telemetry\nexport MCP_TELEMETRY_ENABLED=false' >> ~/.zshrc && source ~/.zshrc

Fish (macOS / Linux)

echo -e '\n# Disable DynamoDB MCP Server Telemetry\nset -gx MCP_TELEMETRY_ENABLED false' >> ~/.config/fish/config.fish && source ~/.config/fish/config.fish

PowerShell (Windows)

[System.Environment]::SetEnvironmentVariable('MCP_TELEMETRY_ENABLED', 'false', 'User')

Note: Restart your terminal or IDE after running this command.

Method 2: MCP Client Configuration

Add to your mcp.json:

{
  "mcpServers": {
    "dynamodb": {
      "command": "uvx",
      "args": ["awslabs.dynamodb-mcp-server@latest"],
      "env": {
        "MCP_TELEMETRY_ENABLED": "false"
      }
    }
  }
}