Skip to content

Daily Agent MCP

Self-hosted productivity data layer for OpenClaw. Postgres behind a typed MCP interface, plus a Next.js dashboard that reads and edits the same database. Single-user, Tailscale-gated.

Not a chatbot

This project is not an AI product. It's a durable store for tasks, habits, journal, workouts, focus sessions, goals, and spaces — exposed to your agent over MCP and to your browser over HTTP. All generative AI (briefings, reviews, insights) lives in OpenClaw.

The shape of it

Two front doors, one database.

flowchart TD
    OC[OpenClaw agent] -->|/api/mcp + Bearer| MCP["/api/mcp<br/>MCP server"]
    UI[Browser dashboard] -->|"/tasks, /habits, ..."| API[Next.js API routes]
    MCP -->|Drizzle| DB[(Postgres)]
    API -->|Drizzle| DB
  • MCP server (/api/mcp) — the agent's interface. 34 typed tools for reading and writing every piece of productivity data, 13 prompt templates, plus read-only resources. Bearer-token authenticated.
  • Dashboard — a Next.js UI for browsing and manually editing the same data. No AI features. No generate buttons. Just CRUD.

OpenClaw owns model choice, scheduling, message delivery (Telegram / WhatsApp / etc.), briefings, insights, and reviews. This repo owns storage and the contract.

Who this is for

You if:

  • You're already running OpenClaw (or a similar agent) and want it to stop writing data into a pile of markdown templates and scripts.
  • You want your productivity data in one Postgres database you control, not scattered across a dozen services.
  • You're comfortable running Docker + Compose on a VPS and putting it behind Tailscale.
  • You want a simple browser UI to poke at the data without opening a SQL shell.

Where to go next

  • Quick start

    Download docker-compose.example.yml, fill three env vars, docker compose up -d. Works on any Docker host.

    Install in 5 minutes

  • Updating

    docker compose pull && docker compose up -d. Migrations run automatically.

    See quick-start

  • Build from source

    For contributors who want to build the image locally instead of pulling from GHCR.

    Deploy from source

  • MCP reference

    34 tools, grouped by domain, with input schemas and examples.

    Browse tools

  • OpenClaw integration

    The skill file OpenClaw needs, plus usage patterns.

    Skill setup

  • Architecture

    Request flow, auth layers, data model, where validation happens.

    Under the hood

  • Troubleshooting

    401s, connection refused, port conflicts, MCP schema errors.

    Fix it

License

Apache 2.0. Modify and self-host freely.