Install Victoriametrics in Goose
What you need first
- Goose, installed.
- Docker, which
gives the
dockercommand the server starts with. - Your own values for
YOUR_VM_INSTANCE_ENTRYPOINT,YOUR_VM_INSTANCE_TYPE,YOUR_VM_INSTANCE_BEARER_TOKEN.
Steps
- Open
~/.config/goose/config.yaml. On Windows it is%APPDATA%\Block\goose\config\config.yaml. - Add this entry. If the file already has
extensions, add only the entry inside it.
extensions:
"mcp-victoriametrics":
type: stdio
name: "mcp-victoriametrics"
enabled: true
cmd: "docker"
args: ["run", "-i", "--rm", "-e", "VM_INSTANCE_ENTRYPOINT", "-e", "VM_INSTANCE_TYPE", "-e", "VM_INSTANCE_BEARER_TOKEN", "ghcr.io/victoriametrics/mcp-victoriametrics:1.120.1"]
env_keys: []
envs: { "VM_INSTANCE_ENTRYPOINT": "YOUR_VM_INSTANCE_ENTRYPOINT", "VM_INSTANCE_TYPE": "YOUR_VM_INSTANCE_TYPE", "VM_INSTANCE_BEARER_TOKEN": "YOUR_VM_INSTANCE_BEARER_TOKEN" }
timeout: 300 - Replace
YOUR_VM_INSTANCE_ENTRYPOINT,YOUR_VM_INSTANCE_TYPE,YOUR_VM_INSTANCE_BEARER_TOKENwith your own values. - Save the file and start a new Goose session.
Check it worked
Ask Goose: List the tools of mcp-victoriametrics.
If it does not start
- Cannot connect to the Docker daemon
- Docker is not running. Start it, then restart Goose.
- The server starts, but its tools fail
- A
YOUR_…placeholder is still in the config, or its value is wrong. - Nothing changes after a restart
- The file is not valid YAML any more. Check that the entry is indented like the lines around it.