Skip to content

Install the plugin

The plugin ships as an .mcpb Desktop Extension. You build it from the repo, then drag it into Claude Desktop. Make sure you've covered Before you begin first — you need uv installed.

1. Build the bundle

git clone https://github.com/PrimeDeltaCorp/primedelta-mcp.git
cd primedelta-mcp/mcpb
npm i -g @anthropic-ai/mcpb   # the bundler, once
./build.sh                    # produces primedelta-mcp.mcpb

build.sh writes primedelta-mcp.mcpb in the mcpb/ directory.

2. Add it to Claude Desktop

Open Claude Desktop → Settings → Extensions, then drag primedelta-mcp.mcpb into the window (or double-click the file). Claude Desktop collects the configuration through its own UI on install — see Configure the plugin.

First launch takes a moment

The bundle ships source and resolves its Python environment with uv on first run — expect a minute or two the first time, with network access. Subsequent launches are fast.

3. Where your key lives

In the default browser mode no key is stored at all — your wallet holds it. For privatekey or aws signing, Claude Desktop puts the sensitive value in your OS's native secret store (not a plaintext config file):

OS Secret store
macOS Keychain
Windows Credential Manager
Linux your distro's Secret Service — GNOME Keyring / KWallet, via libsecret

Two things worth knowing:

  • At runtime the key is a plaintext environment variable in the plugin's process. The secret store protects it at rest and during setup, but the running server — and anything that can read its environment — sees the plaintext. So use a dedicated, limited-funds wallet for privatekey, never a personal key, and prefer aws (KMS) where the key never leaves the HSM.
  • On headless Linux with no keyring daemon running, Claude Desktop's fallback isn't documented and can hang or fail — this is a desktop path, so it's rarely an issue, but if you hit it, sign with KMS on a self-hosted server instead.

What "installed" looks like

Once it's running, ask Claude:

What's my session status?

You should get back your network, signing mode, whether a signer is configured, and your active caps and gates. If the signer is missing or the network is wrong, fix it in Configure the plugin. If something errors, see Plugin troubleshooting.


Next → Configure the plugin