Purpose
klanex-mcp is the MCP (Model Context Protocol) server for klanex, with the goal of providing a reliable asynchronous execution layer for agents' tool calls. It sits between the agent's tool-use intent and the real third-party API, ensuring that every call can "land".
Main Capabilities
- Schema validation: After passing in payload_schema, hallucinated payloads will be rejected before execution; on mismatch, it returns synchronously with correction hints.
- Fault absorption: Transient failures such as 429s, timeouts, and 5xx are handled by klanex through retries, backoff, and circuit-breaking mechanisms, without requiring agent intervention.
- Idempotency: Through idempotency_key, submissions can be safely retried, preventing operations such as refunds from being executed repeatedly due to network fluctuations.
- Approval threshold: requires_approval can pause execution and wait for a human to approve or reject through the API, dashboard, or Slack button.
- Credential security: Credentials are stored once as a connection, injected by klanex at execution time, and do not enter the model context.
- Readable errors: Every error carries an llm_hint, telling the agent what needs to be fixed, or explaining that klanex is already handling it, thereby allowing the agent to self-correct.
- Audit and reporting: An audit trail is retained, and results are reported back via signed webhook.
Usage
Hosted connection (recommended)
klanex's MCP server is hosted, so no installation is required if the client supports HTTP transport:
- Get an API key at klanexai.com; sandbox keys are free.
- Configure the connection in Cursor / Windsurf / VS Code (mcp.json).
- For clients that can only set the Authorization header, you can use
Authorization: Bearer klx_....
stdio proxy connection
For clients that only support stdio (such as Claude Desktop), this package provides the ability to proxy stdio to the hosted endpoint:
- The proxy routes by key prefix,
klx_test_…keys automatically point to the sandbox. - The address can be overridden by setting
KLANEX_MCP_URL.
Full API documentation: api.klanexai.com/docs
Applicable Scenarios
- An agent needs to call a third-party API, and the call result must reliably land.
- Scenarios where hallucinated payloads must be prevented from executing, rate limits and failures must be handled, idempotency guarantees are needed, human approval is needed for high-risk operations, or credentials need to be isolated outside the model context.
Limitations
The materials do not provide specific limitation information regarding pricing, supported platform scope, rate limits, SLA, etc., and none is currently provided.
