> ## Documentation Index
> Fetch the complete documentation index at: https://docs.walletwall.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Install & Connect

> Run WalletWall MCP locally over stdio in GitHub Copilot, Claude Code or any MCP client, then verify the exact server surface you connected.

> [!NOTE]
>
> **INSTALLABLE · LOCAL · PRE-RELEASE**
>
> Not independently reviewed. See [what you can use today](https://docs.walletwall.org/concepts/product-status.md) for every surface
> side by side.

WalletWall MCP is a **local stdio server**. Your MCP client starts it as a child process and exchanges
JSON-RPC messages over standard input and output. There is no WalletWall account, API key or hosted MCP
service to configure.

## Requirements

* **Node.js 22.18 or newer**, available as `node` on your `PATH`.
* **Git**, when you install from a repository clone.
* No WalletWall account, credential or hosted service.

## Choose your client

> [tab] GitHub Copilot
>
> Add the WalletWall repository as a plugin marketplace, then install the plugin:
>
> ```bash theme={null}
> copilot plugin marketplace add Wallet-Wall/walletwall-copilot
> copilot plugin install walletwall@walletwall
> ```
>
> Start a **new** session afterwards. The plugin bundles the local server, four skills and the
> WalletWall canvas. See [GitHub Copilot](https://docs.walletwall.org/mcp/github-copilot.md) for the full integration guide.

> [tab] Claude Code
>
> Clone the Claude distribution and point Claude Code at it as a local plugin directory:
>
> ```bash theme={null}
> git clone https://github.com/Wallet-Wall/walletwall-claude.git
> cd walletwall-claude
> claude --plugin-dir .
> ```
>
> The plugin launches its committed `server/walletwall-mcp.mjs` over stdio and adds four skills. It
> is a generated distribution of the same WalletWall engine, not a second implementation. See
> [Claude / local HTTP adapter](https://docs.walletwall.org/mcp/claude-local-adapter.md).

> [tab] Any MCP client
>
> Clone the source repository:
>
> ```bash theme={null}
> git clone https://github.com/Wallet-Wall/walletwall-copilot.git
> ```
>
> Register `plugin/server/walletwall-mcp.mjs` as a local stdio server. The committed bundle imports
> only Node.js built-ins and runs without `npm install`:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "walletwall": {
>       "type": "stdio",
>       "command": "node",
>       "args": ["/absolute/path/to/walletwall-copilot/plugin/server/walletwall-mcp.mjs"]
>     }
>   }
> }
> ```
>
> The configuration file location depends on your client. Add no server arguments or environment
> variables beyond the absolute file path: the stdio server reads neither.

## Verify the connection

A current WalletWall MCP connection should have all three of these properties:

**1. Six tools**

Your client lists exactly `resolve_asset`, `normalize_observation`, `inspect_evidence`,
`check_invariants`, `trace_provenance` and `assess_vault_readiness`. GitHub Copilot displays the
server name as a prefix, for example `walletwall-resolve_asset`.

**2. Eleven resources**

The server lists eleven `walletwall://` resources. A server that lists six is an older build.

**3. Read the conformance resource**

Read `walletwall://conformance/version`. It reports the WWEP, registry, policy and rules versions
and the content digests of the bundled registry, policies and specification.

> [card] [Run the Quickstart](https://docs.walletwall.org/mcp/quickstart.md)
>
> Exercise the real server with synthetic evidence and no WalletWall-hosted runtime.

> [card] [Understand WWEP](https://docs.walletwall.org/mcp/evidence-model.md)
>
> Learn what the states mean before using them in an application.

## Optional: loopback HTTP

stdio is the default and the only transport inside the published packages. If a client can connect only
over HTTP, the source repository also contains an optional Streamable HTTP adapter bound to
`127.0.0.1` by default. You run it yourself; WalletWall does not host it.

> [card] [Claude / local HTTP adapter](https://docs.walletwall.org/mcp/claude-local-adapter.md)
>
> When to use the adapter, how to run it, and the security boundary around its unauthenticated port.

## Package, registry and version details

> [accordion] Official MCP Registry listing
>
> WalletWall is listed as `io.github.Wallet-Wall/walletwall` in the official MCP Registry. The
> registry hosts metadata only; the MCPB package is a GitHub Release asset.
>
> | Field | Value |
> | - | - |
> | Latest listed version | `0.2.1` (the earlier `0.2.0` remains listed) |
> | Package | MCPB, `walletwall.mcpb` on the `v0.2.1` release |
> | Transport | `stdio` |
> | `fileSha256` | `ea034481c9319bd0221b7de686fa82d163f870247d32249239171689131963cc` |
>
> Query the listing yourself:
>
> ```bash theme={null}
> curl -s "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.Wallet-Wall/walletwall"
> ```
>
> The listing's repository and package URLs still use the former repository name,
> `walletwallrus-copilot`; GitHub redirects them. The older `0.2.0` package serves six resources and
> no shape diagnostics, so prefer `0.2.1`.

> [accordion] Verify the MCPB bytes
>
> The MCPB contains `manifest.json`, `server/walletwall-mcp.mjs`, `LICENSE` and
> `THIRD_PARTY_NOTICES.md`. Before using a downloaded package, compare its digest with the Registry
> listing:
>
> ```bash macOS and Linux theme={null}
> shasum -a 256 walletwall.mcpb
> ```
>
> ```powershell Windows theme={null}
> Get-FileHash walletwall.mcpb -Algorithm SHA256
> ```
>
> A digest match identifies the bytes named by the listing; it is not a signature or certification.
> In the source repository, `npm run verify:bundle` rebuilds the server and `npm run verify:mcpb`
> repacks the MCPB and compares the deterministic digests.

> [accordion] Version matrix
>
> Versions at the time of writing (November 2026):
>
> | Domain | Version |
> | - | - |
> | WalletWall MCP engine | `0.1.0` |
> | WWEP | `0.1` (draft) |
> | Bundled registry | `0.2.0`, verified point in time on 2026-10-24 |
> | Authority policies | `0.1.0-draft` |
> | Derivation and readiness rules | `0.1.0-draft` |
> | MCPB package | `0.2.1` |
> | GitHub Copilot plugin | `0.3.0` |
> | Claude Code plugin | `0.3.1` |
> | WallPrint | `0.1` |
>
> Version strings do **not** pin the MCP surface: older builds have reported the same engine or plugin
> version while serving six resources instead of eleven. When exact behavior matters, inspect the
> server you are actually running: count its resources and read `walletwall://conformance/version`.

## Uninstall

> [tab] GitHub Copilot
>
> ```bash theme={null}
> copilot plugin uninstall walletwall
> copilot plugin marketplace remove walletwall
> ```

> [tab] Claude Code
>
> Stop passing `--plugin-dir` and delete the local clone.

> [tab] Any MCP client
>
> Remove the `walletwall` entry from your client's MCP configuration.

The WalletWall stdio server writes no cache or query history of its own. Your client's plugin
directories and logs are managed by your client.

## Where to go next

> [card] [GitHub Copilot](https://docs.walletwall.org/mcp/github-copilot.md)
>
> The plugin's four skills, the WalletWall canvas and its trust boundary.

> [card] [Claude / local HTTP adapter](https://docs.walletwall.org/mcp/claude-local-adapter.md)
>
> The Claude Code plugin and the optional loopback adapter.

> [card] [Privacy & Security](https://docs.walletwall.org/mcp/privacy-security.md)
>
> What runs where, and what your AI client and model provider can see.

> [card] [Troubleshooting](https://docs.walletwall.org/mcp/troubleshooting.md)
>
> Discovery and configuration problems, by symptom.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.