Blacksmith MCP is an MCP server that connects Claude to Blacksmith CI data, allowing users to query workflow runs, analyze test failures, detect flaky tests, and monitor usage through natural conversation.
From the registry: MCP server for Blacksmith CI - query runs, analyze test failures, detect flaky tests.
Please install the `blacksmith` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Blacksmith account + Chrome session** — Log in at app.blacksmith.sh in Chrome so the MCP server can auto-extract your session cookie (or set BLACKSMITH_SESSION_COOKIE manually). (https://app.blacksmith.sh)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["blacksmith-mcp"]
- required environment variables:
- `BLACKSMITH_ORG`: Blacksmith organization name (example: `<your-blacksmith-org>`)
- optional environment variables:
- `BLACKSMITH_SESSION_COOKIE`: Blacksmith session cookie (auto-extracted from Chrome when possible) (example: `<your-blacksmith-session-cookie>`)
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.BLACKSMITH_ORGrequiredYour Blacksmith organization nameBLACKSMITH_SESSION_COOKIESession cookie (auto-extracted from Chrome if not set)Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.