Skill

activate-mcp

Mount an MCP server from the Claude Vault inventory in the current project by writing to .mcp.json and enabling it in .claude/settings.json. Use when the user wants to "activate", "mount", or "add" a vault MCP server to the current repo only.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin claude-vault

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Mount a vault MCP server in the current project.

SKILL.md

Similar Skills

cache-components

139.3k

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.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars0

Forks0

Last CommitApr 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

activate-mcp

Mount a vault MCP server in the current project.

Inputs

The user names an MCP server (e.g. "mount the greeninvoice MCP"). If ambiguous, run list-vault first or ask.

Steps

Resolve the inventory path per skills/_shared/inventory-path.md and read it. Find the MCP entry under mcpServers by name. If not found, tell the user and stop.

The inventory entry's config object is the canonical server spec (command, args, env, etc.).

Determine project root (cwd or nearest .git/.claude ancestor).

Read <project>/.mcp.json. If it doesn't exist, start with { "mcpServers": {} }.

Set mcpServers["<name>"] = <inventory.config>. If the server is already present with a different config, ask the user before overwriting.

Write .mcp.json back with 2-space indentation.

Read <project>/.claude/settings.json (create if missing). Ensure enabledMcpjsonServers exists as an array. Add <name> if not already present.

Write settings back.

Confirm: server name, files edited, and the reminder that Claude Code must be restarted for the MCP to mount. If the config references env vars (e.g. ${FOO}), list them so the user knows to ensure they're set.

Safety

Project-scoped only. Never touch user-global config.

Do not paste secrets inline. If the inventory uses ${VAR} placeholders, preserve them — do not resolve.

If the server requires auth and no env var is present, warn but still write the config.

Output style

One-line confirmation, list of edited files, and the env-vars-needed line if applicable. Single restart reminder.

activate-mcp

Mount a vault MCP server in the current project.

Inputs

The user names an MCP server (e.g. "mount the greeninvoice MCP"). If ambiguous, run list-vault first or ask.

Steps

Resolve the inventory path per skills/_shared/inventory-path.md and read it. Find the MCP entry under mcpServers by name. If not found, tell the user and stop.
The inventory entry's config object is the canonical server spec (command, args, env, etc.).
Determine project root (cwd or nearest .git/.claude ancestor).
Read <project>/.mcp.json. If it doesn't exist, start with { "mcpServers": {} }.
Set mcpServers["<name>"] = <inventory.config>. If the server is already present with a different config, ask the user before overwriting.
Write .mcp.json back with 2-space indentation.
Read <project>/.claude/settings.json (create if missing). Ensure enabledMcpjsonServers exists as an array. Add <name> if not already present.
Write settings back.
Confirm: server name, files edited, and the reminder that Claude Code must be restarted for the MCP to mount. If the config references env vars (e.g. ${FOO}), list them so the user knows to ensure they're set.

Safety

Project-scoped only. Never touch user-global config.
Do not paste secrets inline. If the inventory uses ${VAR} placeholders, preserve them — do not resolve.
If the server requires auth and no env var is present, warn but still write the config.

Output style

One-line confirmation, list of edited files, and the env-vars-needed line if applicable. Single restart reminder.