Centralize Trilium web and MCP on Vega #99

Closed
opened 2026-07-26 19:17:42 +01:00 by nimmo · 0 comments
Owner

Summary

Move the shared Trilium web/MCP endpoint to vega over Nebula and stop deploying the separate Lyra-hosted MCP path.

Scope

  • run services.trilium-server only on vega
  • keep the Trilium web listener Nebula-only
  • repoint Codex and OpenCode MCP clients to Vega's built-in Trilium MCP endpoint
  • authenticate those clients with the shared ETAPI token
  • document the new topology and the remaining manual AI / LLM toggle

Validation

  • nix flake check passes
  • branch is reviewed through the standard comment-based PR workflow
  • vega can be tested before merge as needed

Notes

The Trilium AI / LLM enable toggle appears to remain app state rather than a declarative server option, so enabling it in the UI after deployment is acceptable for this change.

## Summary Move the shared Trilium web/MCP endpoint to vega over Nebula and stop deploying the separate Lyra-hosted MCP path. ## Scope - run `services.trilium-server` only on vega - keep the Trilium web listener Nebula-only - repoint Codex and OpenCode MCP clients to Vega's built-in Trilium MCP endpoint - authenticate those clients with the shared ETAPI token - document the new topology and the remaining manual AI / LLM toggle ## Validation - [ ] `nix flake check` passes - [ ] branch is reviewed through the standard comment-based PR workflow - [ ] vega can be tested before merge as needed ## Notes The Trilium AI / LLM enable toggle appears to remain app state rather than a declarative server option, so enabling it in the UI after deployment is acceptable for this change.
nimmo closed this issue 2026-07-26 19:58:42 +01:00
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
nimmo/nixos-config#99
No description provided.