create-mcp-json

Generate mcp.json client configurations from server.json for MCP servers.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/pulsemcp/agentic-engineering --skill create-mcp-json
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-mcp-json
Source: https://github.com/pulsemcp/agentic-engineering/tree/main/.claude/skills/create-mcp-json
Command: npx skills add https://github.com/pulsemcp/agentic-engineering --skill create-mcp-json

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of an MCP client configuration by generating a ready-to-use mcp.json from an existing server.json, ensuring consistent client-server wiring.

Core Features & Use Cases

  • Generates a complete mcp.json entry per server.json, enabling deterministic client config generation for MCP.
  • Enforces minimum version pinning, environment variable handling, and per-entry constraints from user context.
  • Supports both stdio-based and remote MCP server configurations via the server.json specification.

Quick Start

Provide a server.json in context and run the skill to generate an mcp.json configuration for connecting to your MCP server.

Frequently Asked Questions about create-mcp-json

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

FAQPage Schema
How do I generate an mcp.json client configuration from a server.json?

To generate an mcp.json client configuration, provide an existing server.json in context and run the skill to automatically produce ready-to-use mcp.json entries for deterministic client-server wiring.

What is the best way to configure MCP clients for multiple servers consistently?

Generating an mcp.json from server.json specifications ensures consistent client-server wiring by enforcing per-entry constraints and minimum version pinning across multiple MCP servers.

Does MCP config generation support both stdio and remote server connections?

MCP config generation supports both stdio-based and remote MCP server configurations, outputting valid mcp.json entries according to the MCP specification for each server type.

How are environment variables handled when creating an mcp.json file?

Environment variable handling is properly enforced during mcp.json creation, applying per-entry constraints from user context to ensure secure and valid client configurations.

Why does my MCP client configuration fail to connect across different CLI tools?

Inconsistent MCP client configurations often fail due to missing version pinning or invalid entries; generating a validated mcp.json ensures deterministic connections across CLI tools and editors.

Do I need a server.json file to create an mcp.json configuration?

Yes, a server.json file is required as the input specification to generate a complete and valid mcp.json entry for connecting your MCP client to the server.