mcp-montano

The MCP Montano server is a TypeScript-based MCP server designed to integrate with the Cursor development environment. It compiles from TypeScript to JavaScript and exposes an MCP-compatible server that can be run in development or production. You can run it in development mode to enable faster feedback during coding, or build and start a production-ready version for deployment. The project includes a ready-made example for adding the MCP to Cursor, allowing you to load and manage the Montano MCP server directly from your Cursor workspace. To use, first install dependencies, then run the appropriate npm script to start in development or build and run in production, and finally configure Cursor with the provided MCP snippet to load the server.

Prerequisites:\n- Node.js v18 or higher\n- npm (comes with Node.js)\n- Cursor IDE (recommended)\n\nInstallation steps:\n1) Clone the repository:\nbash\ngit clone git@github.com:lucasmontano/mcp-montano-server.git\ncd mcp-montano-server\n\n2) Install dependencies:\nbash\nnpm install\n\n3) Run in development mode:\nbash\nnpm run dev\n\n4) Build and run in production mode:\nbash\nnpm run build\nnpm start\n\n5) Optional: add MCP to Cursor using the example configuration:\njson\n{\n "mcpServers": { \n "montano-mcp-server": {\n "command": "node", \n "args": ["path/to/mcp-montano-server/build/index.js"]\n }\n }\n}\n

Tips:\n- Ensure you are using Node.js v18+ to match the prerequisites.\n- The development workflow uses npm run dev for rapid iteration; use npm run build followed by npm start for a production-like environment.\n- When configuring Cursor, point to the built index.js file inside the build directory as shown in the example.\n- If you encounter module resolution errors during development, try removing node_modules and running npm install again.\n- The repository structure typically includes src for TypeScript sources and build for compiled JavaScript; ensure you run the build step before starting in production.\nEnvironment variables: this server example does not define required environment variables by default, but you can extend the env object in mcp_config to pass any needed configuration (e.g., MCP version, port, or external service endpoints).