MCP Manager
Manages project-specific Model Context Protocol (MCP) servers by adding or removing them at the local scope.
The source repository doesn't declare a license. Check its terms before reusing the code.
Key features
- Integration with documentation servers like context7 and Nuxt UI
- Project-scoped removal of MCP servers to maintain environment isolation
- Smart redirection to native CLI for global configuration tasks
- Localized MCP server addition using pre-configured scripts
- Support for browser automation via Chrome DevTools protocol
Use cases
- Equipping a project with up-to-date library documentation and API references
- Setting up browser automation and debugging tools for a specific web development task
- Cleaning up local project configurations by removing unused MCP servers
FAQ
How does this differ from the native 'claude mcp' command?
This skill is optimized for project-specific isolation using pre-configured scripts. While it handles local additions and removals, you should use the native 'claude mcp' CLI for global configurations, listing active servers, or enabling and disabling servers.
Which MCP servers can I manage with this skill?
This skill currently supports project-scoped management for context7 (library documentation), chrome-devtools (browser automation), and nuxt-ui (UI component documentation). It ensures these tools are available exactly where you need them.
Can this skill help me with browser automation?
Yes. By using this skill to add the chrome-devtools MCP server to your project, you enable Claude to interact with the Chrome DevTools Protocol for browser-based debugging and automation tasks.
What does the MCP Manager skill do?
The MCP Manager skill allows Claude to manage Model Context Protocol (MCP) servers at a local project level. It provides specialized scripts to add or remove servers like context7 and chrome-devtools to your current working directory without affecting your global configuration.
Why should I use local scope for MCP servers?
Using local scope maintains environment isolation. It prevents your global development environment from being cluttered with project-specific documentation servers or automation tools that aren't relevant to other codebases.