morgen-mcp

An MCP server that connects your Morgen calendar to any MCP-compatible AI client.

---

The idea

Calendar apps give you the technical skeleton of your day; what you did and when. Physical journals capture the feeling of it. This tool lives in between.

morgen-mcp exposes your Morgen schedule as tools that your AI client can call. At the end of the day, start a conversation: the AI fetches your events, reads your existing notes for context, asks you a couple of short questions, and writes something that reads like a real diary and not a meeting log.

Pair it with mcp-obsidian and the entry lands directly in your Obsidian daily note. No extra subscriptions, no extra API keys. Works with whatever AI client you already use.

---

How it works

morgen-mcp is an MCP (Model Context Protocol) server. It exposes 3 tools:

Tool	Description
get_events	Fetch events for a given date across selected calendars
list_accounts	List connected Morgen accounts and their IDs
list_calendars	List calendars under an account

The AI client calls these tools to get your schedule. Writing the diary entry and saving it is up to the client and whatever other MCP tools you have connected.

---

Requirements

• Python 3.14+
• uv
• A Morgen account - get your API key at platform.morgen.so
• Any MCP-compatible client (Claude Desktop, Cursor, Windsurf, etc.)

---

Setup

git clone https://github.com/batoorsayed/morgen-mcp
cd morgen-mcp
uv sync

1. Get your Morgen API key

Go to platform.morgen.so > Developers > API Keys.

2. Configure environment

cp .env.example .env
# Add your API key to .env

Then run this to fetch your account IDs and get a ready-to-paste env line:

uv run morgen-mcp --list-accounts

It will print something like:

Accounts:
  abc123def456  Your Name  [icloud]
  xyz789ghi012  Your Name  [google]
  ...

Add to your .env:
  MORGEN_ACCOUNT_ID=abc123def456,xyz789ghi012,...

It also prints a suggested CLAUDE.md snippet you can paste into your project instructions.

Copy the env line into your .env. Include only the accounts whose events you want. See the rate limits note below.

3. Register with your MCP client

Claude Code : Run this from inside the cloned directory:

claude mcp add --scope user morgen-mcp -- uv --directory $(pwd) run morgen-mcp

Run once. Available across all projects. Credentials are picked up from .env automatically.

Other clients (Claude Desktop, Cursor, Windsurf, etc.) : Add to your client's MCP config file, replacing /path/to/morgen-mcp with the actual path to your clone. Most clients expand $VAR references from your shell environment. If yours doesn't, paste the actual values directly.

{
  "mcpServers": {
    "morgen-mcp": {
      "command": "uv",
      "args": ["--directory", "/path/to/morgen-mcp", "run", "morgen-mcp"],
      "env": {
        "MORGEN_API_KEY": "$MORGEN_API_KEY",
        "MORGEN_ACCOUNT_ID": "$MORGEN_ACCOUNT_ID"
      }
    }
  }
}

---

Usage

Just talk to your AI client:

"Write my diary entry for today"
"What did I have on my calendar yesterday?"
"Summarize my week"

The end-of-day ritual

At the end of the day, open your AI client and say something like "write today's diary entry". From there:

1. The AI fetches your events for the day via get_events
2. It checks whether today's Obsidian daily note (YYYY-MM-DD.md) exists, and creates it if not
3. It reads your morning note and any recent notes you've flagged, to enrich the context
4. It asks you 2–3 short questions: things the calendar can't tell it (what was hard, what surprised you, what's worth remembering)
5. It writes a personal diary entry and appends it under a ### End of Day heading

This workflow requires both morgen-mcp (calendar) and mcp-obsidian (notes) connected to your client. morgen-mcp only handles the events fetch. The AI orchestrates the rest using both MCPs and the system prompt below. Credit to bitbonsai for mcp-obsidian.

System prompt: Add this to your client's project instructions:

When I ask for a diary entry:
1. Fetch my Morgen events for that day using get_events
2. Check if today's Obsidian daily note (YYYY-MM-DD.md) exists — if not, create it
3. Read today's note and any notes I've flagged as important from the past few days
4. Ask me 2-3 short questions to capture what the calendar doesn't show
5. Write a personal diary entry — human, not a bullet list — weaving the events and my answers together
6. Append it to my daily note under a "### End of Day" heading

---

Output example

### End of Day

Morning focus block finally broke the deadlock on the data layer —
that one took longer than it should have but shipping it felt like
putting down something heavy. Three back-to-back meetings killed the
afternoon momentum. The kind of day where you do more than it felt like.

---

Rate limits

The Morgen API allows 100 points per 15-minute window. Each /list call (calendars, events) costs 10 points.

get_events makes one calendars fetch plus one events fetch per configured account. With 6 accounts that's 70 points, leaving 30 to spare. Fine for a diary tool used a few times a day, but avoid calling it in rapid succession.

If you hit a 429, wait a few minutes and try again.

---

Privacy

Event data is fetched from Morgen and passed to your AI client for processing. No data is stored or sent anywhere else. Your AI client's own privacy policy applies to how it handles that data.

---

Contributing

Small tool, open door. PRs welcome — keep it simple.

---

License

MIT