MCP Auto-Registration
Let Chau7 add its MCP entry to supported client configs.
Availability
Partially implemented in stable. Read the limits below before relying on this workflow.
Reviewed against stable v0.5.1. Rust candidate additions are labeled separately. Release status.
The pain this solves
- MCP client setup uses different config formats and locations.
- Automatically editing nonexistent or invalid client configuration would be misleading.
What ships with it
- Known registration targets include Claude Code, Cursor, Windsurf, Gemini CLI, and Codex.
- Client registration is skipped when required config paths are absent.
- JSON merge updates the Chau7 entry while retaining other server entries; malformed JSON is skipped.
Questions this answers
- How do I configure MCP servers in Claude Code?
- Why is MCP setup so tedious with manual JSON editing?
- How do I add a terminal MCP server to Cursor?
- Can MCP servers register themselves automatically?
- How to set up MCP in Windsurf without editing config files?
How it works
During MCP setup, Chau7 attempts registration for Claude Code, Cursor, Windsurf, Gemini CLI, and Codex. JSON clients receive a Chau7 entry merged into the existing MCP server map; Codex uses its supported TOML configuration path.
Registration is conditional. The implementation skips absent client directories or configuration files rather than creating every client’s setup from scratch. Claude hooks are also only added when the expected Claude settings file exists.
For JSON configurations, Chau7 updates its own named entry and preserves other server entries. Invalid existing JSON is skipped with a warning, and successful registration still depends on the client configuration being writable and the client recognizing the configured bridge.
Why it matters
MCP setup differs across clients. Chau7 can write its own entry into several known configurations, while avoiding the claim that every client is installed, configured, or connected automatically on every machine.
Frequently asked questions
Which clients are covered?
The stable registration code handles Claude Code, Cursor, Windsurf, Gemini CLI, and Codex.
Will Chau7 create config for a client that is not installed?
No. The JSON registration helpers skip a client when its configuration directory is absent; Codex registration also requires its config file.
Does it replace my other MCP server entries?
The JSON merge updates Chau7’s named entry in the existing server map and keeps other entries. Invalid JSON is skipped rather than rewritten.