halkyon-days/halkyon
Watch
1
0
Fork
You've already forked halkyon
 0
Code Issues Pull requests Projects Releases 37 Packages Wiki Activity Actions

chore: no Serverpod CLI analytics; the MCP bridge documented

Browse source 
The Serverpod CLI reports the commands run and the Serverpod features a project uses to PostHog, under a per-project ID, unless each call passes --no-analytics; there is no setting or environment variable. The VS Code task now passes it, and AGENTS.md asks for it on every call.

AGENTS.md prescribes the serverpod MCP tools, but nothing configured them. They come from serverpod mcp-server, a bridge to the running serverpod start; AGENTS.md now says how to set it up in .mcp.json, which stays git-ignored like every agent configuration.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>
This commit is contained in:
Tizian 「ティツィアーン」 2026-09-30 11:06:50 +02:00
commit 7bd94a5bb8
Signed by: raisondetredev
GPG key ID: 07F6FCF405488B64
2 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.vscode/tasks.json vendored
View file

@ -5,7 +5,7 @@
"label": "serverpod_start", "label": "serverpod_start",
"type": "shell", "type": "shell",
"command": "serverpod", "command": "serverpod",
"args": ["start"], "args": ["--no-analytics", "start"],
"options": { "options": {
"cwd": "${workspaceFolder}/halkyon_learn_server", "cwd": "${workspaceFolder}/halkyon_learn_server",
"env": { "env": {

4
AGENTS.md
View file

@ -23,6 +23,10 @@ NEVER edit generated code. The server's `lib/src/generated/` directory and the w
Migrations are a narrow exception: the `migration.sql` of a generated migration MAY be edited by hand when the generated SQL would lose data — to add a data transformation, or to reach a destructive change through non-destructive steps. Never touch the other files in the migration directory, and keep the schema the SQL ends up with identical to `definition.sql` — new databases are created from that file and never run `migration.sql`. Migrations are a narrow exception: the `migration.sql` of a generated migration MAY be edited by hand when the generated SQL would lose data — to add a data transformation, or to reach a destructive change through non-destructive steps. Never touch the other files in the migration directory, and keep the schema the SQL ends up with identical to `definition.sql` — new databases are created from that file and never run `migration.sql`.
The `serverpod` MCP tools come from `.mcp.json`: `serverpod mcp-server`, a bridge to the running `serverpod start`. They load when a session starts; if they are missing, the server wasn't running or the session predates `.mcp.json`. Like all agent configuration, `.mcp.json` is git-ignored; in a fresh clone, create it with a server `serverpod` running `serverpod` with the arguments `--no-analytics mcp-server --server-dir halkyon_learn_server`.
**Pass `--no-analytics` to every `serverpod` call** (before the command: `serverpod --no-analytics generate`). Otherwise the CLI reports the commands run and the Serverpod features the project uses to PostHog; there is no setting or environment variable to switch that off. The VS Code task and `.mcp.json` pass it already.
Only when the server cannot be started at all, fall back to the CLI in the server package: Only when the server cannot be started at all, fall back to the CLI in the server package:
- `serverpod generate` to regenerate the client and the generated server code. - `serverpod generate` to regenerate the client and the generated server code.