Blacksmith MCP Server

MCP server for Blacksmith CI - query runs, analyze test failures, detect flaky tests.

Local serverstdio

What is the Blacksmith MCP server?

Connect Blacksmith to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for Blacksmith CI - query runs, analyze test failures, detect flaky tests. The blacksmith mcp server is what makes that connection.

What the server does

An MCP server that connects Claude to your Blacksmith CI data. Query workflow runs, analyze test failures, detect flaky tests, and monitor usage—all through natural conversation.

  • "Why did the last CI run fail?"
  • "Which tests are flaky this week?"
  • "Compare test failures between main and my PR"
  • "What's using the most cache storage?"

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • get_current_usage — Current core usage (active vs max)
  • get_invoice_amount — Current billing period amount
  • get_usage_summary — Billable minutes vs free tier
  • get_cache_stats — Cache size, entries by repository
  • get_cache_entries — Detailed cache entries for a repo
  • Authentication — The Authentication tool exposed by this server
  • Organization — The Organization tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: BLACKSMITH_ORG. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Installation goes through your MCP client rather than a global install: point it at blacksmith-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Blacksmith's toolset — get_current_usage, get_invoice_amount, get_usage_summary and 4 more — is a fair guide to whether it matches your workflow. It is maintained by grahamnotgrant; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Blacksmith's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
get_current_usageCurrent core usage (active vs max)
get_invoice_amountCurrent billing period amount
get_usage_summaryBillable minutes vs free tier
get_cache_statsCache size, entries by repository
get_cache_entriesDetailed cache entries for a repo
AuthenticationThe Authentication tool exposed by this server.
OrganizationThe Organization tool exposed by this server.

How to install the Blacksmith MCP server

{
  "mcpServers": {
    "blacksmith": {
      "command": "npx",
      "args": ["-y", "blacksmith-mcp"],
      "env": {
        "BLACKSMITH_ORG": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
BLACKSMITH_ORGConfiguration value read at startup.Optional

Example prompts to try

  • Use Blacksmith to get current usage.
  • Use Blacksmith to get invoice amount.
  • Use Blacksmith to get usage summary.

Frequently asked questions

It connects Blacksmith to MCP-compatible AI assistants such as Claude and Cursor, exposing 7 tools (get_current_usage, get_invoice_amount, get_usage_summary, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Blacksmith directly.