Roadmap §3.3. Claude Code reads per-project .mcp.json files, but BCC only surfaces the global ~/.claude.json — project-scope servers are invisible unless the user manually does Add config….
Design
Core: discover_project_configs(claude_json_path) -> list[Profile] — read the projects map keys (absolute project paths) from ~/.claude.json; for each path where <path>/.mcp.json exists, emit a Profile labeled Project: <basename> pointing at that .mcp.json. Fail-quiet on unreadable/malformed input. .mcp.json is a standalone top-level mcpServers file, i.e. already exactly BCC's format.
Wire into discover_profiles() after the Claude Code entry, de-duped against already-listed paths.
Acceptance: a project with .mcp.json listed in ~/.claude.json shows up in the Install dropdown automatically and is editable like any profile.
Roadmap §3.3. Claude Code reads per-project `.mcp.json` files, but BCC only surfaces the global `~/.claude.json` — project-scope servers are invisible unless the user manually does Add config….
**Design**
- Core: `discover_project_configs(claude_json_path) -> list[Profile]` — read the `projects` map keys (absolute project paths) from `~/.claude.json`; for each path where `<path>/.mcp.json` exists, emit a Profile labeled `Project: <basename>` pointing at that `.mcp.json`. Fail-quiet on unreadable/malformed input. `.mcp.json` is a standalone top-level `mcpServers` file, i.e. already exactly BCC's format.
- Wire into `discover_profiles()` after the Claude Code entry, de-duped against already-listed paths.
- Tests: projects map with/without `.mcp.json`, malformed `.claude.json`, missing `projects` key, path de-dup, label format.
**Acceptance**: a project with `.mcp.json` listed in `~/.claude.json` shows up in the Install dropdown automatically and is editable like any profile.
the_og
added the P1 label 2026-07-12 13:50:31 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Roadmap §3.3. Claude Code reads per-project
.mcp.jsonfiles, but BCC only surfaces the global~/.claude.json— project-scope servers are invisible unless the user manually does Add config….Design
discover_project_configs(claude_json_path) -> list[Profile]— read theprojectsmap keys (absolute project paths) from~/.claude.json; for each path where<path>/.mcp.jsonexists, emit a Profile labeledProject: <basename>pointing at that.mcp.json. Fail-quiet on unreadable/malformed input..mcp.jsonis a standalone top-levelmcpServersfile, i.e. already exactly BCC's format.discover_profiles()after the Claude Code entry, de-duped against already-listed paths..mcp.json, malformed.claude.json, missingprojectskey, path de-dup, label format.Acceptance: a project with
.mcp.jsonlisted in~/.claude.jsonshows up in the Install dropdown automatically and is editable like any profile.