From claude-vault
Remove an MCP server from the current project's .mcp.json and disable it in .claude/settings.json. Symmetric counterpart to activate-mcp.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin claude-vaultThis skill uses the workspace's default tool permissions.
Unmount an MCP server from the current project. Removes it from `.mcp.json` and from `enabledMcpjsonServers` in `.claude/settings.json`.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Unmount an MCP server from the current project. Removes it from .mcp.json and from enabledMcpjsonServers in .claude/settings.json.
The user names an MCP server. If ambiguous, run list-active.
.git/.claude ancestor).<project>/.mcp.json. If missing or the server isn't present, say so and stop.mcpServers["<name>"]. Write the file back with 2-space indentation. If mcpServers becomes empty, leave it as {}.<project>/.claude/settings.json. If enabledMcpjsonServers contains the name, remove it. Write back..mcp.json file even if it ends up empty — leave the empty { "mcpServers": {} } shell.settings.local.json overrides separately.One-line confirmation. Restart reminder.