SelfHeal MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SELFHEAL_CONFIG | No | Config file path for proxy mode | ./selfheal.config.json |
| SELFHEAL_MAX_RETRIES | No | Max retry attempts | 3 |
| SELFHEAL_MAX_DELAY_MS | No | Max delay cap | 30000 |
| SELFHEAL_BASE_DELAY_MS | No | Base delay for backoff | 1000 |
| SELFHEAL_CIRCUIT_THRESHOLD | No | Failures before circuit opens | 5 |
| SELFHEAL_CIRCUIT_COOLDOWN_MS | No | Cooldown before half-open test | 120000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wrap_callA | Execute a function call with retry, circuit breaker, and metrics. Pass a target name and the function will be retried on transient failures. Use this to wrap any unreliable external call. |
| circuit_statusA | Check the health status of a target. Returns circuit state, failure count, and cooldown. |
| circuit_resetA | Reset a circuit breaker back to closed (healthy). Use after fixing the underlying issue. |
| metricsA | Get observability metrics — success rates, latency, top errors, breakdown by tool and target. |
| recent_errorsA | Get the most recent failed calls with full error details and retry logs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clear, distinct purpose. circuit_reset and circuit_status are for circuit breaker state management, metrics for system observability, recent_errors for error inspection, and wrap_call for executing calls with resilience. There is no overlap or ambiguity between them.
The naming uses snake_case but mixes patterns: some tools start with a noun (circuit_*), some with an adjective (recent_errors), and one with a verb (wrap_call). While readable, the lack of a consistent verb_noun or noun_verb pattern reduces predictability.
With 5 tools, the server covers the essential resilience operations without being bloated. The number is appropriate for a focused self-healing utility, though a few additional tools (e.g., for configuration) could be added without harm.
The tool set covers the core lifecycle of circuit breakers, error tracking, and metrics. However, it lacks configuration tools for setting circuit breaker parameters or managing targets, which might be needed for full autonomy.