Skip to main content
Glama
emaratHossain

eventin-mcp-server

README.md
Eventin MCP Server - Quick Start Guide
======================================

Setup Steps:
------------

1. Install Python 3.13 (if not already installed).

2. (Recommended) Create and activate a virtual environment:
   python -m venv .venv
   .\.venv\Scripts\activate

3. Install uv (if not already installed):
   pip install uv

4. Install dependencies:
   uv pip install -r requirements.txt
   OR
   uv pip install -e .

5. Start eventin locally, and check if it's running in the browser properly

6. Replace My base_url your yours

7. ![API TO CALL](image.png)

8. Run the Eventin MCP server:
   uv --directory . run eventin_mcp_server.py

   This will start the MCP server for Eventin bookings.

9. Logs:
   - Server logs are written to booking_server.log in this directory.

======================================

Steps to communicate with our MCP server using claude desktop:
------------

1. Download and install claude desktop
2. Open claude desktop, click "Upgrade to connect your tools to Claude" ![alt text](image-1.png)
3. Click "Manage Connectors" in right corner ![alt text](image-2.png)
4. Click "Developer" menu in the left side, and you find "Edit Config" button, click it ![alt text](image-3.png)
5. After that, you will find "claude_desktop_config.json", here just put following code
```jsx
   {
      "mcpServers": {
         "eventin": {
            "command": "uv",
            "args": [
            "--directory",
            "D:\\machine_learning\\mcp-server-demo", //your directory may be different
            "run",
            "eventin_mcp_server.py"
            ]
         }
      }
   }
```
7. Now you will see that, your mcp tools are connected with the claude ![alt text](image-4.png)
8. Sample output <img width="1522" height="813" alt="image" src="https://github.com/user-attachments/assets/a2ce8ca9-b25b-4bdb-88f6-9abbf02ff4c6" />

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are clearly distinct: get_bookings returns individual booking records with filters, while get_booking_stats provides summary statistics. There is no functional overlap, making selection unambiguous.

Naming Consistency5/5

Both tool names follow a consistent pattern: 'get_' followed by a noun, using snake_case (get_bookings, get_booking_stats). This is predictable and uniform.

Tool Count3/5

With only two tools, the server feels thin and below the typical well-scoped range of 3-15 tools. While both tools are relevant to bookings, the count is borderline and may be insufficient for broader event management needs.

Completeness2/5

The server only provides read and aggregate operations (list bookings, get stats). Missing are any create, update, cancel, or delete functionalities, which are essential for a complete booking management workflow. This represents significant gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues