Template to quickly set up your own MCP server
{
"mcpServers": {
"my-mcp-sse": {
"url": "http://localhost:3001/sse"
},
"my-mcp-stdio": {
"env": {
"NODE_ENV": "development"
},
"args": [
"start"
],
"command": "npm"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Template to quickly set up your own MCP server
Is it safe?
No known CVEs for npx.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 133 days ago. 72 stars. 142,730 weekly downloads.
Will it work with my client?
Transport: stdio, sse, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npx' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Template Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A CLI tool to quickly get started building your very own MCP (Model Context Protocol) server using FastMCP
# with npx
npx @mcpdotdirect/create-mcp-server
# Or with npm
npm init @mcpdotdirect/mcp-server
The template includes:
After creating your project:
Install dependencies using your preferred package manager:
# Using npm
npm install
# Using yarn
yarn
# Using pnpm
pnpm install
# Using bun
bun install
Start the server:
# Start the stdio server
npm start
# Or start the HTTP server
npm run start:http
For development with auto-reload:
# Development mode with stdio
npm run dev
# Development mode with HTTP
npm run dev:http
Note: The default scripts in package.json use Bun as the runtime (e.g.,
bun run src/index.ts). If you prefer to use a different package manager or runtime, you can modify these scripts in your package.json file to use Node.js or another runtime of your choice.
The MCP server supports two transport methods:
stdio Transport (Command Line Mode):
stdoutSSE Transport (HTTP Web Mode):
Start the server in stdio mode for CLI tools:
# Start the stdio server
npm start
# or with other package managers
yarn start
pnpm start
bun start
# Start the server in development mode with auto-reload
npm run dev
# or
yarn dev
pnpm dev
bun dev
Start the server in HTTP mode for web applications:
# Start the HTTP server
npm run start:http
# or
yarn start:http
pnpm start:http
bun start:http
# Start the HTTP server in development mode with auto-reload
npm run dev:http
# or
yarn dev:http
pnpm dev:http
bun dev:http
By default, the HTTP server runs on port 3001. You can change this by setting the PORT environment variable:
# Start the HTTP server on a custom port
PORT=8080 npm run start:http
To connect to your MCP server from Cursor:
my-mcp-server (or any name you prefer)commandnpm starturlhttp://localhost:3001/sseFor a more portable configuration, create an .cursor/mcp.json file in your project's root directory:
{
"mcpServers": {
"my-mcp-stdio": {
"command": "npm",
"args": [
"start"
... [View full README on GitHub](https://github.com/mcpdotdirect/template-mcp-server#readme)