AnomalyArmor

What AnomalyArmor MCP server does

AnomalyArmor MCP server gives AI agents access to data observability functions in the AnomalyArmor platform. It covers operational checks and configuration tasks across monitored data assets, including health summaries, alerts, freshness schedules, schema monitoring, data quality, referential integrity, coverage, destinations, lineage, and tags.

The repository also provides 14 slash-command skills for Claude Code. These include onboarding, status checks, alert management, source connections, monitoring setup, natural-language questions, analysis, quality rules, coverage reviews, recommendations, tagging, investigations, lineage, and table profiling.

How it works

The MCP package uses a consolidated tool design: domain-level tools accept an action parameter for related operations. The README lists 29 consolidated MCP tools and describes 52 tools in the package overview. Operations include reading summaries, filtering alerts, creating or modifying rules, testing connections, starting discovery, checking asynchronous job status, and triggering analysis.

An agent can use the server to inspect current conditions or make changes. For example, it can identify stale tables, review unresolved alerts, create a freshness schedule, enable schema monitoring, add null-rate or row-count metrics, configure validity rules, or examine upstream and downstream lineage. Natural-language questions and AI recommendations are also available for supported assets.

Setup and configuration

An AnomalyArmor MCP server deployment requires an AnomalyArmor account and an API key. The key can be supplied through the ARMOR_API_KEY environment variable or stored in ~/.armor/config.yaml under the api_key field.

The documented MCP configuration runs the package with uvx:

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

The README also documents a Claude Code plugin installation through the AnomalyArmor marketplace or skills.sh. After configuration changes, restart the AI tool. If the server is not found, verify that uvx is installed and that the MCP configuration is valid.

Tools and capabilities

The AnomalyArmor MCP server supports these areas:

• Health summaries and daily briefings across monitored assets.
• Alert queries, inbox management, history, trends, acknowledgement, resolution, snoozing, and comments.
• Alert rule creation, updates, deletion, duplication, and enablement controls.
• Asset listing, source creation, connection testing, schema discovery, and asset management.
• Freshness checks and schedules, including pause and resume operations.
• Schema baselines, change lists, monitoring configuration, and dry runs.
• Metrics, validity rules, referential checks, and their results.
• Slack, email, and webhook alert destinations.
• Coverage scoring, monitoring recommendations, natural-language questions, and intelligence generation.
• Lineage graphs, tags, API key information, and asynchronous job status.

Reach for AnomalyArmor MCP server when an agent needs both observability information and configuration controls rather than read-only reporting. The available operations can affect monitoring rules, schedules, destinations, tags, and other platform settings, so clients should confirm intended changes before executing them.