Configuration Schema

Relevant source files

The following files were used as context for generating this wiki page:

• README.md
• package.json
• src/index.ts
• tsconfig.json
• src/types.ts

The Configuration Schema for mcpmcp-server defines the structure and parameters required to integrate the Model Context Protocol (MCP) gateway with various AI clients. It serves as the primary interface for users to bridge local MCP clients (such as Claude Desktop) with the remote mcpmcp.io discovery and integration service.

The schema is primarily expressed through JSON objects expected by client-side configuration files. These configurations instruct the host application on how to spawn the mcp-remote proxy and point it toward the centralized mcpmcp endpoint.

Sources: README.md:1-20, package.json:1-15

Client Integration Configuration

Integrating with an MCP client requires defining a specific entry within the mcpServers object of the client's configuration file. This entry utilizes npx to execute the latest version of the mcp-remote package, passing the remote gateway URL as a positional argument.

Configuration Object Structure

The configuration follows a standard key-value structure where the key identifies the server and the value contains the execution details.

Field	Type	Description
command	string	The command to execute (typically npx).
args	string[]	Arguments including package flags and the remote URL.

Sources: README.md:10-17

Implementation Flow

The following diagram illustrates how the configuration schema is utilized by an AI client to establish a connection with the remote server.

The diagram shows the sequence from the local client reading the JSON configuration to the establishment of the remote connection.
Sources: README.md:7-17

Schema Specification

The core of the configuration is the JSON block defined within the user's local setup. It relies on the availability of Node.js environments to process the npx command.

{
  "mcpServers": {
    "mcpmcp": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://mcpmcp.io/mcp"]
    }
  }
}

Sources: README.md:11-17

Argument Breakdown

• -y: Forces npx to skip the confirmation prompt for installing the mcp-remote package.
• mcp-remote@latest: Ensures the client always uses the most recent bridge logic for the protocol.
• https://mcpmcp.io/mcp: The target endpoint for the remote MCP server registry.

Sources: README.md:14, package.json:1-5

Technical Environment

The project is built using TypeScript, as evidenced by the project structure and build configuration. This ensures that the underlying logic for handling MCP requests follows a strictly typed schema internally.

Build and Dependency Structure

Setting	Value	Description
Language	TypeScript	Primary source language.
Target	ES2022	The JavaScript version targeted by the compiler.
Module	NodeNext	Module resolution strategy for Node.js compatibility.

Sources: tsconfig.json:1-20, package.json:10-25

The class diagram represents the logical relationship between the local execution configuration and the remote server registry.
Sources: README.md:10-20, src/index.ts

Conclusion

The configuration schema for mcpmcp-server is designed for simplicity, leveraging the mcp-remote proxy to minimize local setup requirements. By using a standard JSON format, it ensures compatibility with major MCP-compliant clients like Claude Desktop while providing a direct pipeline to remote AI tool discovery.