Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.
AnomalyArmor MCP server exists for a simple reason — assistants are far more useful when they can act on AnomalyArmor directly instead of describing what you should do. Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.
AI skills and MCP server for AnomalyArmor data observability. Monitor data quality, detect schema drift, and manage alerts directly from Claude Code, Cursor, or any MCP-compatible AI tool.
skills on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: ARMOR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
ARMOR_API_KEY env var or create ~/.armor/config.yaml:Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by ai.anomalyarmor; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
{
"mcpServers": {
"armor": {
"command": "npx",
"args": ["-y", "skills"],
"env": {
"ARMOR_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
ARMOR_API_KEY env var or create ~/.armor/config.yaml:| Variable | Description | Required |
|---|---|---|
| ARMOR_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.