cal-auto-python MCP Server

What this does

cal-auto-python exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

GITHUB_TOKEN
GITHUB_PROJECT_ID
CAL_AUTO_TIMEZONE
CAL_AUTO_CONFIG_DIR
CAL_AUTO_WORKING_DAY_START
CAL_AUTO_WORKING_DAY_END
CAL_AUTO_CALENDAR_ID
CAL_AUTO_TASK_LIST_ID
CAL_AUTO_ATTENDEES
CAL_AUTO_SCHEDULABLE_STATUSES
CAL_AUTO_COUNT_ALL_DAY_EVENTS

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install cal-auto-python?

Run the Claude Code command in the install section to add cal-auto-python to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with cal-auto-python?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to cal-auto-python as well.

Does cal-auto-python need an API key?

Yes. Before it can run, set these environment variables: GITHUB_TOKEN, GITHUB_PROJECT_ID, CAL_AUTO_TIMEZONE, CAL_AUTO_CONFIG_DIR, CAL_AUTO_WORKING_DAY_START, CAL_AUTO_WORKING_DAY_END, CAL_AUTO_CALENDAR_ID, CAL_AUTO_TASK_LIST_ID, CAL_AUTO_ATTENDEES, CAL_AUTO_SCHEDULABLE_STATUSES, CAL_AUTO_COUNT_ALL_DAY_EVENTS. They go in the env block of your MCP config.