MCP.so
Sign In
Servers

MCP Server Configuration

@rvjwhite

Fixed configuration for Model Context Protocol server with proper dependencies

Overview

What is MCP Server Configuration?

MCP Server Configuration is a fixed configuration repository for the Model Context Protocol (MCP) server that resolves the ERR_MODULE_NOT_FOUND error related to the zod-to-json-schema dependency. It is intended for developers using the @modelcontextprotocol/server-filesystem package who encounter that import issue.

How to use MCP Server Configuration?

Clone the repository, run npm install to install dependencies, then start the server with npm start. An alternative quick fix involves creating a new Node.js project, installing @modelcontextprotocol/server-filesystem, zod, and zod-to-json-schema explicitly, adding "type": "module" to package.json, and creating a simple index.js that imports and creates the server.

Key features of MCP Server Configuration

  • Resolves ERR_MODULE_NOT_FOUND for zod-to-json-schema
  • Provides a ready-to-use fixed configuration
  • Includes proper dependency declarations
  • Offers an alternative quick-fix approach

Use cases of MCP Server Configuration

  • Developers unable to run the MCP filesystem server due to missing module error
  • Those who prefer a pre-configured repository over manual fixes
  • Users wanting to quickly test or deploy the MCP filesystem server with correct dependencies

FAQ from MCP Server Configuration

What error does this configuration fix?

It fixes the ERR_MODULE_NOT_FOUND error that occurs when the zod-to-json-schema module cannot be resolved, preventing the MCP server from starting.

What dependencies are required?

The repository requires @modelcontextprotocol/server-filesystem, zod, and zod-to-json-schema as explicit dependencies, plus "type": "module" in package.json.

How do I run the server after installing?

After following the installation steps, run npm start to start the MCP server.

Can I fix the error without this repository?

Yes. The README describes an alternative manual fix: create a new Node.js project, install the three required packages, enable ES modules, and create a minimal entry file.

More from Developer Tools