Developers

Build on WeeklyPlanner

Use the public API for tasks, groups, preferences, profile, and automation flows. The MCP server follows the same API surface.

Create an accountLog in/settings

REST API

Task, group, profile, settings, stats, and API key endpoints live under /api/v1.

API Keys & Scopes

Create API keys from account settings and limit them to the scopes your integration actually needs.

MCP Server

A dedicated MCP server already exists in the repository and talks to the same task and settings APIs.

Security

Supabase Auth protects the app. API key verification, scopes, and rate limits share the main API entry path.

Quickstart

1. Create an account

Sign up first, then open Settings to manage your account-level developer access.

2. Create an API key

Generate a key in Settings, choose only the scopes you need, and store it immediately. The plain key is shown once.

3. Call the API or MCP

Send the key as a Bearer token. MCP requests also set X-WeeklyPlanner-Source: mcp.

Examples

Read tasks

curl -X GET "https://weeklyplanner.cc/api/v1/tasks?date_from=2026-03-01&date_to=2026-03-31" \
  -H "Authorization: Bearer wp_your_api_key" \
  -H "Content-Type: application/json"

Create a task

curl -X POST "https://weeklyplanner.cc/api/v1/tasks" \
  -H "Authorization: Bearer wp_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Prepare weekly review",
    "date": "2026-03-20",
    "time_block": "evening",
    "priority": "high"
  }'

MCP environment

WEEKLYPLANNER_API_URL=https://weeklyplanner.cc
WEEKLYPLANNER_API_KEY=wp_your_api_key

Available scopes

Grant the smallest scope set possible for each integration.

tasks:readtasks:writegroups:readgroups:writestats:readsettings:readsettings:writeprofile:readprofile:write

Core endpoints

Tasks

List, create, update, delete, batch update, and reorder task positions.

Groups

Manage group names, colors, ordering, and group-aware task moves.

Settings & Profile

Read and update view preferences, locale, ADHD mode, and personal profile fields.

Stats

Read aggregate usage and planning statistics for dashboards or assistant workflows.

Reference docs and copy-paste examples will keep expanding. Billing already runs through Creem inside the product, but public developer endpoints still focus on tasks, settings, stats, and API keys.

PrivacyTermsRefunds