MCP 91c

🚀 MCP Client Project Documentation

The MCP Client project aims to expose the local MCP server through the Flask framework and achieve intranet penetration. This project enables platforms such as Coze, Dify, and FastGPT to interact with local resources.

📦 Installation Guide

There is no installation guide provided in the original document, so this section is skipped.

✨ Features

• Exposes the local MCP server via the Flask framework.
• Enables intranet penetration for interaction with local resources.
• Provides multiple API interfaces for different operations.

📚 Documentation

Configuration File Explanation

mcp_server.json

This file is used to configure information about the MCP server. The specific content is as follows:

{
    "servers": [
        {
            "name": "server1", // Server name (customizable)
            "type": "http",   // Type: http or https
            "path": "/path/to/server1", // Service startup path
            "port": 8080,     // Service port
            "command": "python server1.py" // Startup command
        },
        {
            "name": "server2",
            "type": "http",
            "path": "/path/to/server2",
            "port": 8081,
            "command": "python server2.py"
        }
    ]
}

⚠️ Important Note

• Ensure that the path and startup command are correct.
• If the server type is HTTPS, specify it in the type field.

Security Precautions

Environment Variable Security

The .env file contains sensitive information (such as API keys). Please keep it properly:

• Avoid committing the .env file to the version control system.
• Do not place the file in a publicly accessible location.

Suggestions for Using Debug Mode

Debug mode is only suitable for the development environment. Disable it in the production environment:

app.run(debug=True, ssl_context='adhoc')

Solutions to Certificate Issues

Self-Signed Certificate Issues

When deploying on a cloud platform, self-signed certificates may cause failures in obtaining static resources.

Solutions:

1. Local Development Environment: Use self-signed certificates and debug mode.
2. Production Environment: Deploy a real SSL certificate issued by a trusted CA. Refer to the cloud platform documentation to complete the configuration.

API Interface Explanation

1. Get the Tool List

• Request Method: POST
• URL: /list_tool
• Request Body Example:

  {
      "server_name": "weather",
      "secret_key": "your-secret-key"
  }
  

• Response Example:

  {
      "tools": ["get_weather", "forecast"]
  }
  

2. Call a Tool

• Request Method: POST
• URL: /call_tool
• Request Body Example:

  {
      "server_name": "weather",
      "tool_name": "get_weather",
      "params": {"city": "Beijing"},
      "secret_key": "your-secret-key"
  }
  

3. Get the Server List

• Request Method: GET
• URL: /list_server
• Response Example:

  {
      "servers": ["server1", "server2"]
  }
  

4. Get the File List

• Request Method: GET
• URL: /list_files
• Response Example:

  {
      "files": ["file1.txt", "file2.csv"]
  }
  

5. Download a File

• Request Method: GET
• URL: /get_download_link?filename=file1.txt&secret_key=your-secret-key
• Response Example:

  {
      "download_url": "http://example.com/file1.txt"
  }
  

💻 Usage Examples

Example 1: Get the Tool List

curl -X POST http://localhost:5000/list_tool \
-H "Content-Type: application/json" \
-d '{"server_name":"weather","secret_key":"your-secret-key"}'

Example 2: Call a Tool

curl -X POST http://localhost:5000/call_tool \
-H "Content-Type: application/json" \
-d '{"server_name":"weather","tool_name":"get_weather","params":{"city":"Beijing"},"secret_key":"your-secret-key"}'

📄 License

There is no license information provided in the original document, so this section is skipped.

⚠️ Important Note

• Ensure that all API requests contain the correct secret_key.
• Adjust server configuration and permission settings according to actual needs.

By following the above steps, you can successfully configure and use the MCP Client project.