For developers & agents

Build on your family's Plannie.

Point Claude - or any agent - at your household over MCP, or build on the open REST API. One scoped key, one pasted config, about ten minutes.

Plannie is a shared family organiser with a first-class agent surface: a hosted MCP server and an open REST API, scoped by household, attributed by name, and revocable at any time - not a bolt-on integration.

Create a key

In Plannie, open Settings → Integrations and create an API key. Pick exactly the scopes your agent should have - calendar only, lists only, whatever feels right.

Point your agent at it

Paste one small config into your MCP client, or call the REST API directly. No SDK, no OAuth dance - the key is the whole handshake.

Watch it show up

Everything an agent adds appears in the family calendar with a sparkle badge and an activity-feed entry, attributed by name. The whole household sees what was done, and by whom.

CONNECT

Pick your tool

One command or one click for the popular agents - all of them talk to the same hosted MCP server. The REST API is there when you'd rather build it yourself.

Stays right here in your browser - it's only written into the snippets and buttons below.

claude mcp add --transport http plannie https://api.plannie.io/mcp \
  --header "Authorization: Bearer fam_live_…"

One command in your terminal. Add --scope user to make Plannie available in every project, then check with /mcp.

{
  "mcpServers": {
    "plannie": {
      "command": "npx",
      "args": ["-y", "@plannie/mcp"],
      "env": {
        "PLANNIE_API_URL": "https://api.plannie.io/v1",
        "PLANNIE_API_KEY": "fam_live_…"
      }
    }
  }
}

Drop into claude_desktop_config.json (Claude Desktop → Settings → Developer → Edit config). npx fetches @plannie/mcp on first run - no install step.

{
  "mcpServers": {
    "plannie": {
      "url": "https://api.plannie.io/mcp",
      "headers": { "Authorization": "Bearer fam_live_…" }
    }
  }
}

Add to Cursoror paste into ~/.cursor/mcp.json - global, or per-project in .cursor/mcp.json.

code --add-mcp '{"name":"plannie","type":"http","url":"https://api.plannie.io/mcp","headers":{"Authorization":"Bearer fam_live_…"}}'

Install in VS Codeor run the command above, or add the server to .vscode/mcp.json.

codex mcp add plannie \
  --env PLANNIE_API_URL=https://api.plannie.io/v1 \
  --env PLANNIE_API_KEY=fam_live_… \
  -- npx -y @plannie/mcp

Registers the local @plannie/mcp bridge with Codex CLI - it lands in ~/.codex/config.toml.

curl "https://api.plannie.io/v1/events?from=2026-08-24&to=2026-08-30" \
  -H "Authorization: Bearer fam_live_…"

Plain REST under /v1 - JSON in, JSON out, scoped by your key. The full contract lives in the live API reference.

Different client, or want the details? The API reference has the full per-client walkthrough under "Connect an agent".

TOOLS

What your agent can do

Sixteen tools cover the family's week - events, tasks, lists, meals, members and the activity feed. Each one maps straight onto the REST API, so what MCP can do, your own code can too.

list_eventscreate_eventupdate_eventdelete_eventlist_taskscreate_taskcomplete_taskget_listsadd_list_itemcheck_list_itemget_meal_planset_mealremove_meallist_recipesget_membersget_activity

SCOPES

Keys that only open one door

Every key is scoped at creation and can expire on a date you choose. A hallway dashboard gets calendar.read and nothing else; revoke any key any time from Settings → Integrations.

calendar.readcalendar.writetasks.readtasks.writelists.readlists.writemeals.readmeals.writechores.readcheckins.readcheckins.writeactivity.read

FOR AGENTS

Self-describing, on purpose

If you're an agent reading this: everything below is machine-readable, generated from the running API, and enough to connect without a human in the loop - except for the key, which a household member creates for you.

OpenAPI spec https://api.plannie.io/openapi.json every endpoint, schema and error, generated from the running API
API reference https://api.plannie.io/docs the same spec, browsable by humans
Hosted MCP https://api.plannie.io/mcp streamable HTTP · Bearer fam_live_… key
llms.txt https://plannie.io/llms.txt this page, condensed for agents

Developer & agent questions

Can AI agents connect to Plannie, and with which scopes?+

Yes - any MCP client or REST caller can connect with a scoped API key a household member creates under Settings → Integrations. Scopes are granted per key (calendar-only, lists-only, whatever the agent needs) and can expire on a chosen date.

Which plan includes API and MCP access?+

The Premium + MCP plan - see pricing for the current price. It includes everything in Plannie Premium plus the open API and the hosted MCP server for your own agents, automations and integrations.

Is agent activity visible to the family?+

Always. Every event, task or list item an agent creates carries a sparkle badge in the app and a named entry in the household's activity feed - nothing an agent does is invisible to the people who share the household.

The full reference

Every endpoint, request shape and error code - served live by the API itself, always in sync with what's deployed.

Open the API reference

API & MCP access is part of the Premium + MCP plan - and included in every trial.