# Sapiom Dev MCP server

> Enables coding agents to scaffold, test, deploy, and inspect Sapiom agents and web applications locally.

- Repository: https://github.com/sapiom/sapiom-js
- Page: https://hostedmcp.org/servers/sapiom/mcp
- Transport: stdio
- Stars: 22
- License: MIT
- Latest version: 0.20.0

## Install

### Claude Code

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

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

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

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

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

### VS Code CLI

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

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

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

### Codex

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

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

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

### Gemini CLI

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

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

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

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `SAPIOM_ENVIRONMENT` | no | no |  |

## Tools (27)

- `sapiom_authenticate`
- `sapiom_status`
- `sapiom_logout`
- `sapiom_send_feedback`
- `sapiom_dev_agents_scaffold`
- `sapiom_dev_agents_check`
- `sapiom_dev_agents_run_local`
- `sapiom_dev_agents_link`
- `sapiom_dev_agents_clone`
- `sapiom_dev_agents_deploy`
- `sapiom_dev_agents_run`
- `sapiom_dev_agents_inspect`
- `sapiom_dev_agents_signal`
- `sapiom_dev_agents_emit_event`
- `sapiom_dev_agents_schedule`
- `sapiom_dev_agents_schedule_inspect`
- `sapiom_dev_agents_schedule_cancel`
- `sapiom_dev_agents_schedule_secret`
- `sapiom_dev_agents_cron_preview`
- `sapiom_dev_sandbox_configure`
- `sapiom_dev_sandbox_check`
- `sapiom_dev_sandbox_preview`
- `sapiom_dev_app_publish`
- `sapiom_dev_app_list`
- `sapiom_dev_app_settings`
- `sapiom_dev_app_delete`
- `sapiom_dev_map`

## FAQ

### Does the local development tool require an API key?

Local authoring tools like scaffold, check, and run_local do not require Sapiom authentication, though networked tools like deploy and run do.

### How can I authenticate with the Sapiom cloud?

Run the `sapiom_authenticate` tool, which opens a browser login flow and caches your API key in `~/.sapiom/credentials.json`.

### Can I change the deployment environment?

Yes, you can override the default production environment by setting the `SAPIOM_ENVIRONMENT` environment variable to staging or prod.