portainer-mcp

# Install the MCP server portainer-mcp (`io.github.ginkida/portainer-mcp`)

Its page: https://plug.directory/servers/io.github.ginkida/portainer-mcp

It runs on the person's machine and needs uv installed.

Use the section for the person's client.

## Claude Desktop, Cursor, Devin Desktop, Cline, LM Studio, Gemini CLI, mcp-client-cli, oterm, TUUI, BoltAI, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI

Merge into the place for the person's client:

- Claude Desktop: claude_desktop_config.json (Settings › Developer › Edit Config)
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- mcp-client-cli: ~/.llm/config.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- TUUI: resources/assets/config/mcp.json in the installed app
- BoltAI: ~/.boltai/mcp.json
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)

```json
{
  "mcpServers": {
    "portainer-mcp": {
      "command": "uvx",
      "args": ["portainer-mcp"]
    }
  }
}
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport stdio portainer-mcp -- uvx portainer-mcp
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "portainer-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": ["portainer-mcp"]
    }
  }
}
```

## Zed

Merge into ~/.config/zed/settings.json:

```json
{
  "context_servers": {
    "portainer-mcp": {
      "command": "uvx",
      "args": ["portainer-mcp"]
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "portainer-mcp"
    type: stdio
    command: "uvx"
    args:
      - "portainer-mcp"
```

## Goose

Merge into ~/.config/goose/config.yaml:

```yaml
extensions:
  "portainer-mcp":
    type: stdio
    name: "portainer-mcp"
    enabled: true
    cmd: "uvx"
    args: ["portainer-mcp"]
    env_keys: []
    envs: {}
    timeout: 300
```

## Codex

Run in a terminal:

```sh
codex mcp add portainer-mcp -- uvx portainer-mcp
```

## Agenvoy

Merge into ~/.config/agenvoy/mcp.json:

```json
{
  "servers": {
    "portainer-mcp": {
      "command": "uvx",
      "args": ["portainer-mcp"]
    }
  }
}
```

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "portainer-mcp": {
      "command": "uvx",
      "args": ["portainer-mcp"]
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.