Moncha Connect

Connect

Give an AI agent read and write access to your Moncha data — the same access you already have in the app, nothing more, revocable any time.

Two ways in, same 19 capabilities either way: an API key for any HTTP client, or MCP for an MCP-native agent.

Create an API key Connect via MCP

How it works — API key

Three steps, no separate app to install

Using an MCP client instead? Skip ahead to MCP — different steps, same capabilities.

1

Create a key

Sign in on the account page and generate a key — shown once, in full.

2

Give it to your agent

Any HTTP client that can send a Bearer token.

3

It calls Connect

Your agent reads and writes Memories on your behalf, over plain HTTPS.

What it can do

Built around what you'd ask it to do, not around a database table

Every route is named for the intention behind it — "remember this," "what's due today" — so a thin, one-tool-per-route wrapper needs no logic of its own to translate between the two.

Capture

Remember a note, a link, or a task — with a due date, a space, and who or where it's about.

Find & check what's due

Search by text or tag, or ask what's due today, this week, or overdue.

Organize

Tag people and places, edit a title or note, set or stop a repeating reminder.

Track progress

Mark something done, reopen it, or read one Memory back by id.

Trust

A key acts as you, nothing else

Reference — API key

Endpoints

Full request/response shapes live in the OpenAPI document linked below — this is the tour, not a copy of the contract.

Base URL
https://connect.getmoncha.app/connect/v1 Authorization: Bearer mm_live_<your key>

Identity

GET/whoamiConfirm this key, resolve the user it belongs to, and get a date anchor for "today."

Memories

POST/rememberCapture a Memory — resolves its own space by name, no id lookup required.
GET/findFind Memories by text, tag, status, or due date, optionally scoped to one space.
GET/agendaWhat's due — today, this week, or overdue.
GET/memories/{id}Read one Memory by id.
PATCH/memories/{id}Edit a title, note, or due date/time — a true partial update.
POST/memories/{id}/tagAdd people, place, or topic tags — merges into what's already there.
POST/memories/{id}/untagRemove people, place, or topic tags by label match.
POST/memories/{id}/repeatSet or replace a recurrence rule.
POST/memories/{id}/doneMark a Memory done.
POST/memories/{id}/reopenMark a done Memory pending again.
POST/memories/{id}/stop_repeatingEnd a recurring series — this instance stays, no more get generated.
POST/memories/{id}/linkLink a Memory as part_of or related to another.
POST/memories/{id}/unlinkRemove a link between two Memories.
POST/memories/{id}/archiveArchive a Memory — reversible, leaves status/completion untouched.
POST/memories/{id}/unarchiveReverse archive on a Memory.
POST/memories/{id}/moveMove a Memory to another Space by name — creator only.
POST/memories/{id}/visibilityMake a Memory private or shared — creator only.

Spaces

GET/spacesList every space you actively belong to, including Personal.
POST/spacesCreate a new shared space — icon required, one of the fixed palette.
PATCH/spaces/{id}Rename a space and/or change its icon — owner-only.

Full request/response schemas, error codes, and pagination details: the full reference — or grab the raw OpenAPI document to import into Postman, an MCP client, or any spec-driven tool.

MCP

Or connect an MCP client directly

Same 19 capabilities as the reference above, exposed as MCP tools — for an MCP client instead of raw HTTP.

MCP endpoint
https://connect.getmoncha.app/mcp OAuth 2.1 — not the API key above

If your client supports the 2026-07-28 MCP spec, it discovers and authorizes automatically — no manual registration. Older clients: see the OAuth reference below.

Full contract: the MCP OpenAPI document · the OAuth 2.1 document