Overview
What is MCP Server Template for Cursor IDE?
A simple template for creating custom tools for Cursor IDE using Model Context Protocol (MCP). It allows developers to create their own repository from this template, modify the tools, and connect them to Cursor IDE.
How to use MCP Server Template for Cursor IDE?
Deploy the server to Heroku with one click, or run locally via Docker or traditional Python setup. Configure Cursor IDE by adding a new MCP server with either an SSE endpoint (Heroku or Docker) or a stdio command (local setup).
Key features of MCP Server Template for Cursor IDE
- One-click deployment to Heroku
- Docker and Docker Compose support
- Supports both SSE and stdio transports
- Configurable via environment variables (port, host, debug)
- Installable via Smithery for Claude Desktop
- Comes with a testable server mood endpoint
Use cases of MCP Server Template for Cursor IDE
- Creating custom MCP tools for Cursor IDE
- Quickly prototyping and deploying server-side MCP tools
- Integrating custom APIs or local scripts with Cursor’s agent
- Learning how to build and connect MCP servers
FAQ from MCP Server Template for Cursor IDE
How do I connect the server to Cursor IDE?
Open Cursor Settings → Features, add a new MCP server, choose “sse” (for remote/Docker) or “stdio” (for local), and enter the appropriate URL or command path.
What transport protocols are supported?
The server supports two transports: SSE (Server-Sent Events) for remote or Docker setups, and stdio for local execution.
What environment variables can I configure?
Set MCP_SERVER_PORT (default 8000), MCP_SERVER_HOST (default 0.0.0.0), DEBUG (default false), and MCP_USER_AGENT in a .env file.
Can I deploy this to cloud platforms besides Heroku?
The README only provides a Heroku deployment button; other platforms are not mentioned.
Does the server require any external dependencies?
The server uses Python with uv package manager and can be installed with uv pip install -e ".[dev]". Docker is an alternative deployment method.
