Stats
Actions
Tags
From mcp-manager
List all configured MCP servers with their enabled/disabled status, grouped by scope (project vs global). Use this to see what MCP servers are available, check which servers are enabled or disabled, manage MCP configuration, or audit MCP server setup.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mcp-manager:listThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Show all configured MCP servers grouped by scope, with their enabled/disabled status and connection type.
Show all configured MCP servers grouped by scope, with their enabled/disabled status and connection type.
scope: "global"): stored in ~/.claude.json — NOT ~/.cursor/mcp.jsonscope: "<workspace-path>"): stored in .mcp.json at the project rootCheck if the MCP Manager server is running:
curl -s --max-time 2 http://localhost:4111/api/health
If the server is NOT running, start it:
cd "$CLAUDE_PLUGIN_ROOT" && nohup node server/index.js > ~/.mcp-manager.log 2>&1 &
sleep 2
Fetch the full MCP configuration:
curl -s http://localhost:4111/api/config
Parse and display the response in a readable format:
"global" means ~/.claude.json, any path means .mcp.json in that directoryscope field for project servers is the full workspace path (e.g., /Users/me/project), not the string "project"If the user wants to toggle or modify a server, suggest using /mcp-manager:toggle, /mcp-manager:add, or /mcp-manager:delete.
npx claudepluginhub sanjibdevnathlabs/claude-plugins --plugin mcp-managerChecks and configures MCP servers in .mcp.json for project integration. Use for setup, status checks, adding core servers like context7 and sequential-thinking, or specific ones like playwright.
Manages Model Context Protocol (MCP) servers for Claude Code projects: installs/configures .mcp.json, OAuth remotes, runtime enable/disable, troubleshooting connections.
List tools and invoke calls on MCP servers using fastmcp CLI. Handles HTTP/Python files/configs/stdio targets, schemas, JSON output, auth, and discovery for workflows.