Stateless Hono MCP Server

An example Hono MCP server using Streamable HTTP. Exposed over MCP by the stateless hono mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

const server = getServer(); try { const transport: StreamableHTTPServerTransport = new StreamableHTTPServerTransport({ sessionIdGenerator: undefined, }); await server.connect(transport); - await transport.handleRequest(req, res, req.body); + await transport.handleRequest(req, res, await c.req.json()); res.on('close', () => { console.log('Request closed'); transport.close(); server.close(); }); + return toFetchResponse(res); } catch (error) { ```

Its toolset

Everything the assistant can do here goes through one of these:

• start-notification-stream — Starts sending periodic notifications for testing resumability
• greeting-template — A simple greeting prompt template

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Stateless Hono's toolset — start-notification-stream, greeting-template — is a fair guide to whether it matches your workflow. It is maintained by mhart; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Stateless Hono's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the stateless hono mcp server does with a few real requests.