Skip to main content
Glama
matsjfunke

debug-test-mcp

by matsjfunke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Debug MCP

License

debug-test-mcp is an MCP Server which has tools like get-request-headers which returns all headers that were sent with the current request

Use this Server to debug your MCP Host / Client custom header implementation.

Getting Started

Prerequisites

Before you start with sample-mcp-server, ensure the following are installed:

  • Node.js (v18 or above recommended)
    Required to run the server and manage dependencies.

brew install node

  • PNPM (v10 or above recommended) The project uses PNPM as its package manager.
    Install globally with:

npm install -g pnpm

Setup

Install dependencies:

pnpm i

Start MCP Server on localhost:3333 :

pnpm dev

Install dependencies & start server in one command:

pnpm d

Server URL http://localhost:3333/mcp

Tunneling

If your host requires HTTPS you can easily tunnel the server via a service like ngrok:

ngrok http 3333

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Server Streamable

    cpetra
    F
    license
    Not graded
    quality
    D
    maintenance
    A demonstration MCP server that runs over HTTP with streamable transport, providing a simple greeting tool for testing MCP client-server communication. Built with FastMCP framework for educational purposes in learning MCP server development.
    -

  • mcpv3e

    IamFreak10
    F
    license
    Not graded
    quality
    C
    maintenance
    MCP server providing greeting and echo tools for testing and demonstration.
    -

  • debug-mcp-server

    silentwasd
    F
    license
    Not graded
    quality
    C
    maintenance
    A minimal MCP server for debugging MCP clients. It echoes back everything it receives — tool arguments, session IDs, metadata — so you can inspect exactly what your client is sending.
    -