MCP Test Server

Created By
nabadeep25a year ago
streamable http MCP Server using Nodejs
Overview

what is MCP Test Server?

MCP Test Server is a streamable HTTP Model Context Protocol (MCP) server built using Node.js, designed for testing and demonstration purposes with various tools.

how to use MCP Test Server?

To use the MCP Test Server, clone the repository, install the dependencies, configure the environment, and run the server. You can access the server at http://localhost:3000/mcp.

key features of MCP Test Server?

  • BMI Calculator for calculating Body Mass Index
  • Weather Service to get current weather information for any city
  • Echo Tool for simple message testing
  • Built with TypeScript and Express.js
  • Hot reload development support

use cases of MCP Test Server?

  1. Testing BMI calculations for health applications.
  2. Fetching weather data for a city in web applications.
  3. Using the echo tool for debugging and testing API requests.

FAQ from MCP Test Server?

  • What is the purpose of the MCP Test Server?

It serves as a testing platform for various tools and functionalities using the Model Context Protocol.

  • How do I install the MCP Test Server?

Clone the repository, install dependencies with npm, and configure the environment variables as needed.

  • Can I add new tools to the MCP Test Server?

Yes! You can create new tool files and register them in the server's main file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nabadeep25
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago