Simple MCP Server
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., "@Simple MCP Server what's the status of flight AA123?"
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.
Simple MCP Server
A simple Model Context Protocol (MCP) server implementation using TypeScript and the official MCP SDK.
Features
This MCP server provides:
Tools
echo: Echoes back the input text
add_numbers: Adds two numbers together
get_current_time: Returns the current date and time
get_flight_status: Get real-time flight status using flight number (supports both mock and real API data)
Resources
info://server: Server information and capabilities
greeting://hello: A simple greeting message
Related MCP server: TypeScript MCP Server Boilerplate
Installation
Install dependencies:
npm installBuild the project:
npm run buildUsage
Development Mode
Run the server in development mode with hot reloading:
npm run devProduction Mode
Build and run the compiled server:
npm run build
npm startWatch Mode
Build and watch for changes:
npm run watchMCP Client Integration
To use this server with an MCP client, you'll need to configure the client to connect to this server. The server uses stdio transport, so it can be launched as a subprocess.
Example configuration for MCP clients:
{
"mcpServers": {
"simple-server": {
"command": "node",
"args": ["path/to/dist/index.js"]
}
}
}Project Structure
├── examples/ # Example implementations
│ ├── resources/
│ │ └── example-resource.ts # Example resource implementations
│ └── tools/
│ └── example-tool.ts # Example tool implementations
├── src/ # Source code
│ ├── handlers/
│ │ └── index.ts # MCP request handlers
│ ├── resources/
│ │ ├── index.ts # Resource implementations
│ │ └── registry.ts # Resource registry
│ ├── tools/
│ │ ├── index.ts # Tool implementations
│ │ └── registry.ts # Tool registry
│ ├── types/
│ │ └── index.ts # TypeScript type definitions
│ ├── utils/
│ │ └── config.ts # Configuration and utilities
│ ├── index.ts # Main entry point
│ └── server.ts # Core server implementation
├── dist/ # Compiled JavaScript (generated)
├── package.json # Node.js dependencies and scripts
├── tsconfig.json # TypeScript configuration
├── test.js # Basic test script
├── test-comprehensive.js # Comprehensive test script
└── README.md # This fileModular Architecture
The server is built with a modular architecture that makes it easy to extend:
Tools: Each tool is a separate class implementing the
ToolHandlerinterfaceResources: Each resource is a separate class implementing the
ResourceHandlerinterfaceRegistries: Central registries manage all tools and resources
Handlers: Request handlers manage MCP protocol communication
Types: Shared TypeScript interfaces for type safety
Development
Adding New Tools
Create a new tool class implementing
ToolHandlerinsrc/tools/Add the tool to the
ToolRegistryinsrc/tools/registry.tsSee
examples/tools/example-tool.tsfor a complete example
Adding New Resources
Create a new resource class implementing
ResourceHandlerinsrc/resources/Add the resource to the
ResourceRegistryinsrc/resources/registry.tsSee
examples/resources/example-resource.tsfor complete examples
Flight Status Tool
The flight status tool provides real-time flight information:
Features:
Real-time flight status (scheduled, active, landed, cancelled, delayed)
Departure and arrival airport information
Airline details
Scheduled times
International flight support
Usage:
# Test the flight status tool
node test-flight-status.jsAPI Integration: By default, the tool uses mock data. To get real flight data:
Sign up for a free API key at AviationStack
Set the environment variable:
AVIATIONSTACK_API_KEY=your_api_keyRebuild and restart the server
Testing
Run the test scripts to verify functionality:
# Basic test
node test.js
# Comprehensive test with all features
node test-comprehensive.js
# Test flight status tool specifically
node test-flight-status.jsGit Configuration
The project includes a comprehensive .gitignore file that excludes:
Environment files (
.env*) containing API keysCompiled output (
dist/)Dependencies (
node_modules/)IDE/editor files
OS-specific files
Logs and temporary files
Important Security Note: API keys and secrets are automatically excluded from git tracking.
See GITIGNORE_INFO.md for detailed information about ignored files.
MCP Protocol
This server implements the Model Context Protocol (MCP) which allows AI assistants to securely access external tools and data sources. The server communicates via JSON-RPC over stdio.
For more information about MCP, visit: https://modelcontextprotocol.io/
Available Tools
4 toolsadd_numbersB
Add two numbers together
Inputs: a (required), b (required).
echoB
Echo back the input text
Inputs: text (required).
get_current_timeB
Get the current date and time
Inputs: no named parameters.
get_flight_statusB
Get the latest status of a flight using flight number
Inputs: flightNumber (required), airlineIata.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: mathematical addition, text echoing, time retrieval, and flight status checking. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
The naming follows a consistent verb_noun pattern (e.g., add_numbers, get_current_time) with one minor deviation: 'echo' is a verb-only name without a noun, which slightly breaks the pattern but remains readable and intuitive.
With only 4 tools, the server feels thin and lacks a cohesive domain focus, as it mixes unrelated utilities (math, text, time, flights). While the count is reasonable for a simple server, it suggests a lack of depth or clear scope.
The toolset is severely incomplete for any coherent domain; it appears as a random collection of utilities with no clear coverage. For example, if targeting travel, it lacks tools for booking or searching flights, and as a general utility server, it misses common operations like file handling or data conversion.
Maintenance
Related MCP Connectors
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…
Kickstart development with a customizable TypeScript template featuring sample tools for greeting,…
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA starter template for building MCP servers with TypeScript support, example tools, and automated installation scripts for Claude Desktop, Cursor, and other MCP-compatible AI assistants. Provides a foundation for creating custom tools, resource providers, and prompt templates.11 npm-
- AlicenseNot gradedqualityDmaintenanceA boilerplate project for quickly developing MCP servers with TypeScript, featuring example tools (calculator, greeting, time) and resources with Zod schema validation.ISC
- AlicenseNot gradedqualityDmaintenanceA boilerplate project for quickly developing MCP servers using TypeScript, featuring example implementations of tools (calculator, greetings) and resources (server info) with Zod schema validation.ISC
- AlicenseAqualityDmaintenanceA boilerplate for building MCP servers using TypeScript, with example tools like calculator and greet, plus resource support.6MIT