Provides example implementations and source code through GitHub repositories.
Available as an npm package for easy installation in Node.js projects.
Provides full TypeScript integration with type safety for creating MCP servers.
Implements built-in parameter validation using Zod schemas for MCP tools.
Click on "Install 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., "@MCPKit create a greeting tool that accepts a name parameter"
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 TypeScript library for creating MCP (Model Context Protocol) servers.
Simple API: Create MCP servers with minimal code
Type Safety: Full TypeScript integration
Parameter Validation: Built-in validation with Zod
MCP Compatible: Fully implements the Model Context Protocol
Related MCP server: easy-mcp
npm install simple-mcpimport { McpServer } from 'simple-mcp';
import { z } from 'zod';
// Create a server instance
const server = new McpServer({ name: 'my-server' });
// Register the tool with the server
server.tool({
name: 'greet',
parameters: {
name: z.string().describe('Person\'s name')
},
execute: async ({ name }) => {
return {
content: [
{
type: 'text',
text: `Hello, ${name}! Nice to meet you.`
}
]
};
}
});
// Start the server
server.start({ transportType: 'stdio' });You can also implement MCP tools using classes:
import { McpServer, type McpTool } from 'simple-mcp';
import { z, ZodObject } from 'zod';
const parameters = {
name: z.string().describe('The name is required'),
};
class GreetTool implements McpTool<typeof parameters> {
public readonly name = 'greet';
public readonly parameters = parameters;
public async execute({ name }: z.infer<ZodObject<typeof this.parameters>>) {
return {
content: [
{
type: 'text',
text: `Hello, ${name}! Nice to meet you.`,
},
],
};
}
}
// Initialize a new MCP server with the name 'greet-server'
const server = new McpServer({ name: 'greet-server' });
// Create an instance of the GreetTool class
const greetTool = new GreetTool();
// Register the tool with the server
server.tool(greetTool);
// Start the server using stdio as the transport method
server.start({ transportType: 'stdio' });Check out the examples directory for more complete examples:
Greeting Tool - Simple greeting example
Calculator Tool - Mathematical operations example
Contributions are welcome! Feel free to open issues or submit pull requests.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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. Dates show when Glama detected each change.
greetWith only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'greet' stands alone without any competing or confusing alternatives.
A single tool inherently exhibits perfect naming consistency as there are no other tools to compare against. The name 'greet' follows a simple verb pattern, and with no other tools, there is no inconsistency.
One tool is generally too few for a server's purpose unless it is extremely narrow, but without a description for 'greet', the scope is unclear. Typically, servers with a single tool feel thin and may not justify a full MCP server, suggesting a mismatch unless the domain is trivial.
With only one tool and no description provided, it is impossible to assess coverage of any domain. The tool surface is severely incomplete as there are no details to infer a purpose or evaluate missing operations, leading to dead ends for agents.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
A simple Typescript MCP server built using the official MCP Typescript SDK and smithery/cli. This…
A TypeScript MCP server for Home Assistant, enabling programmatic management of entities, automati…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
A Model Context Protocol (MCP) server for Selise Blocks Cloud integration
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ribeirogab/simple-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
