mcpsq

MCPSQ is a lightweight MCP server that helps you discover and manage MCP servers from a single place. Once running, it exposes an MCP endpoint at /mcp (via SSE) and a message handling endpoint at /messages, enabling integration with chat tools and automation platforms. With Cursor integration, MCPSQ can be configured as an MCP source so Cursor can search for, add, list, and remove MCP servers directly from within your chat workspace. The included tools allow you to find MCP servers relevant to your query, add an MCP server to Cursor, view all configured MCP servers, and remove any server when it’s no longer needed.

You’ll typically start MCPSQ using a package runner (as described in installation). After configuration, you can query Cursor or any MCP-enabled client to discover MCPSQ-managed MCP servers and use their endpoints for task orchestration, monitoring, or coordination across your Minecraft server ecosystem.

Prerequisites:

• Node.js v18 or higher
• npm (comes with Node.js)
• Internet access to install dependencies

Installation steps:

1. Clone the repository:

git clone https://github.com/xinbenlv/mcpsq.git
cd mcpsq

2. Install dependencies:

npm install

3. Build the project (TypeScript to JavaScript) if you plan to run the built output:

npm run build

4. Run the server in production mode:

npm start

5. (Optional) Run in development mode with auto-reload:

npm run dev

The server will listen on port 3000 by default (adjust via environment variables if needed) and expose:

• GET /mcp (SSE stream for MCP server discovery)
• POST /messages (handle incoming messages)

If you’re deploying to a hosting provider or container, ensure the environment supports Node.js 18+ and that port 3000 is open (or configure PORT accordingly).

Environment variables and configuration tips:

• PORT: Port for the MCP endpoint (default 3000)
• NODE_ENV: Set to production or development as needed
• Cursor integration: configure Cursor MCP with the URL to your MCPSQ /mcp endpoint
• If tools aren’t appearing in Cursor, verify MCP config JSON syntax and that MCPSQ is reachable from Cursor’s host

Common issues:

• Server not starting: confirm port availability and Node.js version
• Cursor cannot connect: double-check the MCP JSON config path and ensure the /mcp URL is correct
• Build/type errors: run npm run typecheck and npm run build to surface issues early