A template repo for writing and publishing local, remote, DXT, and binary MCP servers using Deno.
Most monitoring and observability work still happens through a UI a human drives. Deno MCP Template Repo MCP server moves it into the conversation instead. A template repo for writing and publishing local, remote, DXT, and binary MCP servers using Deno.
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.
The server publishes 14 tools. What each one is for:
Authentication — ** Set MCP_HTTP_BEARER_TOKEN (or --http-bearer-token) so clients must send Authorization: Bearer … or x-api-key: … on /mcp. For CI or productionExposure — ** Binding to a non-loopback hostname without a token logs a warning: anyone who can reach the port can use MCP. Use a token or terminate TLS andCORS — ** Wildcard * origins are not allowed; list explicit origins (e.g. MCP_ALLOWED_ORIGINS)CLAUDE.md — - optional Claude Code project contextWhat — HowGoal — CommandVariable — FlagMCP_NO_HTTP — --no-httpMCP_NO_STDIO — --no-stdioMCP_HOSTNAME — -nMCP_PORT — -pMCP_PUBLIC_BASE_URL — --public-base-urlConfiguration is passed through the environment: MCP_HTTP_BEARER_TOKEN, MCP_PUBLIC_BASE_URL, DENO_DEPLOY_TOKEN, MCP_TLS_KEY, MCP_KV_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Deno MCP Template Repo's toolset — Authentication, Exposure, CORS and 11 more — is a fair guide to whether it matches your workflow. It is maintained by phughesmcr; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Authentication | ** Set MCP_HTTP_BEARER_TOKEN (or --http-bearer-token) so clients must send Authorization: Bearer … or x-api-key: … on /mcp. For CI or production templates, MCP_REQUIRE_HTTP_AUTH=true fails startup if no token is set. Pat |
| Exposure | ** Binding to a non-loopback hostname without a token logs a warning: anyone who can reach the port can use MCP. Use a token or terminate TLS and auth at a reverse proxy. |
| CORS | ** Wildcard * origins are not allowed; list explicit origins (e.g. MCP_ALLOWED_ORIGINS). |
| CLAUDE.md | - optional Claude Code project context |
| What | How |
| Goal | Command |
| Variable | Flag |
| MCP_NO_HTTP | --no-http |
| MCP_NO_STDIO | --no-stdio |
| MCP_HOSTNAME | -n |
| MCP_PORT | -p |
| MCP_PUBLIC_BASE_URL | --public-base-url |
| MCP_TLS_CERT | --tls-cert |
| MCP_TLS_KEY | --tls-key |
Connect from any MCP client:
```json
{
"mcpServers": {
"my-mcp-server": {
"command": "deno",
"args": ["run", "-A", "/absolute/path/to/main.ts"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MCP_HTTP_BEARER_TOKEN | Credential the server authenticates with. | Yes |
| MCP_PUBLIC_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| DENO_DEPLOY_TOKEN | Credential the server authenticates with. | Yes |
| MCP_TLS_KEY | Credential the server authenticates with. | Yes |
| MCP_KV_PATH | Filesystem location the server is allowed to use. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.