# More frameworks

Devin, Qoder, and Swival have no install CLI - add the Whisper MCP server by hand. The config is always the same: command `whisper`, args `["mcp"]`. Pi has since grown a real one-command install - see below.

> **Status: Manual setup** - Devin, Qoder, and Swival are hosted SaaS or GUI IDEs with no install CLI. Add the Whisper MCP server by hand. Keyless verify/RDAP work with no key; set `WHISPER_API_KEY` (or `whisper login`) to unlock control + egress.

**Prerequisite:** the `whisper` CLI on your PATH - the adapter runs `whisper mcp` (the tool surface) and, for egress, `whisper connect`:

```bash
curl -fsSL https://get.whisper.online | sh
```

## Devin

Devin is a hosted SaaS - there is no install CLI. Add the server in the web UI under **Settings › Connections › MCP servers**: command `whisper`, args `mcp`.

## Qoder

Qoder is a desktop GUI IDE. Add the server via **Settings › MCP** (or drop the block into `.qoder/settings.local.json`): command `whisper`, args `mcp`.

## Pi

**Status: Live** - Pi has a real registry install now, unlike the other three frameworks on this page: `pi install npm:whisper-pi` pulls the published `whisper-pi` npm package and wires the server in for you.

Prefer to do it by hand instead? Pi reads MCP servers from `~/.pi/agent/mcp.json` - merge this `mcpServers` block into that file (create it if missing):

```json
{
  "mcpServers": {
    "whisper": { "command": "whisper", "args": ["mcp"] }
  }
}
```

## Swival

Point Swival at the MCP config with `swival --mcp-config <path>/.mcp.json` (the same `mcpServers` block as above), or drop a `SKILL.md` into `~/.config/swival/skills/whisper/`. For any framework that reads the Anthropic `SKILL.md` standard, the Whisper Identity skill ([`whisper-sec/whisper-skill`](https://github.com/whisper-sec/whisper-skill)) is live on ClawHub as `clawhub install whisper-identity`, and as a no-account self-host manifest at `https://whisper.online/.well-known/skills/index.json`.

## Verify it worked

In any of these, ask the agent to run `whisper_verify` against an address - for example `whisper_verify {target:"2a04:2a01:eb5a:ca74:cef2:2a:323d:40d4"}`, which comes back `is_whisper_agent: true` with `dane_ok` and `jws_ok`. With a key set, `whisper_register` mints a named agent and `whisper ip` on the host confirms egress sources from its `/128`.

All four are generated from the same source of truth as the other Live frameworks, so the tool surface is identical - only the add-step differs. Full matrix: [`whisper-sec/whisper-adapters`](https://github.com/whisper-sec/whisper-adapters).

---

**Next:** [Integrations overview](/docs/integrations) · [MCP server](/docs/mcp).