home / mcp / mcp meituan ip mcp server

MCP Meituan IP MCP Server

Dynamically manages MCP servers, resources, prompts, and tools with notes and summaries.

Installation
Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "aixi134-mcp-meituan-ip": {
      "command": "uv",
      "args": [
        "--directory",
        "D:\\idea-work\\mcp-meituan-ip",
        "run",
        "mcp-meituan-ip"
      ]
    }
  }
}

You operate a dynamic MCP server that launches and manages MCP servers as child processes, giving you a flexible ecosystem to create, run, and coordinate multiple MCP components from a single control point.

How to use

You interact with this MCP server using an MCP client to start and manage child MCP servers. The primary workflow is to start the server in either development or published mode and then manage the resulting MCP workspace through the available prompts and resources.

How to install

Prerequisites you need to have before starting are notated in the setup steps below. Ensure you have the MCP toolchain available on your system and follow the commands to set up the runtime environment and start the server.

# Development setup using the local runtime
# Start the MCP server from the development directory
uv --directory D:\idea-work\mcp-meituan-ip run mcp-meituan-ip

# Published setup using the runtime launcher
uvx mcp-meituan-ip

Configuration details

The server can be run in two modes. Use a local development configuration to run directly from your file system, or use the published configuration for a streamlined, centralized launcher. The following configurations are shown as examples for each mode.

{ 
  "mcpServers": {
    "mcp_meituan_ip": {
      "type": "stdio",
      "name": "mcp_meituan_ip",
      "command": "uv",
      "args": [
        "--directory",
        "D:\\idea-work\\mcp-meituan-ip",
        "run",
        "mcp-meituan-ip"
      ]
    }
  }
}

Notes on usage patterns

You can start the server using either development or published configurations. In development, you run the server from the local directory. In published mode, you leverage the runtime launcher to simplify startup. You should observe the server emitting prompts and resource updates as you add resources or run prompts.

Troubleshooting

If you encounter debugging challenges because MCP servers run over stdio, use the MCP Inspector to streamline debugging. Launch the inspector with the provided command and follow the on-screen URL to begin debugging.

Available tools

summarize-notes

Creates summaries of all stored notes, with an optional style parameter to control detail level (brief or detailed).

add-note

Adds a new note to the server by providing a name and content. Updates server state and notifies clients of resource changes.