Meeting MCP

🚀 Meeting Management Platform (MCP) Integration Guide

The Meeting Management Platform (MCP) offers seamless integration with various applications and provides a comprehensive development guide. This document details how to integrate MCP with different tools, the development process, project structure, authentication mechanisms, and license information.

🚀 Quick Start

Integration with Claude Desktop

1. Open Claude Desktop.
2. Navigate to the settings.
3. Click on "Model Context Protocol".
4. Add a new server with the following configuration:
   • Name: Meeting Management Platform MCP
   • Type: sse (Server - Sent Events)
   • Server Address: http://localhost:7017/mcp
   • Optionally, add necessary request headers for authentication.

Integration with Cursor

1. Open Cursor.
2. Go to the settings interface.
3. Navigate to the "Model Context Protocol" option.
4. Add a new server configuration:
   • Name: Meeting Management Platform MCP
   • Type: sse
   • Server Address: http://localhost:7017/mcp
   • Optionally, add request headers required for authentication.

📦 Installation

Build the Project

npm run build

Test with MCP Inspection Tool

npm run inspect

Development Mode (Supports Auto - Restart)

npm run dev

💻 Usage Examples

Log Management

npm run cleanup

This command performs the following operations:

• Cleans up unnecessary log files and cached data.
• Filters out duplicate heartbeat messages.
• Reduces disk usage while retaining important information.
• Maintains a small log footprint, suitable for long - running servers.

📚 Documentation

Project Structure

• src/index.ts: The entry point of the program.
• src/tools/: Tool implementation files.
• src/resources/: Resource definition files.
• src/api/: API clients for communicating with the Meeting Management Platform backend.
• src/types/: TypeScript type definitions.
• src/config.ts: Server configuration.
• src/utils/:
  • logging.ts: Log filtering and management tools.
  • tinyDb.ts: A database for persistent storage of bot information.

Authentication Mechanism

The server requires an API key in the x - api - key request header for authentication. By default, you can set the default API key through the configuration file.

In addition, many tools (named with the pattern "WithCredentials") support passing the API key directly as a parameter instead of in the request header.

🔧 Technical Details

QR Code Generation API Key Configuration

The QR code generator tool requires an API key from the QR Code AI API. Here are several ways to provide it:

1. Include directly in the prompt: When calling the generateQRCode tool, write the API key directly into the prompt text, e.g., "Generate a QR code for my website https://example.com, API key: qrc_your_key_here".
2. Pass as a parameter: When using the generateQRCode tool, provide the apiKey parameter.
3. Environment variable: Set the QRCODE_API_KEY environment variable.
4. Claude Desktop configuration: Add the API key to your Claude Desktop configuration file:
   • Mac/Linux system path: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows system path: %APPDATA%\Claude\claude_desktop_config.json

Example configuration:

{
  "headers": {
    "x-api-key": "qrc_your_key_here"
  }
}

The tool will search for the API key in the order mentioned above. If no key is provided, the available default API key will be used.

To obtain an API key, visit QR Code AI API to register an account.

📄 License

MIT