slaktforskning-mcp-dev

What problem does it solve?

It prevents broken or risky MCP dev-server changes by enforcing a strict “pass-through, never synthesize” contract for tool writes, while also documenting how the prod vs dev MCP servers and the UI bridge work.

Core Features & Use Cases

• Agent-safe tool behavior: Ensures MCP tools never infer missing fields (e.g., date types or genealogical details) and only persist values explicitly provided by the agent.
• Dev-server workflow guidance: Directs agents to use src/mcp/devServer.ts for agent-driven development, UI automation, and chart debugging against the live shared SQLite database.
• UI bridge debugging playbook: Explains how dev UI tools operate via the HTTP control plane (port 19241), how to validate interactive changes without unreliable drag verification, and how to recover when the MCP bridge appears disconnected.
• Production vs development server clarity: Documents entry points, bundling/shipping approach for the production sidecar, and when to restart MCP vs restart the Tauri app.

Quick Start

Use this skill when you modify anything under src/mcp/, src/shared/channels/, src/renderer/tauri-window-api.ts, or src-tauri/src/ui_server.rs, and then validate the change with dev-server UI or chart tools through the MCP interface.