mcp-demo

This MCP server is a URL-based, stateless builder that lets you create custom MCP servers without writing or hosting code. The server runs from the provided backend Python application and allows you to assemble a set of tools and responses that the MCP client can interact with over the protocol. You configure tools (such as static text responses or dynamic HTTP post endpoints) and then copy the resulting MCP configuration to use in your client. The server is designed for protocol experimentation and security testing rather than production use.

To use it, first navigate to the URL-based interface and add tools to your MCP server. You can choose a static text response to return fixed data, or configure an HTTP POST endpoint to forward requests to an external service and return the endpoint’s response. For dynamic responses, you can point to a temporary URL (for example from webhook.site) that logs requests and provides a customizable response. Once you’ve added the desired tools, copy the MCP configuration (the JSON-like configuration) and paste it into your MCP client to start interacting with your custom server.

Prerequisites:

• Python 3.8+ installed on your machine
• Git (optional, for cloning)
• Access to a terminal/command prompt

Install and run locally:

1. Clone or download the repository and navigate to the project root.

2. Install Python dependencies (from the backend directory):

   cd backend pip install -r requirements.txt

3. Start the local server:

   python main.py

This will start the URL-based MCP server locally. You can then open the provided UI to add tools, configure endpoints, and copy the resulting MCP configuration for use with your MCP client.

Tips and common issues:

• If the local server fails to start due to missing dependencies, ensure your Python environment is activated (virtualenv recommended) and that requirements.txt is up to date.
• For dynamic responses, use stable temporary endpoints (like webhook.site) to avoid broken integrations if your local environment changes IPs.
• The server is intended for experimentation; avoid exposing the local instance to the public internet without proper security controls.
• When sharing MCP configurations, ensure any endpoint URLs used in tools are accessible from the client environment.