MCP Configuration

Configure MCP servers across Gemini, Qwen, Claude Code, and VS Code.

3|1|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/vanman2024/dev-lifecycle-marketplace --skill mcp-configuration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Configuration
Source: https://github.com/vanman2024/dev-lifecycle-marketplace/tree/main/.archive/old-numbered-plugins/01-core/skills/mcp-configuration
Command: npx skills add https://github.com/vanman2024/dev-lifecycle-marketplace --skill mcp-configuration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

Setting up and managing Micro-Agent Communication Protocol (MCP) server configurations, especially across different environments and tools, can be complex and error-prone. This skill simplifies the entire configuration lifecycle.

Core Features & Use Cases

  • Centralized Registry Management: Provides scripts to initialize, add, list, and scan MCP servers in a universal registry (~/.claude/mcp-registry/servers.json), ensuring consistent access.
  • Multi-Tool Transformation: Transforms MCP server definitions from the central registry into formats compatible with various tools like Claude Code (.mcp.json), Codex (config.toml), Gemini, and VS Code (.vscode/mcp.json).
  • Environment & Security Setup: Helps configure environment variables, manage API keys securely in .env files, and validate configuration for correctness.
  • Permission Management: Includes scripts to update and validate slash command permissions in .claude/settings.local.json, ensuring proper access control.
  • Use Case: A developer needs to integrate a new FastMCP server with their local Claude Code environment and also make it available for Codex. This skill can initialize a global MCP registry, add the server, and then transform its configuration into the specific .mcp.json and config.toml formats required by each tool.

Quick Start

Initialize the global MCP server registry, then scan the '/Projects/Mcp-Servers' directory for existing MCP servers and add them to the registry.

Frequently Asked Questions about MCP Configuration

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

FAQPage Schema
How do I configure MCP servers across multiple tools like Claude Code and VS Code?

MCP Configuration transforms server definitions from a central registry into tool-specific formats. Initialize a global registry, add your servers, then generate .mcp.json for Claude Code, .vscode/mcp.json for VS Code, and config.toml for other tools automatically.

What's the best way to manage MCP server configurations and environment variables securely?

Store server definitions in a universal registry at ~/.claude/mcp-registry/servers.json and manage API keys in .env files. The skill validates configurations and handles environment variable substitution across all supported tools.

Can I scan existing MCP servers and add them to a central registry automatically?

Yes. MCP Configuration includes scripts to scan directories for existing MCP server definitions, validate them, and add them to the central registry in bulk, eliminating manual configuration entry.

How do I set up a FastMCP server to work with Claude Code and other development tools?

Add the FastMCP server to the central registry using the skill's add command, then export its configuration to the required format for each tool. The skill handles multi-tool transformation automatically.

Does MCP Configuration support both stdio and HTTP-based server definitions?

Yes. The skill configures local stdio and HTTP-based MCP server definitions, supports registry management, validation, and cross-tool transformation for both connection types.

What happens if my MCP server configuration has errors or missing fields?

MCP Configuration includes validation scripts that check configurations for correctness before deployment. Invalid entries are flagged, allowing you to fix issues before they affect tool integration.