Random Number MCP Server

🚀 Random Number MCP Server

This project implements a simple Model Context Protocol (MCP) server, providing a tool to generate random numbers using the random.org API.

🚀 Quick Start

This server demonstrates the basic concepts of MCP, including:

• Setting up an MCP server.
• Defining and implementing tools.
• Integrating external APIs.
• Configuring the server for use with MCP clients.

✨ Features

• Random Number Generation: Utilizes the random.org API to generate truly random numbers.
• MCP Compatibility: Implements the MCP protocol, allowing seamless integration with MCP clients.

📦 Installation

Prerequisites

• Node.js and npm installed.
• An MCP client, such as the Claude desktop application.

Project Setup

1. Clone the repository:

   git clone [repository_url]
   cd [project_directory]
   

2. Install dependencies:

   npm install
   

💻 Usage Examples

Basic Usage

Once the server is running and configured, you can use the get_random_number tool through an MCP client.

API

The server uses the random.org API to generate truly random numbers. No API key is required for basic usage.

MCP Server Implementation

The server is implemented in index.ts and uses @modelcontextprotocol/sdk to handle MCP communication.

Tool: get_random_number

This tool retrieves a random integer from the random.org API.

Input Parameters:

• max (optional): An integer specifying the maximum value (inclusive). Defaults to 100.

Output:

• A string containing the random number.

Server Configuration

The server is configured through the cline_mcp_settings.json file. You need to add an entry for this server, specifying the command to run it:

{
  "mcpServers": {
    "random-number": {
      "command": "node",
      "args": ["[path/to/index.js]"],
      "env": {}
    }
  }
}

Replace [path/to/index.js] with the actual path to the index.js file (usually located in the build or dist directory after running npm run build).

Running the Server

1. Build the server

   npm run build
   

2. Start the server (this is usually done automatically after configuration by the MCP client).