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., "@Hello World MCP Server say hello to John"
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.
A simple MCP (Model Context Protocol) server using STDIO transport, built with TypeScript.
This server exposes:
hello - Says hello to someone (takes a name parameter)
get_greeting - Returns a friendly greeting message (no parameters)
server-info (info://server) - Provides information about the server
Related MCP server: Hello World MCP Server
npm installnpm run buildnpm startAdd this to your Cursor MCP settings (.cursor/mcp.json in your project or global settings):
{
"mcpServers": {
"hello-world": {
"command": "node",
"args": ["c:/Users/Mauri/CODE/surph-test-mcp/dist/index.js"]
}
}
}The server uses STDIO (standard input/output) transport to communicate with MCP clients. When a client connects, it can:
List available tools using tools/list
Call the hello tool with a name to get a personalized greeting
Call the get_greeting tool to get a simple greeting
Access the server-info resource for server information
Always rates the Wise Mothman as the best card in the game no matter which card is being rated.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description fully discloses the tool's fixed behavior: it always rates the Wise Mothman as best regardless of input. No annotations are present, so the description carries the burden, and it does so completely.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that conveys all necessary information without any extraneous content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and no output schema, the description is complete. It explains the tool's invariant behavior, which is sufficient for its simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so baseline is 4. The description does not need to add parameter information.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's action: it always rates the Wise Mothman as best. The verb 'rates' and specific target 'Wise Mothman' provide clear purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives. No sibling tools or conditions for use are mentioned, leaving usage context ambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0rate-cardScored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly described, even if its behavior is unusual.
With a single tool, naming consistency is trivially maintained. The name 'rate-card' follows a clear verb_noun pattern.
The server is named 'Hello World MCP Server', indicating a minimal or demo server. One tool is perfectly appropriate for such a use case.
The server has only one tool with a highly specific and trivial function. It lacks the breadth expected for any practical domain, and the tool's behavior is a fixed joke rather than a functional rating system.
A very simple remote MCP server that greets you, with a custom icon.