forge-mcps

You can manage Claude MCPs across user, project, and local scopes using a centralized CLI. This allows you to list, add, and remove configurations while ensuring environment checks prevent misconfigurations.

Removing MCPs safely requires using a CLI that enforces safe removal prompts when a configuration exists in multiple scopes. This prevents accidental deletion and ensures your environment remains stable.

Yes, you can add known MCPs or custom bundles to your local registry. The CLI workflow supports preflight environment checks to ensure configurations are valid before they are added to the user, project, or local scope.

To list MCPs from local catalogs, you can use the centralized CLI workflow. This provides a clear view of configuration availability and helps you understand what is currently registered in your environment.

Adding an MCP fails during preflight checks when the CLI detects environment inconsistencies that could lead to misconfigurations. Enforcing these checks ensures only valid and compatible MCPs are added to your active scope.

Using a CLI to configure Claude MCPs is recommended because it enforces proper interactions and safe removal prompts. Directly editing files bypasses environment checks and risks creating misconfigurations across multiple scopes.