Cal2prompt MCP Server

Cal2prompt mcp server connects Cal2prompt to AI assistants that speak the Model Context Protocol. cal2prompt is a command-line tool that fetches your schedule (e.g., from Google Calendar) and converts it into a custom prompt or text snippet via a template engine. It can output directly to your stdout, or run as an experimental MCP (Model Context Protocol) server.

What Cal2prompt does

cal2prompt is a command-line tool that fetches your schedule (e.g., from Google Calendar) and converts it into a custom prompt or text snippet via a template engine. It can output directly to your stdout, or run as an experimental MCP (Model Context Protocol) server.

Key capabilities

• 🚀 Google Calendar Integration
• 📄 Flexible LLM Prompt Customization with a Template Engine
• ⚡️ Blazing fast
• 🔧 Experimental MCP Mode

Installing the cal2prompt mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

The server reads one environment variable: CAL2_PROMPT_CONFIG_FILE_PATH. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Productivity servers pay off through capture: the tasks and notes that never get filed are the ones where opening the app is more friction than the thought is worth. Cal2prompt sits in that group. Worth comparing against the other productivity servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• Maintained by shuntaka9576.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the cal2prompt mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.