how to register

[jepegit]

It seems like registering the server only supports claude code for now. Why? Can it also register in Cursor? VS-Code? Is it possible to provide more information in the docs on how to register?

[jepegit]

Fair question, and the honest answer to "why?" is: no reason. Claude Desktop was the client the design work happened to target, not a decision — nothing about the server is specific to it. Fixed in #2.

cellpy mcp install                     # Claude Desktop (default, unchanged)
cellpy mcp install --client cursor
cellpy mcp install --client vscode
cellpy mcp install --list-clients      # where each keeps its config

One thing worth knowing if you ever edit these by hand: VS Code names the key servers, not mcpServers. Writing the wrong one produces a file that parses, saves, and does nothing — no error anywhere, so it looks like the server is broken rather than unregistered. That is now per-client data with a test on each.

Claude Code is handled differently, on purpose. You mentioned Claude Code specifically — its servers live in ~/.claude.json, alongside your sign-in session and per-project trust decisions, or in a project-scoped .mcp.json whose location depends on which project you meant. It has claude mcp add, which handles scopes properly. Merging into a file that important to save one command seemed like a bad trade, so --client claude-code refuses and prints the command instead, filled in with your interpreter and roots:

claude mcp add cellpy --env CELLPY_MCP_ROOT=/path/to/cells -- python -m cellpy_mcp

On docs: the README now has a Registering with your client section with the full path table, the by-hand JSON block, and the one piece of advice that saves the most time — use the full path to the interpreter that has cellpy-mcp installed, never a bare python. A desktop client activates no virtualenv and inherits no shell PATH, and that is the most common reason a server shows up as failed.

Paths were checked against the current VS Code and Cursor documentation rather than from memory. cellpy mcp status now also reports which clients it can see cellpy registered with.

If you use another client that speaks stdio, tell me which and I will add it — the by-hand block works anywhere in the meantime.