> ## 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.

# Claude & the Local HTTP Adapter

> Use WalletWall MCP from Claude Code over local stdio, or run the optional loopback HTTP adapter for clients that require Streamable HTTP.

For Claude Code, use the **local stdio plugin**. The HTTP adapter is an advanced, optional bridge for a
client that genuinely requires Streamable HTTP.

> [!WARNING]
>
> **INSTALLABLE · LOCAL · PRE-RELEASE**
>
> Not independently reviewed; see [what you can use today](https://docs.walletwall.org/concepts/product-status.md). Neither path is
> WalletWall-hosted. WalletWall does not host an MCP endpoint, run Claude sessions,
> proxy inference or consume API credits on your behalf. The WalletWall engine runs on your machine;
> model usage stays in your own Anthropic account.

## Recommended: Claude Code over stdio

```bash theme={null}
git clone https://github.com/Wallet-Wall/walletwall-claude.git
cd walletwall-claude
claude --plugin-dir .
```

The plugin starts one local server from `.mcp.json`:

```json theme={null}
{
  "walletwall": {
    "command": "node",
    "args": ["${CLAUDE_PLUGIN_ROOT}/server/walletwall-mcp.mjs"]
  }
}
```

It injects no credentials, sets no environment and starts no other process. The generated distribution
ships the same engine plus four guidance skills:

| Skill | Focus |
| - | - |
| `walletwall-evidence` | Evidence interpretation and tool selection |
| `walletwall-evidence-audit` | Claim decomposition, conflicts, limitations and missing measurements |
| `walletwall-authority` | Authority, provenance, transport, independence and derivation |
| `vault-readiness` | Technical-readiness criteria and blockers |

`walletwall-claude` is a generated distribution, not a second implementation. Its `PROVENANCE.json`
records the pinned `walletwall-copilot` source commit and SHA-512 digests of the generated payload. A
Claude Directory listing is not currently available.

## Advanced: local Streamable HTTP adapter

The source repository also contains `scripts/claude-mcp-http.ts`, which serves the **same six tools and
eleven resources** over Streamable HTTP. It is not part of a WalletWall-hosted service or published MCP
package: you run it yourself from a source checkout.

```mermaid theme={null}
flowchart LR
    accTitle: The optional loopback HTTP adapter
    accDescr: A client you control connects to a loopback HTTP adapter on your machine. The adapter serves the same WalletWall MCP engine locally. Inference stays in the user's provider account; WalletWall hosts no MCP runtime.

    client["Your MCP client"]
    subgraph machine["Your machine"]
        adapter["Loopback adapter<br/>127.0.0.1:8787/mcp<br/>no authentication"]
        engine["WalletWall MCP<br/>six tools · eleven resources"]
    end
    walletwall["WalletWall-hosted runtime:<br/>none"]

    client -->|"Streamable HTTP"| adapter
    adapter --> engine

    class client external;
    class adapter security;
    class engine process;
    class walletwall risk;

    classDef process fill:#BF4E32,stroke:#8B3120,color:#FAF8F3,stroke-width:1.5px;
    classDef risk fill:#8B3120,stroke:#1E1A14,color:#FAF8F3,stroke-width:1.5px;
    classDef external fill:#FAF8F3,stroke:#9A9186,color:#1E1A14,stroke-width:1.5px;
    classDef security fill:#1E1A14,stroke:#C9A47A,color:#FAF8F3,stroke-width:1.5px;
```

### Run it

```bash theme={null}
git clone https://github.com/Wallet-Wall/walletwall-copilot.git
cd walletwall-copilot
npm ci
node scripts/claude-mcp-http.ts --port 8787
```

The adapter prints its endpoint. Check the health route:

```bash theme={null}
curl -s http://127.0.0.1:8787/health
```

```json theme={null}
{"status":"ok"}
```

Point a Streamable HTTP MCP client at `http://127.0.0.1:8787/mcp`. Each `POST` gets a fresh server; the
adapter issues no MCP session ID and keeps no request state between calls.

> [!WARNING]
>
> **The adapter has no authentication.** Anything that can reach the port can call the six read-only
> tools and read the resources. Keep it on `127.0.0.1`. Do not pass `--host 0.0.0.0` or forward the
> port beyond your machine unless you deliberately put your own access control in front of it.

### What it enforces

> [accordion] Network boundary
>
> The default bind address is `127.0.0.1`. `--host` accepts `127.0.0.1` or `0.0.0.0`; any other value
> exits. Browser origins are accepted only from `127.0.0.1` or `localhost` on the adapter's port;
> when bound to `0.0.0.0`, requests carrying an `Origin` header are refused.

> [accordion] Routes, bodies and headers
>
> MCP uses `POST /mcp`; `GET` and `HEAD /health` expose the health check. JSON bodies are limited to
> 512 KiB, URLs to 256 characters, and non-JSON content is refused. Responses use `Cache-Control:
>         no-store`, `X-Content-Type-Options: nosniff` and `Referrer-Policy: no-referrer`; no CORS header is
> emitted.

> [accordion] Timeouts and engine behavior
>
> Headers must arrive within 5 seconds and the full request within 20 seconds. The adapter runs the
> same read-only WalletWall engine: no outbound network, file writes or credentials.

> [accordion] Advanced integration pattern: Claude Managed Agent
>
> The source repository describes a pattern in which a user-owned Anthropic MCP tunnel forwards to this
> local adapter and is attached to a Managed Agent in the user's Anthropic workspace. WalletWall does
> not operate or proxy that tunnel. WalletWall has validated the adapter on loopback, but no complete
> Managed Agent + tunnel run is on record; treat this as an advanced integration pattern rather than a
> verified default path.

The tools are read-only, so reaching the adapter does not grant transaction capability. It can still let
another local process use your machine to evaluate bundles of its own, which is why the loopback boundary
matters.

> [card] [Use Claude Code](https://docs.walletwall.org/mcp/install.md)
>
> Return to the recommended stdio setup.

> [card] [Review the security model](https://docs.walletwall.org/mcp/privacy-security.md)
>
> Understand model-provider visibility, local trust boundaries and package integrity.


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