# FerrLabs MCP server

> Lets an AI assistant drive the FerrLabs suite including FerrFlow, FerrVault, and FerrTrack through a unified API.

- Repository: https://github.com/FerrLabs/MCP
- Page: https://hostedmcp.org/servers/ferrlabs/mcp
- Transport: stdio
- Stars: 0
- License: MPL-2.0

## Install

### Claude Code

```sh
claude mcp add mcp -- npx -y @ferrlabs/mcp
```

### Cursor (`~/.cursor/mcp.json`)

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

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@ferrlabs/mcp"
      ]
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@ferrlabs/mcp"]}'
```

### Claude Desktop (`claude_desktop_config.json`)

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

### Codex

```sh
codex mcp add mcp -- npx -y @ferrlabs/mcp
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.mcp]
command = "npx"
args = ["-y", "@ferrlabs/mcp"]
```

### Gemini CLI

```sh
gemini mcp add -s user mcp npx -- -y @ferrlabs/mcp
```

### Gemini settings.json (`~/.gemini/settings.json`)

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

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `FERRLABS_API_TOKEN` | no | no |  |
| `FERRLABS_MCP_MODE` | no | no |  |

## FAQ

### How do I authenticate with the FerrLabs MCP server?

The server uses an OAuth 2.0 loopback PKCE flow that opens your default browser for the first tool call, or you can inject a FERRLABS_API_TOKEN for headless use.

### Are there any destructive tools I should be careful with?

Yes, tools like delete_team, cancel_subscription, and revoke_token are marked as destructive and should be gated behind a confirmation by the MCP client.
