Klanex MCP

What chrassy/klanex-mcp MCP server does

The chrassy/klanex-mcp MCP server exposes Klanex as an execution layer for agent-initiated HTTP requests. Instead of having an agent call a third-party API directly, the agent submits the request to Klanex and receives an execution record. Klanex can validate a payload before sending it, handle selected transient failures, and return either the target response or a classified error.

The service is intended for workflows where an API call may need durability, approval, or later inspection. It also provides model-oriented error details through an llm_hint, allowing an agent to distinguish a request that needs correction from a failure Klanex is already handling.

How it works

The execute tool accepts an HTTP call and optional controls such as a JSON Schema payload gate, retry and circuit-breaker behavior, an idempotency key, approval requirements, and a stored credential connection. The wait_seconds option can wait for a terminal result for up to 55 seconds; callers can instead inspect the execution later.

Execution state is available through get_execution, while list_executions provides paginated account history with status and time filters. A terminal execution can be submitted again with replay_execution, using the original request bytes rather than asking the model to reconstruct the call. get_usage reports the plan and current-month quota. list_connections exposes references to stored credential connections without placing their secret values in model context.

Setup and configuration

The hosted service exposes https://api.klanexai.com/mcp for production and https://api.sandbox.klanexai.com/mcp for a free-to-try sandbox. Both require a Klanex API key. Clients can send the key in the X-API-Key header; Authorization: Bearer is also supported for clients that require that form.

For stdio-only clients, install and run the klanex-mcp npm package with npx -y klanex-mcp. Set KLANEX_API_KEY in the process environment. Keys beginning with the test prefix route to the sandbox automatically, and KLANEX_MCP_URL can override the selected endpoint.

Tools and capabilities

• Submit HTTP executions with execute.
• Validate payloads against an optional JSON Schema before execution.
• Retry rate limits, timeouts, and 5xx responses with backoff and circuit-breaker handling.
• Use idempotency keys to make retried submissions safer for non-repeatable actions.
• Pause work for an approval decision through API, dashboard, or Slack buttons.
• Inspect status, attempts, responses, and classified errors.
• Replay completed executions byte-for-byte.
• Reference encrypted stored credentials by connection_id.

Limitations and notes

The chrassy/klanex-mcp MCP server is an interface to the hosted Klanex service, not a general local HTTP execution engine. Its production and sandbox endpoints require API keys, and the material does not specify production pricing or quota amounts. The stdio package acts as a proxy to the hosted endpoint, so connectivity to that service remains part of the deployment requirements. The documented wait_seconds blocking period is limited to 55 seconds; longer-running work must be checked asynchronously.