AnomalyArmor MCP Server for Claude

Overview

AnomalyArmor Agents ships armor-mcp, a Model Context Protocol server for data observability. Fifty-two consolidated tools cover health summaries, alerts, freshness, schema drift, data quality, lineage, tags, and AI-driven monitoring recommendations—designed for data teams using Claude Code or Cursor.

Source lives in anomalyarmor/agents. Docs: docs.anomalyarmor.ai.

Features

• Consolidated action-parameter tools to reduce context window usage.
• Health summaries, daily briefings, and alert inbox management.
• Freshness schedules and schema drift monitoring.
• Data quality metrics, validity rules, and referential checks.
• AI recommendations and natural language ask_question intelligence.

Use Cases

• Ask whether warehouse tables are healthy this morning.
• Investigate why the orders table is stale and which dashboards are affected.
• Create freshness monitoring for high-traffic finance tables.
• Review unresolved critical alerts from yesterday.
• Get AI recommendations for tables lacking coverage.

Installation

Claude (Connectors)

1. Generate an aa_live_ API key in AnomalyArmor.
2. Set ARMOR_API_KEY or create ~/.armor/config.yaml.
3. Add uvx armor-mcp to MCP client stdio configuration.
4. Invoke health_summary or get_todays_briefing to verify connectivity.

Claude Code

claude mcp add armor -- uvx armor-mcp
claude mcp list

Other MCP clients

Add the connector using the JSON configuration below in your MCP client settings.

Configuration

{
  "mcpServers": {
    "armor": {
      "command": "uvx",
      "args": ["armor-mcp"]
    }
  }
}

For authenticated setups:

{
  "mcpServers": {
    "armor": {
      "command": "uvx",
      "args": ["armor-mcp"],
      "env": {
        "ARMOR_API_KEY": "aa_live_your_key_here"
      }
    }
  }
}

Alternatively install the Claude plugin: claude plugin install armor@anomalyarmor.

Examples

Health check

Is my data healthy? Summarise alerts, stale tables, and schema changes.

Investigate stale table

Why is the orders table stale and what depends on it?

Recommend monitoring

What should I monitor on my Snowflake warehouse based on table patterns?

Security

• Treat alert rule creation as production-impacting configuration.
• Scope API keys to the minimum AnomalyArmor workspace needed.
• Review ask_question responses before sharing externally—they may quote internal schema names.

Troubleshooting

No API key configured

Set ARMOR_API_KEY or add api_key to ~/.armor/config.yaml.

MCP server not found

Verify uvx is installed and restart the MCP client after config edits.

Empty asset list

Connect a data source and run discovery in AnomalyArmor first.

Plugin skills missing

Run claude plugin list to confirm armor@anomalyarmor is installed.

Duplicate Check

No existing AnomalyArmor or armor-mcp entry was found in content/mcp/. This differs from generic SQL MCP servers because it targets observability alerts, freshness, and schema drift—not ad hoc querying.