mcp-circuit-breaker

Detect repeated MCP tool failures and block retry loops with a circuit breaker.

7|Updated May 26, 2026
One-click install
npx skills add https://github.com/chrono-meta/forge-harness --skill mcp-circuit-breaker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-circuit-breaker
Source: https://github.com/chrono-meta/forge-harness/tree/main/plugins/fh-commons/skills/mcp-circuit-breaker
Command: npx skills add https://github.com/chrono-meta/forge-harness --skill mcp-circuit-breaker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MCP tool failures often trigger cascading retry loops that waste tokens, degrade AI session performance, and produce no useful output, leaving you stuck waiting for unresponsive tools to recover without a clear path forward.

Core Features & Use Cases

  • Failure Pattern Detection: Automatically identifies repeated failures of the same MCP tool and classifies the failure type (timeout, auth error, admin gating, rate limit, etc.) to avoid wasting retries on non-transient issues.
  • Circuit Breaker State Machine: Trips a circuit after configurable failure thresholds to block further calls to the broken tool, preventing token waste from compounding.
  • Ranked Fallback Alternatives: Proposes 3 prioritized fallback options for each failure type, including substitute tools, graceful degradation, and scheduled recovery probes.
  • Use Case: If you are working with a flaky third-party MCP server that keeps timing out, this skill stops the retry loop, suggests using a local alternative or waiting for recovery instead of burning through your token budget.

Quick Start

Invoke the mcp-circuit-breaker skill when you notice an MCP tool failing repeatedly to get failure classification, blocked retries, and ranked fallback options immediately.

Frequently Asked Questions about mcp-circuit-breaker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop MCP tool retry loops from wasting tokens?

To stop MCP tool retry loops from wasting tokens, you can use a circuit breaker state machine that trips after configurable failure thresholds, blocking further calls to the broken tool and preventing cascading retries.

Why does my AI agent get stuck retrying failed MCP tools?

Your AI agent gets stuck retrying failed MCP tools because standard workflows lack failure pattern detection, causing them to attempt calls on non-transient issues like expired credentials or rate-limited APIs without tripping a circuit breaker.

What is a circuit breaker pattern for AI agent tool failures?

A circuit breaker pattern for AI agent tool failures is a state machine that detects repeated MCP errors, blocks further calls to the broken tool after a threshold is reached, and proposes ranked fallback alternatives to preserve session quality.

How do I handle flaky third-party MCP server timeouts?

To handle flaky third-party MCP server timeouts, implement a circuit breaker that classifies the failure type, halts retry loops, and suggests using a local alternative or waiting for recovery via half-open probes instead of burning tokens.

Can I get fallback options when an MCP tool fails with an auth error?

Yes, when an MCP tool fails with an auth error, the circuit breaker classifies the failure type and proposes three prioritized fallback options, including substitute tools, graceful degradation, and scheduled recovery probes.