For developers

Bring Daylogue into your assistant.The person stays in charge.

Daylogue’s personal MCP reaches the signed-in person’s own Daylogue: journal and mood, daily check-ins, Story, patterns and themes, goals and habits, body and calendar within their permissions, assessments, their own Inner Circle answers, and their Life Map. Every save needs their approval. Someone asks their assistant about last week, and it answers from what they actually wrote.

Server URL

https://daylogue.com/api/mcp

Add it as a custom connector in Claude, ChatGPT, or any MCP client that supports OAuth. The client registers itself, then the person signs in and picks what to share.

How connecting worksSee the tools

Updated October 6, 2026. Implementation reference only. Muse client testing is pending, and that submission is paused.

Tools

Each permission unlocks only its own tools.

A connection lists only the tools its permissions allow. The person can uncheck any permission on the consent screen, and an existing connection never gains a new permission without asking again.

Mood history

read:checkins
  • get_history

    Recorded mood, energy, and stress ratings with dates. Missing ratings stay missing.

  • get_daily_checkin

    Whether the person checked in today, and the ratings they gave, with up to two things they said were coming up so the check-in can ask how they went.

Mood summaries

read:insights
  • get_insights

    Descriptive mood statistics for seven or thirty days. No causes, no forecasts.

Journal text

read:journal
  • get_journal_entries

    Search eligible check-in writing, prompt answers, and your messages in journal conversations with memory on.

  • get_weekly_review

    Seven days of eligible passages and mood statistics. Also needs read:checkins.

  • get_recurring_tags

    Tags you added and accepted that appear on at least two dates. Also needs read:insights and rules-based pattern consent.

Save a mood

write:checkins
  • log_mood

    Saves the 1 to 10 rating the person chose. Never inferred from their words.

  • save_daily_checkin

    Mood, energy, stress, sleep and optional words, after the person approves them. Ratings save on every account; on a device-encrypted account, words wait sealed until the person next opens Daylogue on the web. Words also need write:journal. It can also keep up to two short phrases about what the person said is coming up, for the next check-in to ask about.

  • add_checkin_photos

    A Daylogue link where the person adds up to four photos to their own check-in. Photos never pass through the assistant.

Save writing

write:journal
  • save_journal

    Saves the exact text the person reviewed and approved.

Membership

read:account
  • get_account

    Membership plan and Pro status. No billing details, no other members.

Life Map

read:life_map
  • get_life_map

    The map the person wrote: what matters, what recharges them, and the lines they rate. Watch-outs are not included.

  • get_life_map_checkin

    The lines due on a date, their recharge list, and anything already saved that day.

  • get_life_map_summary

    Week or month averages of their own ratings, their lowest bucket and where they said they go for it. Their own formula only if they wrote one.

  • get_life_map_entries

    Recent check-ins, with notes only when asked.

  • get_life_map_versions

    The last 20 saved versions, with a short outline. Watch-out text is never shown here.

Save to a Life Map

write:life_map
  • save_life_map

    Saves the whole map after the person reviews it and says yes.

  • save_life_map_checkin

    Saves the 1 to 5 ratings the person gave, what centered them, and an optional note.

  • restore_life_map_version

    Brings back an earlier version after the person picks it. The current one goes into history, so it can be undone.

  • set_life_map_reminders

    A notification, email or text at their chosen time. Texts go only to a number they verified in Daylogue; this cannot add or change one.

Watch-outs (off unless ticked)

read:life_map_private / write:life_map_private
  • get_life_map_watchouts

    Their private watch-outs list. Only when they ask.

  • save_life_map_watchouts

    Saves changes they review and approve.

Story

read:story
  • get_story

    One section at a time: chapters, reads, editions, saved weeks, personality over time, what Daylogue has noticed (if switched on), mind map without people, Inbox. Daylogue-written text is labelled.

Patterns and themes

read:patterns
  • get_patterns

    Read between the lines, or the Story page patterns. Counts from the person's own records, not causes.

  • get_pattern_detail

    The days counted and what a pattern is not.

  • get_themes

    Themes and a theme's story. Eating, weight and self-harm themes stay in the app.

Answering patterns

write:patterns
  • review_pattern

    Fits, does not fit, or not sure, bound to the evidence the person saw.

  • review_self_model

    Whether a reading sounds like them.

  • rename_theme

    A new name; the old one is kept as also known as.

Goals, habits, programs, what helped

read:goals / write:goals
  • get_goals

    Goals with progress and milestones, habits, programs, what helped, and days marked as rest or sick.

  • save_goal / update_goal / add_goal_milestone

    Goals in the person's words, progress and status, milestones.

  • log_habit / rate_what_helped / set_life_context

    A habit done, whether an idea helped, a day marked. Pregnancy and postpartum are set only in the app.

Body, calendar, assessments

read:body (off unless ticked) / read:calendar / read:profile
  • get_body

    Device health numbers within the person's health permissions. Not a medical reading.

  • get_calendar

    Event times and meeting sizes, never titles, with calendar patterns on. Work calendars need their own opt-in.

  • get_assessments

    Saved results, never the answers.

Inner Circle

read:circle / write:circle (off unless ticked)
  • get_circle

    Names of people and groups, the person's own answers and shares, and questions waiting. Never anyone else's words.

  • answer_circle_question / answer_group_question

    Answers in the person's approved words. The people involved are told.

Every connection

  • get_capabilities

    What this connection can do, and what needs the app.

  • get_journaling_prompt

    One optional question for today. Reads and saves nothing.

  • get_big_five_questions

    The same 50 Big Five questions Daylogue uses, ten at a time.

  • score_big_five

    Five dimension averages from all 50 answers. Not saved, not a diagnosis.

  • get_membership_options

    A link to membership help. No subscription prices, upgrade offers or checkout.

  • open_daylogue

    A link to finish something in the app. The link alone does nothing.

  • get_life_map_guide

    How to help the person write their own Life Map, one question at a time. Also the daylogue-build-life-map command.

  • Slash commands

    Come with the connector: daylogue-checkin, daylogue-life-map-checkin, daylogue-build-life-map, daylogue-week, daylogue-patterns, daylogue-mind-map, daylogue-goals, daylogue-noticed, daylogue-circle. Use one as a command or a scheduled routine.

Connect

Standard MCP authorization, no setup call.

  1. Discover

    The first unauthenticated request returns HTTP 401 with a WWW-Authenticate header that points to the protected-resource metadata. That names the authorization server.

  2. Register

    Clients register with RFC 7591 dynamic client registration. Redirects must be exact HTTPS URLs, loopback HTTP URLs, or private-use app schemes. Public clients use none; clients that ask for a secret may use client_secret_post or client_secret_basic. Self-registered apps are shown to the person as unverified, with the site they return to. Contact developer support to list a reviewed client with its own logo.

  3. Authorize

    Request response_type=code with PKCE S256, a unique state, and optionally scope and resource=https://daylogue.com/api/mcp. When scope is left out, the consent screen offers every scope the client registered. The person signs in, can uncheck any permission, then allows or declines.

  4. Exchange and refresh

    Exchange the code with grant_type=authorization_code, code_verifier, and the same redirect_uri. The scope in the response is what the person actually granted. Access tokens last one hour. Refresh tokens rotate on every use: store the new one, because presenting a used refresh token disconnects the assistant.

  5. Call tools

    Send Authorization: Bearer <access_token> on every request. The server is stateless and answers with JSON; it does not keep sessions or offer a standalone SSE stream. Never put tokens in URLs or prompts.

Endpoints

MCP server (Streamable HTTP)
https://daylogue.com/api/mcp
Protected-resource metadata
https://daylogue.com/.well-known/oauth-protected-resource/api/mcp
Authorization-server metadata
https://daylogue.com/.well-known/oauth-authorization-server/api/ai-assistant
Client registration
https://daylogue.com/api/ai-assistant/oauth/register
Authorization
https://daylogue.com/api/ai-assistant/oauth/authorize
Token exchange and refresh
https://daylogue.com/api/ai-assistant/oauth/token
Revocation
https://daylogue.com/api/ai-assistant/oauth/revoke

Disconnecting

People disconnect under Settings, Your Data, Connected assistants. A client can revoke its own connection by posting the token and its client ID to the revocation endpoint; clients with a secret authenticate the same way they do at token exchange. Unknown or already-revoked tokens get the same empty success response.

Reads and saves

A partial record, handled with care.

What reads cover

Reads cover a requested window of up to 90 days, scanning at most 500 recent eligible-candidate entries. Passages are capped at 3,000 characters, and coverage fields say what was scanned. This is a partial record, not a complete journal export; archived conversations, conversations with memory disabled, assistant replies, and encrypted writing are not returned.

What never leaves

No AI records, organization-scoped records, encrypted journal text, safety-excluded entries, and other people’s words are omitted. Ratings from encrypted check-ins are included, because Daylogue stores ratings readably for every account. No AI mode, integration settings, and age eligibility can restrict access. Every call rechecks the token, permissions, and account policy before it reads and again before it answers, so a disconnect mid-call returns nothing.

How saves work

Send date, an IANA timezone, a new UUID idempotencyKey, and confirmed:true only after the person approves the exact content. Dates may be up to 90 days back. Journal text is limited to 10,000 characters. Retry an uncertain save with the same key and content; the same key with different content fails, and a deleted entry is never recreated by a retry.

Encrypted accounts

Direct saves require an account explicitly configured without device encryption. Otherwise the tool answers saved:false with a link, and the person unlocks and saves in Daylogue. No plaintext copy is ever written. Writing that needs the separate private-note choice gets the same handoff. The one readable exception is comingUp on save_daily_checkin: up to two short phrases the person approved by saving (for example, conferences Monday), kept until the next check-in asks how it went, or 10 days.

Results and errors

Results arrive in structuredContent.result with a matching text copy. Only saved:true confirms a save; HTTP 200 alone does not. A failed tool call sets isError:true and never includes journal text. Missing or expired tokens get 401, bad input 400 or 413, and too many requests 429.

await client.callTool({
  name: "get_journal_entries",
  arguments: { days: 30, limit: 10, query: "work" }
})

What stays in the app

Voice and media capture, encrypted journal text, share cards and replies, theme merges, edition corrections, privacy changes, exports, deletion, and billing management continue in Daylogue. The MCP does not show subscription prices, promote upgrades, charge a card or create subscriptions; membership help is available in Daylogue.

Older connections

The downloadable desktop extension and its custom SSE endpoint are retired. Use the server URL above. A stdio bridge in the source works for clients that cannot do remote OAuth, but it cannot refresh a token on its own.

Building a client for Daylogue?

Tell us what you are building. We can list a reviewed client with its name and logo, and help you test sign-in and saves.

Email developer support

Daylogue is not therapy and is not a replacement for professional care.