Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-first-server Add 5 and 7"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Primer servidor MCP (Model Context Protocol) en TypeScript, siguiendo la actividad First Server del MCP Workshop.
Expone dos capacidades sobre transporte stdio:
Tipo | Nombre | Descripción |
Tool |
| Suma dos números ( |
Resource |
| Devuelve |
Node.js 18+ (probado con v25)
npm
Related MCP server: Python MCP Server
npm install
npm run buildnpm run inspectorAbre la interfaz web del MCP Inspector, donde puedes listar y ejecutar la tool add
y leer el resource greeting://{name}.
Sin inspector, hablando JSON-RPC directo por stdio:
printf '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"t","version":"0"}}}\n{"jsonrpc":"2.0","method":"notifications/initialized"}\n{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"add","arguments":{"a":2,"b":3}}}\n{"jsonrpc":"2.0","id":3,"method":"resources/read","params":{"uri":"greeting://Mundo"}}\n' | node build/index.jsSalida esperada (entre otras líneas):
{"result":{"content":[{"type":"text","text":"5"}]},"jsonrpc":"2.0","id":2}
{"result":{"contents":[{"uri":"greeting://Mundo","text":"Hello, Mundo!"}]},"jsonrpc":"2.0","id":3}Ejemplo de configuración (Claude Desktop, VS Code, etc.):
{
"mcpServers": {
"demo": {
"command": "node",
"args": ["/ruta/absoluta/a/mcp-first-server/build/index.js"]
}
}
}src/index.ts código del servidor
tsconfig.json compila src/ -> build/
build/ salida compilada (no versionada)Inputs: a (required), b (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
With only one tool, there is no risk of confusing it with another tool. The tool is uniquely identifiable even without a description.
A single tool named 'add' introduces no naming conflicts or mixed conventions. Consistency is trivially maintained.
A server exposing exactly one tool with no description is an extreme mismatch—there is no meaningful tool surface to serve a coherent purpose.
The tool 'add' without a description or supporting tools provides no discernible domain coverage. The surface is severely incomplete and effectively useless for real tasks.
Persistent memory, hybrid search and a goal graph for AI agents, over stdio or remote HTTP.
Remote streamable-HTTP MCP server running on a single Cloudflare Worker. Your assistant gets live Airbnb, Amazon, Booking.com, Google Flights, Maps and Reddit data, social search on X, Instagram and TikTok, the Meta Ad Library, and image/video generation without any keys. Connect your own accounts to let it send WhatsApp or Telegram messages, work an IMAP inbox, manage Meta Ads campaigns and publish to X and LinkedIn. OAuth 2.1 with PKCE; stored credentials are AES-256-GCM encrypted.
