mcp -starter

This MCP server provides a production-ready Model Context Protocol (MCP) endpoint with HTTP/SSE transport, along with integrated OAuth support, IP and email filtering, and structured logging. It is built with TypeScript and designed to run via Docker, making deployment straightforward in various environments. You can extend its functionality in the src/mcp/primitives directory, where you’ll find tools, resources, and prompts to customize your MCP workflows. After starting, the server exposes an HTTP interface at the configured URL (default http://localhost:3000) and can be used with the included MCP tools for resource management, prompt handling, and utilities.

Prerequisites:

• Docker installed on your machine
• Git and a Git client
• Optional: Docker Compose if you prefer orchestrating multiple services
• Basic familiarity with command line

Installation steps:

1. Clone the repository git clone https://github.com/anatoly314/mcp-server-starter.git
2. Navigate to the project directory cd mcp-server-starter
3. Build the Docker image (as described in the README) docker build -t mcp-server .
4. Prepare environment configuration
   • Create .env.http by copying the example and customizing values cp .env.http.example .env.http Edit .env.http to set PUBLIC_URL, OAuth settings, and security filters as needed
5. Run the server using Docker docker run -p 3000:3000 --env-file .env.http mcp-server
6. Verify the server is running Open http://localhost:3000 in your browser

Alternative (local development):

• Install dependencies with pnpm if you want to run a dev server locally pnpm install
• Start the HTTP dev server pnpm run dev:http

Tips and notes:

• The server supports OAuth via Clerk (optional); enable by setting AUTH_ENABLED=true and providing OAUTH_ISSUER_URL and related docs links in .env.http
• Use FILTER_BY_IP and ALLOWED_EMAILS to implement basic access control; supply comma-separated values
• Docker deployment uses an env file (.env.http) to configure runtime variables; ensure this file is secured and not committed to source control
• The extensible architecture under src/mcp/primitives contains tools, resources, and prompts you can customize for your MCP workflows
• If you encounter port conflicts, adjust the Docker run port mapping (e.g., -p 8080:3000) and update PUBLIC_URL accordingly
• For production, consider enabling TLS termination in your reverse proxy and using a secure environment for secrets