MCP

Small MCP servers to copy from. Each is one file in servers/, and mcp.ts does the MCP part, so a server file is just what it offers.

MCP is not an AI. An MCP server adds abilities to an AI app you already use (Claude, Codex, ChatGPT, …): the app is the client, and it calls the server.

The three things a server can offer

Both list a prompt in the / menu as /:, so /recipes:plan_meal, tagged (MCP) to show it comes from a server. Pick it there and fill in the blanks when asked. In the terminal, the older spelling /mcp__recipes__plan_meal 6 also works when typed out, with arguments separated by spaces (so each argument is one word). Either way the server has to be connected first: right after claude starts, or before you’ve approved .mcp.json, you get “Unknown command”. /mcp shows which servers are connected.

VS Code’s @ lists only workspace files, not resources, so there you ask Claude to read one instead.

Tools are the main event. Many apps support only tools, so treat resources and prompts as extras.

The servers

• hello.ts has one tool, greet. It’s the minimal template.
• dice.ts has two tools, roll_dice and flip_coin, with arguments that have limits and defaults.
• recipes.ts offers all three kinds over a few recipes:
  • the tool search_recipes
  • the resources recipe://index and recipe://{name}
  • the prompt plan_meal

Running one in Claude Code

Claude Code (the claude CLI, and the Claude Code panel in VS Code) starts the servers itself over stdio. Nothing is left running, and there’s nothing to host. All three are listed in .mcp.json, so starting Claude Code in this repo picks them up, after a one-time approval. To add a new one, run this from the repo:

claude mcp add --scope project dice -- deno run -A ./servers/dice.ts --stdio