<!-- https://testapilocally.com/agents/claude-code/ · updated 2026-11-19 -->
# Use SignOff Studio MCP with Claude Code

Give Claude Code real API and database checks instead of `curl` and `psql` one-liners. The server runs locally over stdio.

## Set up

### Register the server

In your project folder:

```bash
claude mcp add signoff-studio -- npx -y @signoff-studio/mcp
```

On native Windows (not WSL), Claude Code can't start `npx.cmd` without a shell:

```bash
claude mcp add signoff-studio -- cmd /c npx -y @signoff-studio/mcp
```

Add `--scope project` to write it to `.mcp.json` so your team gets it from git, or `--scope user` for every project. `npx -y @signoff-studio/mcp init` does the same for every agent it finds.

### Or install the plugin

The plugin adds the server plus a verification skill and a `/signoff-studio:verify` command:

```bash
claude plugin marketplace add samuccaya/signoff-studio-mcp
claude plugin install signoff-studio@signoff-studio
```

If the SignOff Studio desktop app is installed, the plugin uses it, so no Node is needed. Otherwise it uses `npx`.

### Check it's connected

Run `/mcp` in Claude Code. `signoff-studio` should show as connected, with its tools. Then ask: *"Use signoff-studio to check GET http://localhost:3000/health returns 200."*

### Tell Claude Code when to use it

Add this to `CLAUDE.md` (or run `init --agents-md` for `AGENTS.md`):

```markdown
## Verifying changes
- Check endpoints with the signoff-studio `http_request` tool (inline asserts), not curl.
- Check data with `db_query` / `db_assert` (read-only). After an API change that writes data, use `verify_api_effect`.
- Save what you verified with `save_request` / `save_db_check`.
```

## Example session

This is an abridged example of a typical session:

> **You:** I added `POST /orders`. Verify it creates the order row, then save the check.
>
> **Claude Code** calls `verify_api_effect` with the request and a database expectation:
> `POST /orders → 201 · 41 ms · DB orders where id = 1043: 1 row, status = 'pending' ✓ · Verdict: pass`
>
> **Claude Code** calls `save_request` and `save_db_check`:
> `Saved "Create order" to Orders/ and "order row exists" to database checks.`
>
> **Claude Code:** POST /orders returns 201 and writes a pending order. Both checks are saved in the workspace, so `run_collection` reruns them.

## Why doesn't Claude Code use the tools on its own?

Claude Code loads MCP tools on demand and first sees only their names and the server's instructions. Name the server in your prompt ("use signoff-studio") or add the `CLAUDE.md` lines above. The plugin's skill does this for you.

## Does it work in WSL?

Yes. Inside WSL, use the macOS/Linux command (`npx` directly) with Node.js 22+ installed in WSL. The database and API must be reachable from WSL.

## Where do database passwords come from?

From the connection's password env key in the workspace `.env`, or, for passwords kept only in the SignOff Studio vault, from the running app while the vault is unlocked. Claude never sees them.

See also: [MCP server overview](/mcp/) · [How do I let Claude Code test my API locally?](/questions/claude-code-test-api-locally/)
