mcp

This MCP server provides a local environment for running Minecraft Control Protocol (MCP) workflows. It pairs with configuration tooling to manage MCP clients and coordinates interactions with local data sources. The repository indicates two primary deployment methods: using npx to run the server directly from the npm package, and deploying via Docker for containerized operation. The server is designed to work with the available packages in the monorepo, notably @gleanwork/configure-mcp-server for setting up MCP clients and @gleanwork/local-mcp-server for the runtime itself. With the npx approach, you don’t need a prior installation of the package; you execute the server command on demand. The Docker approach encapsulates the server in a container image for consistent environments and easier deployment in various hosts. The server will expose tools and interfaces that help configure MCP clients and run local MCP workflows.

Prerequisites:

• Node.js and npm (for npx-based setup)
• Docker (for Docker-based deployment)
• Internet access to fetch packages/images

Option A: Run with npx

1. Ensure Node.js and npm are installed on your system.

2. Run the MCP server directly from the npm package:

   npx -y @gleanwork/mcp-server

   This will download and execute the MCP server package without a global install.

Option B: Run with Docker

1. Ensure Docker is installed and running.

2. Pull and run the MCP server image:

   docker run -it gleanwork/mcp-server

   The container will start the MCP server inside the isolated environment. You may need to expose ports or mount configuration as needed for your setup.

Option C: Local monorepo usage (advanced)

1. Clone the repository and install workspace dependencies if you intend to build from source:

   git clone https://github.com/gleanwork/mcp-server.git cd mcp-server npm install

2. Build or run the individual packages as defined in their READMEs (e.g., packages/local-mcp-server). Follow the package-specific instructions for development usage.

Tips and common considerations:

• If you’re using npx, you can override the default port by setting MCP_PORT in your environment or pass appropriate runtime arguments as supported by the package.
• When running via Docker, you may need to map ports and provide configuration files via volumes to customize MCP clients and server behavior.
• The npm package name referenced by the project is @gleanwork/mcp-server; use this in npx commands.
• Refer to the dedicated READMEs for @gleanwork/configure-mcp-server and @gleanwork/local-mcp-server for deeper configuration options and examples.
• Ensure your environment has access to the necessary MCP client configurations and any external data sources required by your workflows.
• If you encounter permission or networking issues, verify Docker permissions and network accessibility, especially on corporate networks or restricted environments.