Skip to main content
Glama

klanex MCP server

npm MCP Marketplace

Reliable execution for agent tool calls, as an MCP server.

klanex is an async execution layer between an agent's tool-use intents and real third-party APIs: it schema-gates hallucinated payloads before anything runs, absorbs rate limits and outages with retries/backoff/circuit breakers, encrypts credentials, keeps an audit trail, and reports back via signed webhooks. With this MCP server, an agent submits a call once — klanex makes sure it lands.

Failures come back written for the model: every error carries an llm_hint telling the agent exactly what to fix (or that klanex is already handling it), so agents self-correct instead of guessing.

klanex's MCP server is hosted — no install needed if your client supports HTTP transports:

Endpoint

Environment

Keys

https://api.klanexai.com/mcp

production

klx_live_…

https://api.sandbox.klanexai.com/mcp

sandbox (free to try)

klx_test_…

Get an API key at klanexai.com — sandbox keys are free.

Claude Code

claude mcp add --transport http klanex https://api.klanexai.com/mcp \
  --header "X-API-Key: klx_live_..."

Cursor / Windsurf / VS Code (mcp.json)

{
  "mcpServers": {
    "klanex": {
      "url": "https://api.klanexai.com/mcp",
      "headers": { "X-API-Key": "klx_live_..." }
    }
  }
}

Authorization: Bearer klx_... works too, for clients that can only set that header.

Related MCP server: permitd MCP Server

Connect (stdio shim)

For clients that only speak stdio (e.g. Claude Desktop), this package proxies stdio to the hosted endpoint:

{
  "mcpServers": {
    "klanex": {
      "command": "npx",
      "args": ["-y", "klanex-mcp"],
      "env": { "KLANEX_API_KEY": "klx_live_..." }
    }
  }
}

The shim routes by key prefix — klx_test_… keys go to the sandbox automatically. Set KLANEX_MCP_URL to override.

Tools

Tool

What it does

execute

Submit an HTTP call for reliable async execution: optional JSON Schema gate, retries/backoff/circuit breakers, idempotency keys, human approval gates, encrypted credentials. wait_seconds blocks up to 55s for the terminal result.

get_execution

Current status, attempts, target response, or classified error for an execution.

list_executions

The account's executions, filterable by status/time, paginated.

replay_execution

Re-run a terminal execution byte-exact — outage recovery without re-prompting the LLM.

get_usage

Plan and current-month usage/quota.

list_connections

Stored credential connections (token vault) to reference via connection_id — so secrets never pass through model context.

Why this beats calling APIs directly

  • Hallucinated payloads are rejected before they execute — pass payload_schema and mismatches return synchronously with a correction hint.

  • Transient failures are not the agent's problem — 429s, timeouts, and 5xxs are retried with backoff behind a circuit breaker; the agent does nothing.

  • A network blip can never double-execute a refund — idempotency_key makes submits safe to retry.

  • Destructive actions can wait for a human — requires_approval pauses execution for an approve/reject decision (API, dashboard, or Slack buttons).

  • Credentials stay out of model context — store them once as a connection; klanex injects them at execution time.

Full API docs: api.klanexai.com/docs

License

MIT

Available Tools

3 tools
get_executionAInspect

Fetch the current state of an execution by ID: status (PENDING_APPROVAL|QUEUED|RUNNING|RETRYING|SUCCEEDED|FAILED), attempts, the target response on success, or a classified error on failure. Retryable failures need no action from you — klanex is still retrying. Header values always read back REDACTED.

Inputs: execution_id (required).

get_usageAInspect

Report the account's plan and execution usage for the current calendar month: used, included_executions, remaining, and whether overage is allowed. Check this before large batches to avoid hitting a hard quota.

replay_executionAInspect

Re-run a terminal (SUCCEEDED or FAILED) execution as a brand-new execution: same target, byte-exact original payload, same sealed credentials, fresh attempt counter. This is the outage-recovery path — failed calls can be re-executed without regenerating the payload. Each call creates a new execution (deliberately not idempotent).

Inputs: execution_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_execution fetches execution state, get_usage reports account usage, and replay_execution re-runs a terminal execution. No ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: get_execution, get_usage, replay_execution. No deviations.

    Tool Count3/5

    Only 3 tools for an execution management platform is on the low end. While focused, typical CRUD operations would benefit from more tools (e.g., create, list, cancel).

    Completeness2/5

    Obvious gaps exist: no tool to create a new execution (only replay), no list/cancel functionalities. The workflow is incomplete for full lifecycle management.

    Maintenance

    ActivityStale
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides a trust and governance layer for AI agents, enabling secure API access, credential vaulting, paid execution with human approval, and automatic call resume.
      2
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables governed tool-calling agents with policy decisions, optional human approval, hash-chained audit logging, and deterministic evaluation.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to execute real-world API actions with exactly-once reliability, deduplication, auditing, and human-in-the-loop safeguards via MCP.
      3
      -