P
phughesmcr/deno-mcp-template
Template for a local, remote or binary MCP server in Deno
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
# Deno MCP Server Template
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
The batteries-included starting point for building production MCP servers in TypeScript.
Clone, run setup, start building. Ships with STDIO + HTTP transports, security middleware, persistent state, sandboxed execution, CI/CD workflows, and every distribution format you need -- JSR package, native binary, DXT extension, or hosted on Deno Deploy.
## Why This Template?
You get a working MCP server in under 2 minutes. Not a toy -- a real server with rate limiting, CORS, session management, TLS support, and structured logging already wired up.
Deno gives you superpowers that other runtimes don't. Built-in KV database (no Postgres/Redis to set up), native cron scheduling, sandboxed code execution in microVMs, compile-to-binary, and first-class Deploy hosting. This template puts all of them to work.
Ship anywhere, any way. One codebase produces:
a local STDIO server for Cursor, Claude Desktop, or any MCP client
a remote HTTP server with Streamable HTTP transport
a JSR package anyone can deno run without cloning
a standalone native binary (no runtime needed)
a DXT extension for one-click Claude Desktop install
a Deno Deploy app for managed cloud hosting
AI-agent friendly codebase. Small files ( \
--app \
--source local \
--runtime-mode dynamic \
--entrypoint main.ts \
--build-timeout 5 \
--build-memory-limit 1024 \
--region us
# Deploy
deno deploy --prod
Set DENODEPLOYTOKEN, DENODEPLOYORG, and DENODEPLOYAPP in GitHub Actions secrets for automatic deploys. Remove .github/workflows/deploy.yml if not using Deploy.
## Production Checklist
[ ] Run deno task setup and verify all placeholder names are replaced
[ ] Remove or replace demo tools/resources/prompts you won't ship
[ ] Update static/.well-known/openapi.yaml and static/dxt-manifest.json
[ ] Configure MCPALLOWEDORIGINS and MCPALLOWEDHOSTS for your environments
[ ] Replace src/app/http/kvEventStore.ts with a production-grade event store (the included one is a demo)
[ ] Switch from deno run -A to explicit permissions for production
[ ] Review --allow-net scope for any outbound tool calls
[ ] Set environment variables in CI and hosting provider
[ ] Run deno task ci (format, lint, type-check, test)
## Configuration
| Variable | Flag | Default | Description |
| MCPNOHTTP | --no-http | false | Disable HTTP server |
| MCPNOSTDIO | --no-stdio | false | Disable STDIO transport |
| MCPHOSTNAME | -n | localhost | HTTP listen hostname |
| MCPPORT | -p | 3001 | HTTP listen port |
| MCPPUBLICBASEURL | --public-base-url | | Public http(s):// origin for browser links (URL elicitation); no trailing slash |
| MCPTLSCERT | --tls-cert | | PEM certificate path (requires --tls-key) |
| MCPTLSKEY | --tls-key | | PEM private key path (requires --tls-cert) |
| MCPHEADERS | -H | | Response headers (collection) |
| MCPJSONRESPONSE | --json-response | false | JSON-only responses (disable SSE) |
| MCPDNSREBINDING | --dnsRebinding | false | Enable transport-level Origin/Host checks (loopback binds already get Host validation) |
| MCPALLOWEDORIGINS | --origin | | Allowed CORS origins (collection) |
| MCPALLOWEDHOSTS | --host | | Allowed hostnames (collection) |
| MCPKVPATH | --kv-path | | Custom Deno KV database path |
Clone, run setup, start building. Ships with STDIO + HTTP transports, security middleware, persistent state, sandboxed execution, CI/CD workflows, and every distribution format you need -- JSR package, native binary, DXT extension, or hosted on Deno Deploy.
## Why This Template?
You get a working MCP server in under 2 minutes. Not a toy -- a real server with rate limiting, CORS, session management, TLS support, and structured logging already wired up.
Deno gives you superpowers that other runtimes don't. Built-in KV database (no Postgres/Redis to set up), native cron scheduling, sandboxed code execution in microVMs, compile-to-binary, and first-class Deploy hosting. This template puts all of them to work.
Ship anywhere, any way. One codebase produces:
a local STDIO server for Cursor, Claude Desktop, or any MCP client
a remote HTTP server with Streamable HTTP transport
a JSR package anyone can deno run without cloning
a standalone native binary (no runtime needed)
a DXT extension for one-click Claude Desktop install
a Deno Deploy app for managed cloud hosting
AI-agent friendly codebase. Small files ( \
--app \
--source local \
--runtime-mode dynamic \
--entrypoint main.ts \
--build-timeout 5 \
--build-memory-limit 1024 \
--region us
# Deploy
deno deploy --prod
Set DENODEPLOYTOKEN, DENODEPLOYORG, and DENODEPLOYAPP in GitHub Actions secrets for automatic deploys. Remove .github/workflows/deploy.yml if not using Deploy.
## Production Checklist
[ ] Run deno task setup and verify all placeholder names are replaced
[ ] Remove or replace demo tools/resources/prompts you won't ship
[ ] Update static/.well-known/openapi.yaml and static/dxt-manifest.json
[ ] Configure MCPALLOWEDORIGINS and MCPALLOWEDHOSTS for your environments
[ ] Replace src/app/http/kvEventStore.ts with a production-grade event store (the included one is a demo)
[ ] Switch from deno run -A to explicit permissions for production
[ ] Review --allow-net scope for any outbound tool calls
[ ] Set environment variables in CI and hosting provider
[ ] Run deno task ci (format, lint, type-check, test)
## Configuration
| Variable | Flag | Default | Description |
| MCPNOHTTP | --no-http | false | Disable HTTP server |
| MCPNOSTDIO | --no-stdio | false | Disable STDIO transport |
| MCPHOSTNAME | -n | localhost | HTTP listen hostname |
| MCPPORT | -p | 3001 | HTTP listen port |
| MCPPUBLICBASEURL | --public-base-url | | Public http(s):// origin for browser links (URL elicitation); no trailing slash |
| MCPTLSCERT | --tls-cert | | PEM certificate path (requires --tls-key) |
| MCPTLSKEY | --tls-key | | PEM private key path (requires --tls-cert) |
| MCPHEADERS | -H | | Response headers (collection) |
| MCPJSONRESPONSE | --json-response | false | JSON-only responses (disable SSE) |
| MCPDNSREBINDING | --dnsRebinding | false | Enable transport-level Origin/Host checks (loopback binds already get Host validation) |
| MCPALLOWEDORIGINS | --origin | | Allowed CORS origins (collection) |
| MCPALLOWEDHOSTS | --host | | Allowed hostnames (collection) |
| MCPKVPATH | --kv-path | | Custom Deno KV database path |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/phughesmcr-deno-mcp-template/)
- Source
- awesome · https://github.com/phughesmcr/deno-mcp-template
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.