Skip to main content
Glama

Sloot MCP Server

by meefer33
GitHub
TypeScript
OverviewInspectNewEndpointsSchemaRelated ServersReviewsScore
Need Help?View Source CodeReport Issue

Sloot MCP Server

A complete TypeScript Model Context Protocol (MCP) server implementation using Express.js and the official MCP SDK.

Features

  • 🚀 Express.js HTTP Server: RESTful API with MCP protocol support

  • 🔧 Session Management: Automatic session handling with UUID-based session IDs

  • 🛠️ Built-in Tools: Example tools including echo, time, and calculator

  • 📡 Streamable Transport: HTTP-based transport with Server-Sent Events (SSE)

  • 🔒 Type Safety: Full TypeScript implementation with strict typing

  • ❤️ Health Monitoring: Built-in health check endpoint

Available Tools

The server provides the following MCP tools:

  1. echo - Echo back any message

  2. get_time - Get current server time

  3. calculate - Perform basic mathematical calculations

Quick Start

Prerequisites

  • Node.js 18+

  • npm or yarn

Code Quality Tools

This project includes:

  • ESLint - Code linting with TypeScript support

  • Prettier - Code formatting

  • TypeScript - Type checking and compilation

Installation

  1. Clone or download this project

  2. Install dependencies:

npm install

Development

Run the server in development mode with hot reload:

npm run dev

Production

Build and run the production server:

npm run build npm start

Watch Mode

Run with file watching for development:

npm run watch

Code Quality

Check code quality and formatting:

# Lint the code npm run lint # Fix linting issues automatically npm run lint:fix # Format code with Prettier npm run format # Check if code is properly formatted npm run format:check # Run all checks (lint + format check + build) npm run check

Usage

Starting the Server

The server will start on port 3000 by default (configurable via PORT environment variable):

🚀 MCP Server running on port 3000 📡 MCP endpoint: http://localhost:3000/mcp ❤️ Health check: http://localhost:3000/health

MCP Endpoints

  • POST /mcp - Main MCP communication endpoint

  • GET /mcp - Server-to-client notifications (SSE)

  • DELETE /mcp - Session termination

  • GET /health - Health check and status

Testing the Server

You can test the health endpoint:

curl http://localhost:3000/health

Response:

{ "status": "healthy", "timestamp": "2024-01-01T12:00:00.000Z", "activeSessions": 0 }

MCP Client Integration

This server is designed to work with MCP clients. The server handles:

  • Session initialization with automatic UUID generation

  • Session persistence across requests

  • Proper cleanup when sessions are closed

  • DNS rebinding protection (configurable)

Session Headers

When making requests to the MCP endpoint, include the session ID in headers:

mcp-session-id: <session-uuid>

Configuration

Environment Variables

  • PORT - Server port (default: 3000)

DNS Rebinding Protection

For local development, you can enable DNS rebinding protection by uncommenting and configuring these options in the transport configuration:

enableDnsRebindingProtection: true, allowedHosts: ['127.0.0.1'],

Development

Project Structure

sloot-mcp/ ├── src/ │ └── index.ts # Main server implementation ├── dist/ # Compiled JavaScript (generated) ├── package.json # Dependencies and scripts ├── tsconfig.json # TypeScript configuration └── README.md # This file

Scripts

  • npm run build - Compile TypeScript to JavaScript

  • npm run start - Run the compiled server

  • npm run dev - Run with tsx for development

  • npm run watch - Run with file watching

  • npm run lint - Run ESLint to check for code issues

  • npm run lint:fix - Run ESLint and automatically fix issues

  • npm run format - Format code with Prettier

  • npm run format:check - Check if code is properly formatted

  • npm run check - Run linting, formatting check, and build

Extending the Server

Adding New Tools

To add new tools, modify the ListToolsRequestSchema handler in src/index.ts:

server.setRequestHandler(ListToolsRequestSchema, async () => { return { tools: [ // ... existing tools { name: "your_tool", description: "Description of your tool", inputSchema: { type: "object", properties: { // Define your tool's parameters }, required: ["required_param"] } } ] }; });

Then add the tool implementation in the CallToolRequestSchema handler.

Adding Resources

You can add MCP resources by implementing the appropriate request handlers for resources.

License

MIT

This server cannot be installed

-
security - not tested
F
license - not found
-
quality - not tested

How are these scores calculated?

remote-capable server

The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.

A TypeScript MCP server implementation using Express.js that provides basic tools like echo, time retrieval, and calculator functionality. Features session management, RESTful API endpoints, and Server-Sent Events for streamable communication.

  1. Features
    1. Available Tools
      1. Quick Start
        1. Prerequisites
        2. Code Quality Tools
        3. Installation
        4. Development
        5. Production
        6. Watch Mode
        7. Code Quality
      2. Usage
        1. Starting the Server
        2. MCP Endpoints
        3. Testing the Server
      3. MCP Client Integration
        1. Session Headers
      4. Configuration
        1. Environment Variables
        2. DNS Rebinding Protection
      5. Development
        1. Project Structure
        2. Scripts
      6. Extending the Server
        1. Adding New Tools
        2. Adding Resources
      7. License

        New MCP Servers

        MCP directory API

        We provide all the information about MCP servers via our MCP API.

        curl -X GET 'https://glama.ai/api/mcp/v1/servers/meefer33/sloot-mcp'

        If you have feedback or need assistance with the MCP directory API, please join our Discord server