Integration

Reflect integration

Reflect Classic is the end-to-end encrypted note-taking app at reflect.app, organised in graphs (one per workspace); this API needs a Reflect Classic account. An agent can list the user's graphs, append text to a daily note (optionally under a named list), create a note from Markdown, save a bookmarked link and list the saved links, and list the Kindle books synced into a graph with their highlights and notes. Every write changes the user's real Reflect graph. Existing note contents cannot be read back or edited: notes are encrypted, so the API only appends. It does not reach Reflect Open, the newer app that keeps notes as local Markdown files: writes stay in the Classic account and do not sync there. Authentication is a Reflect access token sent as a Bearer token: create OAuth credentials at reflect.app/developer/oauth and generate an access token there (Reflect describes it as equivalent to an API key).

Connect Reflect How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Reflect.Built from the 7 Reflect tools below, on the connection you add once.

What you can do with Reflect

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Link, 2 operations

create_linkCreate linkPOSTSaves a web link as a bookmark in the user's graph, with an optional title, description and highlights, and returns the stored link with its id. The API offers no way to edit or delete it.
list_linksList linksGETLists the web links the user bookmarked in a graph, each with its URL, title, description, saved highlights and last update time (personal content). Note contents are not returned.

Book, 1 operation

list_booksList booksGETLists the books Reflect's Kindle sync imported into a graph, each with its Amazon ASIN, title, authors and the highlights and notes the user took while reading (personal content).

Daily note, 1 operation

append_to_daily_noteAppend to daily notePUTAppends text to the user's real daily note in a graph for a date (today by default), at the end of the named list when list_name is given. The API cannot edit or remove it afterwards, and earlier note content is never returned.

Graph, 1 operation

list_graphsList graphsGETLists the Reflect graphs (note workspaces) the access token can reach, each with its id and name. The id is the graphId every other tool takes.

Me, 1 operation

get_current_userGet current userGETReturns the Reflect account the access token belongs to: its uid, email and name (the user's personal data) and the ids of the graphs it can use (the graphId the other tools take).

Note, 1 operation

create_noteCreate notePOSTCreates a real note in the user's graph from a subject and Markdown content, optionally pinned, and returns its id and timestamps. The API cannot read, edit or delete the note afterwards.

Use Reflect from Claude Code, Cursor or Codex

Connect Reflect in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Reflect operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Reflect

Create your workspace
Sign up free. Nothing to install.
Connect Reflect once
Add your Reflect connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.