Skip to main content
Glama

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

Related MCP server: Tasker MCP

Setup Guide

  • Install 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

Conversation flow tests were impressive

Docs and References

Available Tools

12 tools
complete_actionC

Mark an action as done.

Inputs: action_id (required).

create_actionA

Create an action (task/to-do) that needs to be taken, optionally linked to an event.

Inputs: title (required), assignee, due_date, event_id, +2 more.

create_eventB

Create a new planning event (e.g. a meeting, milestone, deadline).

Inputs: title (required), start_time (required), tags, end_time, +2 more.

delete_actionC

Delete an action.

Inputs: action_id (required).

delete_eventA

Delete an event and all its associated actions.

Inputs: event_id (required).

get_actionA

Get full details of a single action by ID.

Inputs: action_id (required).

get_eventA

Get full details of a single event by ID.

Inputs: event_id (required).

get_plan_summaryB

Get a high-level summary of all events and their associated actions.

Inputs: no named parameters.

list_actionsA

List actions, optionally filtered by status, assignee, priority, or linked event.

Inputs: status, assignee, event_id, priority.

list_eventsA

List all events, optionally filtered by tag or date range.

Inputs: tag, after, before.

update_actionC

Update an action — change its status, assignee, priority, due date, etc.

Inputs: action_id (required), title, status, assignee, +4 more.

update_eventB

Update fields on an existing event.

Inputs: event_id (required), tags, title, end_time, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers