prometheus.codes

MCP integration

Augment Code

Run Prometheus alongside Augment Code's own context engine. Useful for comparison benchmarks or migrations.

Augment Code ships its own first-party context engine, but it also loads arbitrary MCP servers from augment_settings.json. Prometheus drops in cleanly next to (or instead of) the bundled engine.

1. Locate the settings file

  • macOS — ~/Library/Application Support/Augment/augment_settings.json
  • Windows — %APPDATA%\Augment\augment_settings.json

If the mcpServers key does not exist yet, add it.

2. Add the prometheus block

{
  "mcpServers": {
    "prometheus": {
      "command": "npx",
      "args": ["-y", "@prometheus/context-mcp@latest"],
      "env": {
        "PROMETHEUS_API_KEY": "${PROMETHEUS_API_KEY}",
        "PROMETHEUS_WORKSPACE_ID": "${PROMETHEUS_WORKSPACE_ID}"
      }
    }
  }
}

Augment expands shell-style ${VAR} references at load time, so the API key never lives in the JSON itself.

3. Reload the Augment plugin

In VS Code, run Augment: Reload MCP Servers from the command palette (Cmd-Shift-P). The Prometheus tools appear in the Augment chat panel under the External group.

Tool naming inside Augment

Augment prefixes external tools with the server name, so search_code shows up as prometheus.search_code. Mention this prefix in your agent system prompt if you instruct the model to call specific tools by name.

See MCP tools for the full surface and JSON schemas.