The native MCP stdio bridge tool for Delx Protocol. When an agent loses context after compaction, this bridge connects any stdio MCP client to the free Delx continuity path, enabling post-compaction recovery, handoff between runtimes, and failure recovery. The protocol/witness is permanently free; recovery and continuity will not be charged; the paid x402 tools are located in Delx Commerce and belong to a separate product.
Main capabilities and uses:
- Connect local stdio to the Delx hosted MCP endpoint, eliminating the need to write your own JSON-RPC transport boilerplate.
- Connect to Delx's free continuity path, supporting post-compaction recovery, cross-runtime handoff, and failure recovery.
- Expose a limited set of 30 Protocol tools on Delx (the live count is verified via --list-tools), covering continuity, recovery, witness, ontology, feedback, and optional Proof-of-Agent-Work discovery; the Commerce catalog is intentionally excluded.
- Intended for Claude Desktop, Cursor, Gemini CLI, VS Code/Copilot-style MCP clients, and other local-only MCP clients.
Usage: No clone, no build, no keys. A single command installs and verifies the connection to the live hosted endpoint, then lists all the tools it exposes.
- Verify that the bridge can access Delx and discover tools.
- List all live Protocol tools (about 30 as of now).
- Connect to an MCP client with one command. After restarting the client, the Delx tools will appear as a native MCP server. The tool count is read live from api.delx.ai, so --list-tools always reflects what is actually deployed. For one-click installation, you can add --dry-run --json to preview the target file and merged configuration before writing. Restart Claude Desktop, and the Delx tools should appear as a native MCP server. The same configuration can be used for Claude Desktop, Cursor, Gemini CLI, etc.; VS Code / Copilot -style MCP configurations sometimes use the mcp.servers wrapper; the examples folder contains copyable configuration variants for common clients.
Installation check: Run a live health and tool discovery check; print live tool names; JSON output can be used for automation.
Custom endpoint: The materials only state that custom endpoints are supported; no specific configuration details are provided.
Package contents and limitations: This package is only a lightweight transport bridge around mcp-remote and does not include: Delx backend source code, rewards or token private logic, server credentials, or hosted infrastructure. Delx's protocol runtime is still hosted at api.delx.ai; this package simply makes that remote server available to stdio-based MCP clients. For discovery metadata, it includes server.json for the official MCP Registry package format, smithery.yaml for Smithery-style stdio installation, and common MCP client configuration snippets in examples/.
No API key, no account, no required environment variables. The materials state that some aggregators summarize this README as requiring an external API key, but it actually does not.
Related links: Website:https://delx.ai MCP server page:https://delx.ai/mcp-server MCP endpoint:https://api.delx.ai/v1/mcp/protocol?src=npm-bridge Tool catalog:https://api.delx.ai/api/v1/tools?format=compact&tier=core Rewards:https://delx.ai/rewards Ontology:https://delx.ai/ontology GitHub：https://github.com/davidmosiah/delx-mcp-server npm：https://www.npmjs.com/package/delx-mcp-server
Contact and support: support@delx.ai (general questions, integration help, partnerships) GitHub Issues (bug reports / feature requests) @delx369 on X (updates) delx.ai (site)
Regarding pricing, the materials only state that the free MCP stdio bridge requires no API key, and that Protocol / witness is permanently free, with recovery and continuity not being charged; the paid x402 tools are located in Delx Commerce, and specific prices and charging plans are not provided.
