mcp-management

Configure MCP server access in VS Code via mcp.json files.

7|2|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/asafelobotomy/iCloud-Drive-Downloader --skill mcp-management-asafelobotomy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-management
Source: https://github.com/asafelobotomy/iCloud-Drive-Downloader/tree/main/.github/skills/mcp-management
Command: npx skills add https://github.com/asafelobotomy/iCloud-Drive-Downloader --skill mcp-management-asafelobotomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you set up and maintain Model Context Protocol (MCP) servers in VS Code so your agent can access external tools, resources, and prompts reliably.

Core Features & Use Cases

  • Server configuration guidance: Decide where to place MCP server configs in .vscode/mcp.json (workspace) or profile-level mcp.json (user), and understand how settings.json can override via the mcp key.
  • Server selection & discovery: Identify appropriate built-in, external-access, and documentation-focused servers, plus how to discover and install others from the MCP gallery/marketplace/registries.
  • Operational safety practices: Apply credential-handling guidance, sandboxing considerations, and avoid deprecated/archived server configurations.
  • Common workflows: Enable auto-start behavior, manage “tiers” (always-on vs credentials vs documentation), and handle subagent proposals for MCP changes.

Quick Start

Ask the AI to generate a recommended .vscode/mcp.json that enables the always-on filesystem and git servers and adds a credentials-based server (github or fetch) appropriate for your workflow.

Frequently Asked Questions about mcp-management

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

FAQPage Schema
How do I configure MCP servers in VS Code for external tool access?

To configure MCP servers in VS Code, you place server definitions in `.vscode/mcp.json` for workspace-scoped access or profile-level `mcp.json` for user-scoped access. You can also use `settings.json` to override configurations via the `mcp` key.

What transport options are available when setting up MCP server configuration?

MCP server configuration supports `npx`, `uvx`, and HTTP remote transport selections. Choosing the correct transport ensures your agent can reliably connect to external tools, resources, and prompts within your development environment.

How do I securely handle credentials when integrating MCP servers?

Secure MCP credential handling requires avoiding hardcoded secrets in your configuration files. You should apply operational safety practices like sandboxing considerations and tier-based enabling to manage access for credentials-based servers like GitHub or fetch.

Can I enable auto-start behavior for MCP servers in a workspace setup?

Yes, you can enable auto-start behavior for MCP servers in a workspace setup. This is managed by organizing servers into tiers such as always-on for filesystem and git, or credentials-based, ensuring reliable resource access.

What is the difference between workspace-scoped and user-scoped MCP management?

Workspace-scoped MCP management places configurations in `.vscode/mcp.json` for project-specific access, while user-scoped management uses profile-level `mcp.json` for global access. The `settings.json` file can override both via the `mcp` key.

How do I discover and install MCP servers from the marketplace?

You can discover and install MCP servers from the MCP gallery, marketplace, or registries. This allows you to identify appropriate built-in, external-access, and documentation-focused servers to integrate with your agent.