Summary

A template, and honest about it.

One dice tool is not a product, and the repository's own next steps say as much — add more tools, customise this one, deploy. What it gives you is a working HTTP MCP endpoint on Vercel and the two client configurations to reach it, which is the part that usually costs an afternoon.

What it is

A small Next.js project that serves MCP over HTTP from a Vercel deployment. It ships with exactly one tool, so the value is the wiring: the route handler, the deployment path, and the client configuration that connects to it.

What you get

`roll_dice` rolls an N-sided die and returns the result; `sides` is a number with a minimum of 2
An HTTP MCP endpoint, at `http://localhost:3000/api/mcp` locally and `/api/mcp` on your deployment
The handler lives in `app/api/mcp/route.ts`, which is where you add tools of your own

Requirements

Node.js and npm. `npm install` then `npm run dev` runs it locally. To deploy: push the repository to GitHub, connect it to Vercel, and deploy — your endpoint is then at `/api/mcp` under your project's domain. Cursor connects by server URL. The README configures Claude Desktop through `@modelcontextprotocol/server-fetch`, which npm does not have.