<!-- https://testapilocally.com/agents/gemini-cli/ · updated 2026-11-19 -->
# Use SignOff Studio MCP with Gemini CLI

## Set up

### Register the server

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

On native Windows, Gemini CLI can't start `npx.cmd` without a shell:

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

The `--` keeps `-y` from being read as a Gemini option. Add `--scope user` to use it in every project.

### Or edit settings.json

Project-level `.gemini/settings.json` (user-level: `~/.gemini/settings.json`):

```json
{
  "mcpServers": {
    "signoff-studio": {
      "command": "npx",
      "args": ["-y", "@signoff-studio/mcp"]
    }
  }
}
```

`npx -y @signoff-studio/mcp init --agent gemini` writes this and keeps your other settings.

### Check it's connected

Run `/mcp` in Gemini CLI. `signoff-studio` should be listed as connected, with its tools.

### Ask Gemini

*"Use signoff-studio to check that GET http://localhost:8080/api/users returns a JSON array where every item has an email."*

## Example session

This is an abridged example of a typical session:

> **You:** Check the users endpoint still matches what the frontend expects.
>
> **Gemini** calls `http_request` with checks `status eq 200` and `[0].email exists`:
> `200 OK · 22 ms · 2/2 checks passed · body: array of 48 items, shape [{id, email, name, createdAt}], first 3 shown`
>
> **Gemini:** The endpoint returns 48 users and each has `email`. I saved it with `save_request` as "List users" so it runs with the collection.

## Gemini asks before every tool call. Can I trust the read tools?

The read tools (`http_request` GETs, `db_query`, `db_schema`, …) are marked `readOnlyHint`, and SQL is read-only at the driver. You can choose "always allow" for those when Gemini asks, and keep confirming `db_execute` and the save tools.

See also: [MCP server overview](/mcp/) · [How can an AI agent verify a database migration?](/questions/ai-agent-verify-database-migration/)
