Skip to main content
For Claude Code, use the local stdio plugin. The HTTP adapter is an advanced, optional bridge for a client that genuinely requires Streamable HTTP.
INSTALLABLE · LOCAL · PRE-RELEASENot independently reviewed; see what you can use today. 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.
The plugin starts one local server from .mcp.json:
It injects no credentials, sets no environment and starts no other process. The generated distribution ships the same engine plus four guidance skills: 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.

Run it

The adapter prints its endpoint. Check the health route:
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.
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

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

Use Claude Code

Return to the recommended stdio setup.

Review the security model

Understand model-provider visibility, local trust boundaries and package integrity.