Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Server Templateshow me the available tools"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server Template
A production-ready template for building Model Context Protocol (MCP) servers with TypeScript.
Features
MCP SDK 1.24.3 - Latest SDK with 2025-11-25 spec support
Dual Transport - Stdio (Claude Desktop) and HTTP (cloud deployment)
OAuth 2.1 Foundations - Protected resource metadata, bearer token structure
SQLite Caching - TTL-based caching with sql.js (WebAssembly)
Observability - Sentry error tracking + OpenTelemetry tracing
Security - PII sanitization, rate limiting, DNS rebinding protection
Type Safety - Strict TypeScript with Zod validation
Quick Start
Project Structure
Configuration
Environment variables (prefix with MCP_SERVER_):
Variable | Default | Description |
|
| Server name |
|
| Server version |
|
| Log level: debug, info, warning, error |
|
| SQLite database path |
|
| Enable/disable caching |
|
| Default cache TTL (seconds) |
|
| Request timeout (ms) |
|
| Transport: |
|
| HTTP port (when transport=http) |
|
| HTTP host (when transport=http) |
| - | Sentry DSN for error tracking |
|
| Enable OpenTelemetry tracing |
| - | OTLP collector endpoint |
|
| Debug mode (skips auth) |
Creating Tools
Tools are registered with the ToolRegistry using Zod schemas:
Transport Modes
Stdio (Default)
For Claude Desktop and local integrations:
Add to Claude Desktop config:
HTTP
For cloud deployment:
Endpoints:
GET /health- Health checkGET /.well-known/mcp- MCP server metadataGET /.well-known/oauth-protected-resource- OAuth metadata (RFC 9728)GET /mcp- SSE stream for server eventsPOST /mcp- JSON-RPC requestsDELETE /mcp- Close session
Security Features
PII Sanitization
Automatically detects and masks sensitive data:
Rate Limiting
Per-source rate limiting with exponential backoff:
DNS Rebinding Protection
HTTP transport validates Host headers against allowlist.
Observability
Sentry
Error tracking with PII filtering:
OpenTelemetry
Distributed tracing:
Use tracing utilities:
Development
MCP 2025-11-25 Spec Compliance
Feature | Status |
Tools | ✅ Implemented |
Resources | 📝 Scaffolded |
Prompts | 📝 Scaffolded |
Streamable HTTP | ✅ Implemented |
.well-known/mcp | ✅ Implemented |
OAuth 2.1 Foundations | ✅ Scaffolded |
Tasks | ❌ Not yet |
Elicitation | ❌ Not yet |
OAuth 2.1 Implementation
The template includes foundations for OAuth 2.1 per the MCP spec:
Protected Resource Metadata (RFC 9728) at
/.well-known/oauth-protected-resourceBearer token middleware structure (implement JWT validation)
WWW-Authenticate headers with resource_metadata reference
Scope checking structure for tool authorization
To complete OAuth integration:
Choose an authorization server (Auth0, Logto, etc.)
Implement JWT validation in
bearerAuthMiddlewareAdd JWKS fetching and caching
Configure scopes per tool
See MCP Authorization Spec for details.
License
MIT