MCP Server Scaffolder

A list of tools in, a complete MCP server skeleton out in TypeScript or Python, with the client entry that registers it and the transport wiring already written.

Server nameLower case, hyphens. Used as the package and the client key.

Language

What this server is forShown by clients that list servers.

Transport

Your toolsOne per line: name(arg: type, arg: type = default) = what it does. Types: str, int, float, bool, list[str], or a union of quoted literals.

Tools in the server

6 arguments across them. Every tool is offered to the model on every request the client makes, so its name and description are a recurring cost as well as a recurring decision.

Tools: 3
Arguments: 6
Tools with no description: 0
Generated characters: 2,670
Problems found: 0

src/index.tsRead-only. Select all and copy.

/* orders — an MCP server.
 *
 * Written against the high-level McpServer API of @modelcontextprotocol/sdk.
 * NOTHING HERE HAS BEEN RUN: this page generates text and cannot install or
 * type-check anything. If the SDK version you install disagrees, the shape of
 * the registerTool call is the thing to check first.
 */
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";

const server = new McpServer({
  name: "orders",
  version: "0.1.0",
});

server.registerTool(
  "search_orders",
  {
    description: "Find a customer's orders by email address. Use when the user asks about the status of an order.",
    inputSchema: {
      email: z.string().describe("TODO: what is email?"),
      status: z.enum(["open", "shipped", "cancelled"]).optional().describe("TODO: what is status?"),
      limit: z.number().int().optional().describe("TODO: what is limit?"),
    },
  },
  async ({ email, status, limit }) => {
    // TODO: do the work. Throwing here is reported to the model as an error,
    // which is usually what you want — it can then try something else.
    const result = { email, status, limit };
    return { content: [{ type: "text", text: JSON.stringify(result) }] };
  },
);

server.registerTool(
  "get_order",
  {
    description: "Fetch one order by its reference. Use when the user names a specific order.",
    inputSchema: {
      order_id: z.string().describe("TODO: what is order_id?"),
    },
  },
  async ({ order_id }) => {
    // TODO: do the work. Throwing here is reported to the model as an error,
    // which is usually what you want — it can then try something else.
    const result = { order_id };
    return { content: [{ type: "text", text: JSON.stringify(result) }] };
  },
);

server.registerTool(
  "cancel_order",
  {
    description: "Cancel an order that has not shipped. Ask the user to confirm before calling this.",
    inputSchema: {
      order_id: z.string().describe("TODO: what is order_id?"),
      reason: z.string().describe("TODO: what is reason?"),
    },
  },
  async ({ order_id, reason }) => {
    // TODO: do the work. Throwing here is reported to the model as an error,
    // which is usually what you want — it can then try something else.
    const result = { order_id, reason };
    return { content: [{ type: "text", text: JSON.stringify(result) }] };
  },
);

const transport = new StdioServerTransport();
await server.connect(transport);
// stdio servers must never write to stdout: it IS the protocol channel.
// console.error is safe; console.log will corrupt every message.

package.jsonRead-only. Select all and copy.

The client entry that registers itThe `mcpServers` shape most clients take. Check your own client's documentation for where the file lives.

What this assumes: the description is copied from your line and everything else is a TODO — a scaffolder that invented argument descriptions would be writing the most important part of the file for you, badly. Names are checked against the character set clients accept and the code is generated against the SDKs' high-level server API, but nothing here is executed, installed or type-checked, so “it compiles” is a claim this page cannot make. The stdio warning in the generated file is not decoration: stdout is the protocol. Everything on this page runs in your browser. Nothing you paste is uploaded, logged or sent anywhere.

Most of the work in a first MCP server is not the tools. It is the twenty lines of wiring that differ between transports, the client entry whose exact shape you have to look up, and the discovery that your console.log debugging has been corrupting the protocol stream all along — stdio servers speak JSON-RPC on stdout, so anything else written there breaks every message. That is why the generated file says so in a comment rather than in a paragraph you would read once.

Where the effort actually goes

Into the descriptions. A tool is chosen by a model reading a name, a sentence and an argument list, so “cancel_order — cancels an order” is not a description, it is a restatement. The useful version says when to call it and when not to: that it is for orders that have not shipped, that it cannot be undone, that the user should confirm first. This page leaves every argument description as a marked TODO for exactly that reason.

Local or remote

stdio means the client starts your server as a subprocess on the same machine, which is simple and inherits whatever credentials that machine has. Streamable HTTP means it is a service, reachable by anything that can reach the URL — which is a much larger question about who may call your tools, and one no scaffolder can answer for you. Start with stdio; move when you have a reason and an answer.

MCP Server Scaffolder

Where the effort actually goes

Local or remote

The reasoning behind this

Related tools