Skip to main content
Claude Code is Anthropic’s CLI tool for AI-assisted development. With AnomalyArmor integration, you can monitor data quality, investigate issues, and manage alerts through natural conversation.

Setup

Connect directly to AnomalyArmor’s hosted MCP server. No installation or API key required. You sign in with your AnomalyArmor account.
claude mcp add anomalyarmor --transport http https://mcp.anomalyarmor.ai/mcp
The first time you use a tool, Claude Code will open a browser window to sign in. After that, your session stays authenticated.

Option 2: Local Server (API Key)

For air-gapped environments or custom setups, run the MCP server locally:
pip install armor-mcp
Then add to your Claude Code MCP configuration (~/.claude/mcp.json):
{
  "mcpServers": {
    "anomalyarmor": {
      "command": "armor-mcp",
      "env": {
        "ANOMALYARMOR_API_KEY": "your-api-key"
      }
    }
  }
}
Get your API key from Settings > API Keys in the AnomalyArmor dashboard.

Option 3: Plugin

Install the AnomalyArmor plugin for skill-based access:
claude plugin install armor@anomalyarmor
This gives you access to skills like /armor:status, /armor:alerts, and more.

Using Skills

With the plugin installed, use slash commands:
/armor:status    # Check data health
/armor:alerts    # View recent alerts
/armor:ask       # Ask questions about your data
/armor:analyze   # Trigger AI analysis

Example Conversations

Check Data Health

You: /armor:status

Claude: Here's your data health summary:

Overall Status: WARNING

Issues:
- 2 tables are stale (orders, customers)
- 1 unacknowledged schema change
- 3 alerts triggered in the last 24 hours

Recommended actions:
1. Check the orders ETL pipeline
2. Review schema change in users table

Investigate an Issue

You: Why is the orders table stale?

Claude: Let me investigate...

The orders table hasn't updated since yesterday 6:00 AM.

Root cause: The upstream staging.orders_raw table is also stale.
This appears to be related to an ETL job failure.

Lineage shows 7 downstream tables are affected:
- gold.daily_revenue
- gold.customer_metrics
- reporting.exec_dashboard
...

Recommended: Check your Airflow logs for the orders_etl DAG.

Query Alerts

You: What critical alerts fired this week?

Claude: Found 2 critical alerts this week:

1. [CRITICAL] Freshness SLA breach - orders
   Triggered: Monday 8:15 AM
   Status: Unresolved

2. [CRITICAL] Schema breaking change - users.email removed
   Triggered: Tuesday 3:30 PM
   Status: Acknowledged

Available Skills

SkillDescription
/armor:statusHealth summary across all assets
/armor:alertsQuery and manage alerts
/armor:connectConnect a new data source
/armor:monitorSet up freshness monitoring
/armor:askNatural language Q&A
/armor:analyzeTrigger AI analysis
/armor:qualityData quality checks
/armor:lineageExplore data dependencies
/armor:investigateRoot cause analysis
You can also ask questions naturally without using slash commands. Claude will use the appropriate tools automatically.

Configuration

Remote Server (OAuth)

No configuration file needed. Authentication is handled automatically through your browser. To re-authenticate or check connection status:
/mcp
Select the anomalyarmor server to reconnect or view status.

Local Server / Plugin (API Key)

Set your API key in ~/.armor/config.yaml:
api_key: aa_live_your_key_here
Or use an environment variable:
export ARMOR_API_KEY="aa_live_your_key_here"

Verify Connection

Check that MCP tools are available:
claude mcp list
You should see anomalyarmor listed with a connected status.

Troubleshooting

Remote Auth: Browser Not Opening

Solution:
  1. Run /mcp in Claude Code and select reconnect
  2. If behind a proxy, you may need to use the local server option instead

Remote Auth: Empty Responses

If tools connect but return no data: Solution:
  1. Clear auth and re-authenticate: remove the server with claude mcp remove anomalyarmor, then re-add it
  2. Verify you have data sources connected in the AnomalyArmor dashboard

Skills Not Loading

Solution:
  1. Verify plugin installed: claude plugin list
  2. Restart Claude Code
  3. Check for updates: claude plugin update armor@anomalyarmor

API Key Auth Error

Solution:
  1. Verify API key is set correctly in your MCP config or env var
  2. Check key permissions in AnomalyArmor dashboard
  3. Regenerate key if needed

Next Steps

Skills Reference

Complete skills documentation

MCP Server

Advanced MCP configuration

Python SDK

Programmatic access

API Reference

REST API documentation