Voided MCP — Source-aware knowledge for AI

Install

Install the single-file server.

Download this standalone server and point it at an absolute path to your Voided source checkout.

terminal

curl -fsSLo voided-mcp.mjs https://voidednetwork.com/downloads/voided-mcp.mjs
shasum -a 256 voided-mcp.mjs
VOIDED_ROOT=/absolute/path/to/voided node /absolute/path/to/voided-mcp.mjs

SHA-256: 9bd1896067921717ab5e4573f733677bdcaeb3f20dff42cc6db594341249e5b8
Transport: stdio JSON-RPC
Server: voided-mcp version 0.1.0
License: MIT

Client configuration

Point it at a local checkout.

VOIDED_ROOT must be an absolute path to the Voided source checkout the agent should know. Add this server entry using your MCP client’s normal configuration surface.

mcp-config.json

{
  "mcpServers": {
    "voided": {
      "command": "node",
      "args": ["/absolute/path/to/voided-mcp.mjs"],
      "env": {
        "VOIDED_ROOT": "/absolute/path/to/voided"
      }
    }
  }
}

Six tools

Search from context to source.

voided_get_context

Confirm the checkout, discover crates and packages, and get a compact repository orientation.

voided_list_modules

List first-party Rust, Node.js, browser, and knowledge surfaces.

voided_search_knowledge

Search docs, READMEs, and examples for concepts and integration rules.

voided_search_code

Search first-party Rust, TypeScript, and JavaScript source.

voided_find_symbol

Locate a named function, type, constant, or export.

voided_read_file

Read a bounded excerpt from a repository-relative text file.

Recommended sequence

Call context first, search knowledge for intended behavior, find the concrete symbol, then read the smallest relevant excerpt. Search results are capped at 25 and file excerpts at 400 lines.

Boundary

Knowledge server, not crypto runtime.

The server is read-only. It does not edit source or execute cryptographic operations.
It reads the local Voided checkout configured by VOIDED_ROOT.
It does not need Recovery Deck order, plaintext, raw keys, derived keys, or user data.
It makes no Voided backend or network request during normal tool operation.
It is developer knowledge infrastructure, not authentication, recovery, or application runtime behavior.

MCP is one option

Use the smallest context surface that fits.

If an agent cannot run a local MCP server, give it a persistent repository instruction, the reusable Voided skill, or a direct reference file instead.

RULESAGENTS.md block

Compact persistent project instruction

→SKILLVoided skill

Reusable API and safety workflow

→TEXT/llms.txt

Small discovery and routing index

→TEXT/llms-full.txt

Standalone full implementation reference

→

Compare every agent surface →

Local source context for AI.

Install the single-file server.

Point it at a local checkout.

Search from context to source.

Knowledge server, not crypto runtime.

Use the smallest context surface that fits.