MCP.so
Sign In

Deno MCP Template Repo

@phughesmcr

Basic information

Category

Developer Tools

License

MIT

Transports

stdio

Author

phughesmcr

About Deno MCP Template Repo

A template repo for writing and publishing local, remote, DXT, and binary MCP servers using Deno.

Deno MCP Template Repo config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "deno-mcp-template": {
      "command": "deno",
      "args": [
        "task",
        "setup"
      ]
    }
  }
}

Deno MCP Template Repo tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Deno MCP Template Repo?

A batteries-included starting point for building production Model Context Protocol (MCP) servers in TypeScript using Deno. It ships with STDIO and HTTP transports, security middleware, persistent state, sandboxed execution, CI/CD workflows, and multiple distribution formats including JSR packages, native binaries, DXT extensions, and Deno Deploy hosting.

How to use Deno MCP Template Repo?

Clone the template with gh repo create my-mcp-server --template phughesmcr/deno-mcp-template, run deno task setup for one-time placeholder renaming, then start with deno task start to run both STDIO and HTTP on localhost:3001. Connect any MCP client by configuring the command to deno run -A main.ts or use a compiled binary, JSR package, or DXT extension.

Key features of Deno MCP Template Repo

  • Dual STDIO and Streamable HTTP transports from a single app
  • Deno KV persistent state with zero-config local storage
  • HTTP middleware including rate limiting, CORS, and bearer auth
  • Sandboxed code execution via @deno/sandbox microVMs
  • CI/CD workflows for testing, release, deploy, and JSR publish
  • Multiple distribution formats: JSR, binary, DXT, or Deno Deploy
  • Example prompts, resources, tools, and task workflows included

Use cases of Deno MCP Template Repo

  • Quickly scaffold a production-ready MCP server for AI agent integration
  • Serve MCP tools and resources over STDIO for desktop clients like Claude Desktop or Cursor
  • Deploy a remote MCP server with Streamable HTTP for cloud-hosted agents
  • Publish an MCP server as a JSR package or standalone binary for distribution
  • Experiment with MCP features including sampling, elicitation, subscriptions, and async tasks

Frequently asked questions

1

What transports does the server support?

The server supports both STDIO transport and Streamable HTTP transport, running simultaneously from a single application.

2

What runtime and dependencies are required?

You need Deno installed. No external databases like Postgres or Redis are required — Deno KV provides persistent state locally and on Deno Deploy.

3

Where does data persist?

Data persists in Deno KV, which works zero-config locally and is built-in on Deno Deploy. An event store for session resumability is also KV-backed.

4

How do I secure the HTTP endpoint?

Set `MCP_HTTP_BEARER_TOKEN` for bearer authentication; set `MCP_REQUIRE_HTTP_AUTH=true` to fail startup if no token is provided. CORS allows only explicit origins, rate limiting is applied, and binding to non-loopback without a token logs a warning.

5

What distribution formats are available?

You can run locally via STDIO, serve over HTTP, publish as a JSR package, compile to a native binary, package as a DXT extension, or deploy to Deno Deploy.

Comments

More Developer Tools MCP servers