mcp-manager

Add or remove MCP servers to the local project scope.

4|2|Updated Jun 2, 2015

Search Tags:#automation #claude #CLI #mcp #config #server-management #project-local

Ready to run

npx skills add https://github.com/lttr/dotfiles --skill mcp-manager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcp-manager
Source: https://github.com/lttr/dotfiles/tree/main/claude/skills/mcp-manager
Command: npx skills add https://github.com/lttr/dotfiles --skill mcp-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires claude, npx, @upstash/context7-mcp, chrome-devtools-mcp, and includes scripts (resource) components.

What problem does it solve?

This Skill helps you add or remove MCP (Model Context Protocol) servers to the current project's local scope, without impacting any shared configuration or git.

Core Features & Use Cases

Local MCP management: Add or remove MCP servers for the active project only.
Guided usage: Redirects enabling/disabling and global configuration tasks to the CLI for full MCP management.
Common servers: context7, chrome-devtools, nuxt-ui can be added per project.

Quick Start

To add context7 to this project, run the provided script: ~/dotfiles/claude/skills/mcp-manager/scripts/mcp-add-context7.sh

To remove context7 from this project: claude mcp remove context7 --scope local

Frequently Asked Questions about mcp-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add MCP servers to my project locally?▼

Add MCP servers to your project's local scope using the provided scripts or the claude mcp CLI. For example, run the context7 script in your project directory, or use `claude mcp add context7 --scope local` to configure servers like context7, chrome-devtools, and nuxt-ui per-project without affecting global settings.

Can I manage MCP server configuration per project instead of globally?▼

Yes, this Skill handles per-project MCP configuration only. You can add or remove servers like context7 and chrome-devtools to the active project scope via local scripts or the claude mcp CLI with `--scope local`, keeping your configuration isolated from shared or global settings.

What MCP servers can I add to my project?▼

You can add context7, chrome-devtools, and nuxt-ui as project-local MCP servers. Each has a corresponding add script in the Skill, and all can be removed using `claude mcp remove [server-name] --scope local` to manage your project dependencies independently.

Does this handle enabling or disabling MCP servers?▼

This Skill focuses on adding and removing MCP servers at the project level. For enabling, disabling, or global MCP configuration tasks, use the dedicated claude mcp CLI commands, which provide full management capabilities beyond local project scope.

How do I remove an MCP server from my project?▼

Remove project-local MCP servers using the claude mcp CLI command `claude mcp remove [server-name] --scope local`, replacing `[server-name]` with context7, chrome-devtools, or nuxt-ui to cleanly revert your project configuration.

Why use project-local MCP configuration instead of global?▼

Project-local MCP configuration isolates server dependencies per project, prevents git conflicts, and avoids impacting shared environments. This approach keeps team workflows clean when different projects need different MCP servers like context7 or chrome-devtools.