Skip to main content
Glama
README.md
# MCP Server

A simple MCP server, dubbed cuebit, based on a concept of an event scheduling and automation platform.

## Requirements

- Python > 3.10
- Claude Desktop

## Setup Guide

- Install [uv](https://docs.astral.sh/uv/) (a lightweight rust-based python package manager)
- Install dependencies
- Start MCP Server (```uv run cuebit.py```)
- Update clause code config the running new MCP Server

   ### MacOS

    ```cat ~/Library/Application\ Support/Claude/claude_desktop_config.json```
 

    Update the JSON to specify how clause can run the server
    
    ```
        "mcpServers": {
        "weather": {
          "command": "uv",
          "args": [
            "--directory",
            "/ABSOLUTE/PATH/TO/PARENT/FOLDER/cuebit",
            "run",
            "cuebit.py"
          ]
        }
      }
    ```

## Testing with claude desktop

Successful connection will have the MCP Server accessible via connectors on claude desktop
<img width="1069" height="708" alt="image" src="https://github.com/user-attachments/assets/dc05f652-dcad-49e6-9887-7e6d29aaed73" />


Conversation flow tests were impressive
<img width="1069" height="828" alt="image" src="https://github.com/user-attachments/assets/42071548-5c27-4f7b-a706-549dabd385cd" />



## Docs and References

- [Model Context Protocol Documentation](https://modelcontextprotocol.io/docs/develop/build-server)
- 

TDQS

A3.6/5.0

Scored across 12 tools

Disambiguation4/5

Tools are cleanly split between events and actions, with each resource having dedicated CRUD operations. The only mild overlap is between complete_action and update_action, since completion could be expressed as a status update, but the explicit purpose is clear enough.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: get/create/list/update/delete/complete plus event/action. The naming is predictable and makes the tool surface easy to navigate.

Tool Count5/5

Twelve tools is well-scoped for a planning/event-and-action server. Each tool covers a distinct operation, and the count feels complete without being bloated.

Completeness5/5

The toolset provides full CRUD for both events and actions, plus a dedicated completion action and a summary endpoint. There are no obvious dead ends; the main workflows of creating, viewing, updating, and removing planning items are all covered.

Maintenance

ActivityInactive
ResponsivenessNo issues