MCP Servers

A remote, GitHub-OAuth-protected MCP server that gives any agent secure read/write access to my Todoist — and quietly logs every tool call so the AI can answer "how much time did you save me?" Two surfaces in one server: a Todoist control plane and an AI-usage observability plane. Live on Cloudflare's edge since September 2025.

Live

Cloudflare Workers

Stack

Cloudflare Workers + Durable Objects + D1 + KV

Auth

GitHub OAuth (per-user approval, not a shared API key)

SDK

@modelcontextprotocol/sdk @cloudflare/workers-oauth-provider

Why it matters

Quantifies the AI's actual impact — every tool call lands in D1 with a configurable time-saved weight, so the server can answer "how much time did you save me this month?" with real numbers. Most MCP servers expose data; this one also measures itself.

A FastMCP server for Madison-area endurance athletes — race discovery, NWS race-day weather, and recurring group rides — wrapped in a /race_prep slash command that resolves fuzzy race references ("madtown half" → the right race) and returns a focused pre-race read: how long you'll be out there, what conditions to expect, and basic nutrition matched to both.

Stack

Python — FastMCP 3.x on Prefect Horizon

Surface

find_races, race_weather, find_group_rides, and the /race_prep prompt

Data

Hand-curated Madison race + group-ride seed (Ironman Wisconsin, Run Madtown, Horribly Hilly, Wisconsin Triathlon Series, Trek Bicycle Madison rides, MadCity Runners…); NWS for inside-7-days forecasts; bundled 30-year NOAA climate normals beyond. Optional RunSignup enrichment when an API key is provided.

Repo

github.com/andywoodruff6/mes-mcp-server

Why it matters

Two design moves I want to be known for: (1) dual-channel weather — the server refuses to invent race-day forecasts beyond NWS's honest 7-day horizon, and falls back to a labeled climate normal rather than confidently presenting next week's weather as race day's. (2) Fuzzy slash-command UX — slash commands that demand UUIDs are a portfolio piece, not a product; resolving "madtown half" server-side is the difference. The piece collapses six websites of Madison endurance planning into one MCP conversation built on FastMCP idioms a Prefect engineer can read in under five minutes.

One MCP server, two domains — a shared context layer my wife and I both pass data through. Household side: shared calendars, home-maintenance reminders, weekend agenda buffer. Food side: pantry inventory, fridge and freezer inventory, weekly meal plan, and an auto-generated shopping list that's just meal plan minus inventory.

The user interface isn't tools, it's slash commands — /plan_week, /weekend_brief, /restock_decision, /maintenance_check — so neither of us has to learn an API to use what's really a shared family operating layer.