Preset file format

Preset files live in the config directory:

  • ~/.config/broxy/preset_<id>.json

The file name and the id field must match.

Minimal example

{
  "id": "developer",
  "name": "Developer tools",
  "tools": []
}

Full example

{
  "id": "research",
  "name": "Research",
  "tools": [
    { "serverId": "docs", "toolName": "search", "enabled": true },
    { "serverId": "github", "toolName": "repo_info", "enabled": true }
  ],
  "prompts": [
    { "serverId": "docs", "promptName": "summarize", "enabled": true }
  ],
  "resources": [
    { "serverId": "docs", "resourceKey": "docs://page/{id}", "enabled": true }
  ]
}

Prompts/resources: null vs empty

  • If prompts or resources is **omitted**, Broxy includes all items from in-scope servers.
  • If prompts or resources is **present but empty**, Broxy includes none.

Built-in presets

Broxy reserves two preset ids that are not backed by files:

  • __empty__: exposes no capabilities.
  • __all_enabled__: exposes all tools/prompts/resources from enabled servers.

Renaming a preset

  • Create a new file with the new id.
  • Update the id field inside the JSON.
  • Remove the old file.

The desktop UI handles this automatically when you rename a preset.

No documentation matches your search.