dashy-mcp: Instructions file for Codex

AGENTS.md — dashy-mcp

MCP server exposing Dashy's REST API as tools so an LLM can read and edit dashboard config: sections, items (tiles), and top-level config keys. Uses FastMCP, uv for deps.

Exposed as 4 resource-scoped portmanteau tools (dashy_config, dashy_key, dashy_section, dashy_item), not one tool per endpoint — see "Portmanteau registration" below. A prior version registered all 14 endpoints individually; already small, but ported to the same pattern as the rest of the fleet for consistency.

Testing

• Offline suite: make test (or uv run pytest)
• Live integration (needs DASHY_URL/DASHY_TOKEN): make test-integration

Release workflow

Always use the make bump-* targets to bump the version (uv version --bump patch|minor|major), which updates pyproject.toml and uv.lock together. Do NOT edit the version by hand.

• Bump: make bump-patch (or bump-minor / bump-major)
• Commit message is just the version, e.g. 0.1.2 — nothing else.
• Tag it v<version> (e.g. v0.1.2).
• Push main and the tag:

  git push origin main
  git push origin v<version>
  

• Then sync the project copy:

  cd /home/savagecore/Documents/christopfarr/mcp/dashy-mcp
  git fetch origin && git reset --hard origin/main
  

• Deploy to the Proxmox host (root SSH key): pull the repo and re-sync the venv:

  ssh [email protected] -- 'cd /root/dashy-mcp && git fetch origin && git reset --hard origin/main && uv sync'
  

  Correction (verified against the live host, this AGENTS.md previously had it backwards): the opencode config (/root/.config/opencode/opencode.jsonc) runs /root/dashy-mcp/.venv/bin/dashy-mcp — i.e. the repo checkout's own venv, not a uv tool install. There is no /root/.local/bin/dashy-mcp symlink and no uv-tool install for this server. uv tool install --force . would create one but would NOT change what opencode actually executes, so it's a no-op for deployment purposes here — use uv sync in the checkout instead, as above.