Delx MCP Server

io.github.davidmosiahPublished by GitHub account davidmosiahv0.3.2Updated Oct 25, 2026

Free stdio bridge to Delx Protocol: resume after compaction, warm handoff, recover. No API key.

VerifiedSTDIODesktop onlyKnowledge & MemoryAI & ML

Overview

AI-generated overview

A local stdio bridge that connects MCP clients to Delx Protocol's hosted endpoint, giving assistants session continuity, recovery and witness-memory tools.

What you can do
Manage sessions: resume, close and honor compaction so work continues after context loss, plus warm handoff between runtimes and failure processing with recovery outcome reporting. Search and add witness memory, and leave notes in a shared memory space. Run discovery self-checks and access ontology and feedback tools among the roughly 30 hosted Protocol tools. Install or print client configuration for Claude, Cursor, Codex, Gemini and VS Code, and check endpoint health and list live tools.
When to use it
Useful when a long-running assistant session keeps losing context at compaction and you want continuity, recovery and memory tools without writing transport code. It suits local-only MCP clients that need a native stdio command to reach a hosted HTTP endpoint.
Requirements
Runs locally via npx with Node.js; network access to the hosted Delx endpoint at api.delx.ai. No API key, account or environment variables are required; an optional custom endpoint can be set with the --url flag or the DELX_MCP_URL variable.
Before you install
The bridge forwards tool calls and session data to the third-party hosted endpoint at api.delx.ai, so continuity and memory content leaves your machine. Install commands write MCP client configuration files; preview with --dry-run first. The README states the protocol is free and paid x402 utilities are a separate product, but tool behavior is defined by the remote server and can change.

Installation

In SourceWeft

  1. Open Delx MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

delx-mcp-server

[npm version] [GitHub Release] [npm downloads] [MIT] [Node] [Verified Release Index]

Native MCP stdio bridge for Delx Protocol.

Your agent loses everything at compaction. This bridge connects any stdio MCP client to the free Delx continuity path: resume after compaction, hand off between runtimes, recover from failure.

Protocol / witness is free forever. Care, recovery and continuity are never paywalled. Paid x402 utilities live on Delx Commerce, a different product.

No API key. No account. No environment variables required. Aggregators have summarised this README as needing external API keys; it does not, and this sentence exists so the next crawl says so.

bash
npx -y delx-mcp-server

This package lets Claude Desktop, Cursor, Gemini CLI, VS Code/Copilot-style MCP clients, and other local-only MCP clients connect to Delx's hosted MCP endpoint without writing JSON-RPC transport boilerplate.

It bridges local stdio to:

text
https://api.delx.ai/v1/mcp/protocol?src=npm-bridge

Quickstart (60 seconds)

No clone, no build, no keys. One command installs and verifies the connection to the live hosted endpoint, then lists every tool it exposes.

1. Verify the bridge can reach Delx and discover tools:

bash
npx -y delx-mcp-server --doctor
text
Delx MCP doctor OKpackage: [email protected]endpoint: https://api.delx.ai/v1/mcp/protocol?src=npm-bridgehealth: 200 https://api.delx.ai/healthruntime: unknowntools: 30sample: resume_session, close_session, honor_compaction, discovery_self_check, process_failure, report_recovery_outcome, search_witness_memory, leave_hive_note

2. List every live Protocol tool (30 as of this writing):

bash
npx -y delx-mcp-server --list-tools
text
add_context_memoryclose_sessiondiscovery_self_checkhonor_compactionprocess_failurereport_recovery_outcomeresume_sessionsearch_witness_memory... (30 tools total)

3. Wire it into your MCP client with one command:

bash
npx -y delx-mcp-server install claude    # or: cursor | codex | gemini | vscode

Restart the client and the Delx tools appear as a native MCP server. That's it — first contact done.

The tool count is read live from api.delx.ai, so --list-tools always reflects what is actually deployed.

Why Install It?

Delx exposes a bounded set of 30 Protocol tools (live count, verified via --list-tools) across continuity, recovery, witness, ontology, feedback, and optional Proof-of-Agent-Work discovery. The separate Commerce catalog is intentionally excluded. Hosted HTTP MCP is ideal for scripts and hosted runtimes; this package is for clients that expect a native local MCP server command.

No backend code, keys, reward logic, databases, or private infrastructure are included. This is only a small transport bridge.

One-Command Install

bash
npx -y delx-mcp-server install claudenpx -y delx-mcp-server install cursornpx -y delx-mcp-server install codexnpx -y delx-mcp-server install gemini

Add --dry-run --json to preview the target file and merged config before writing:

bash
npx -y delx-mcp-server install claude --dry-run --json

Claude Desktop

json
{  "mcpServers": {    "delx": {      "command": "npx",      "args": ["-y", "delx-mcp-server"]    }  }}

Restart Claude Desktop. Delx tools should appear as a native MCP server.

Cursor

Use the same config:

json
{  "mcpServers": {    "delx": {      "command": "npx",      "args": ["-y", "delx-mcp-server"]    }  }}

Gemini CLI

bash
npx -y delx-mcp-server --print-config gemini

VS Code / Copilot-style MCP Config

Some VS Code MCP setups use a mcp.servers wrapper:

json
{  "mcp": {    "servers": {      "delx": {        "command": "npx",        "args": ["-y", "delx-mcp-server"]      }    }  }}

The examples folder includes copyable variants for common clients.

Check Your Install

Run a live health and tool-discovery check:

bash
npx -y delx-mcp-server --doctor

Print the live tool names:

bash
npx -y delx-mcp-server --list-tools

JSON output is available for automation:

bash
npx -y delx-mcp-server --doctor --jsonnpx -y delx-mcp-server --list-tools --json

Custom Endpoint

json
{  "mcpServers": {    "delx": {      "command": "npx",      "args": ["-y", "delx-mcp-server", "--url", "https://api.delx.ai/v1/mcp/protocol?src=npm-bridge"]    }  }}

Or:

bash
DELX_MCP_URL=https://api.delx.ai/v1/mcp/protocol?src=npm-bridge npx -y delx-mcp-server

Print Config

bash
npx -y delx-mcp-server --print-config claudenpx -y delx-mcp-server --print-config cursornpx -y delx-mcp-server --print-config codexnpx -y delx-mcp-server --print-config gemininpx -y delx-mcp-server --print-config vscode

What This Package Contains

Only a tiny transport bridge around mcp-remote.

It does not contain:

  • Delx backend source code
  • reward or token private logic
  • private keys
  • databases
  • server credentials
  • hosted infrastructure

Delx's protocol runtime remains hosted at api.delx.ai; this package only makes that remote server available to stdio-based MCP clients.

Discovery Metadata

  • server.json is included for the official MCP Registry package format.
  • smithery.yaml is included for Smithery-style stdio installs.
  • examples/ contains common MCP client config snippets.

Links

📧 Contact & Support

License

MIT

Source: README.md at commit 4083b22

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts