Resources · Claude connector

Claude Roam Research connectorWhat Claude can do in your Roam Research account.

The Claude Roam Research connector exposes 20 tools. 10 read your graph, 9 write to it, and 1 is only half described. Below: what Claude finds, what it edits, how each change gets signed, and what Roam itself says you cannot undo.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when Claude can work in your graph

Roam is great at capturing and terrible at resurfacing. You know you wrote something about a supplier in March, but not on which page or under which block. With the connector, you ask Claude and it digs through pages, blocks, daily notes, comments and backlinks itself, then brings back what you wrote, in your own words.

Find the thread you lost. search and get_backlinks surface every block that mentions a person or project. For harder questions, roam_query and datalog_query run structured queries across the graph.

Capture without switching apps. You finish a call, dictate three takeaways, and append_to_daily_note drops them on today's page. create_page starts a clean page from markdown when the topic deserves its own home.

Tidy up a messy outline. move_block, update_block and delete_block reorganize a page you let drift, and every change shows up under a separate (AI) author so you can review it.

Now the part the directory sheet plays down. Roam's own documentation warns that changes made this way can be hard or impossible to reverse, since there is no classic undo for bulk edits or deletions. Hiding a block from Claude with a tag is a convenience, not a lock: the raw query tool skips that filter. And nothing runs on its own. No tool fires when you add a page or tick a TODO; for that kind of background job, look at an automation tool instead, a different trade, from our Integrations hub. Other apps get the same breakdown, for example the Claude airtable connector.

Vocabulary

Five words before you plug it in

The vocabulary you will meet along the way.

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
Tool
One named job the connector opens to Claude. Claude picks the ones it needs mid-answer; the directory sheet lists them by name.
Authorization
Roam's own sign-in screen, where you hand Claude the access it will use afterwards. Given once per person, and you can take it back.
Approval
The confirmation Claude waits for before doing something that changes an account, shown in the conversation when it matters.
MCP
The shared standard connectors run on: it is what lets an assistant like Claude talk to an outside service such as Roam.
Connect

Connect Roam Research to Claude in three steps

  1. 01

    Find Roam Research in Claude

    In Claude's settings, open Customize, then Connectors, and find Roam Research. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first; then each member connects separately.

  2. 02

    Start the connection

    Click Connect on its row and sign in to Roam in the window Roam opens itself, with your usual account. If the link breaks later, hit Disconnect and connect again from scratch.

  3. 03

    Check the authorization screen

    Read the screen before you accept. It belongs to Roam, not Claude, and it sets what the access covers. You can take that access back later from the Roam side as well.

Tools

The 20 tools of the Claude Roam Research connector

Roam Research gives Claude 20 tools: 10 that read your account, 9 that change something in it, and 1 no official source describes.

Three groups: what Claude reads, what it changes, and one tool the sources leave unclear. Names stay as Claude shows them, in English.

  • 10 read
  • 9 write
  • 1 not documented

What Claude reads (10)

10 tools

Ten tools that look through your graph without touching it.

datalog_query

Runs a raw Datalog query straight against the graph's database, for questions the ordinary search cannot express.

When it helps
you want every block created in a date range that references two pages at once.
Watch out
Roam says this tool skips the hidden-block filter, so blocks tagged to stay out of the AI's reach can still surface.

Sourcegithub.com · September 30, 2026 ↗

get_block

Returns one block's content as markdown, ready for Claude to quote or summarize.

When it helps
Claude found a relevant reference and needs the exact wording of that block.
Watch out
a block tagged to hide from the AI, and everything nested under it, is skipped.

Sourcegithub.com · September 30, 2026 ↗

get_comments

Fetches the comments on a block, each with its author and date, so Claude sees the discussion and not just the text.

When it helps
you want to know who questioned a decision and when.
Watch out
it reads one block's thread at a time.

Sourcegithub.com · September 30, 2026 ↗

get_graph_guidelines

Loads the instructions and preferences you recorded for AI agents in that graph. Per the directory sheet, Claude reads them when it starts working in a graph.

When it helps
your team has naming conventions and a set page structure that Claude should respect.
Watch out
these guidelines come from you, so a graph with thin guidelines gives Claude little to go on.

Sourcegithub.com · September 30, 2026 ↗

get_page

Returns the content of a page as markdown, so Claude can read and summarize it.

When it helps
you want a summary of your research page on a competitor before a pitch.
Watch out
hidden subtrees stay out of the result.

Sourcegithub.com · September 30, 2026 ↗

list_graphs

Shows the graphs configured for the connection, with their nicknames, so Claude knows where it may look.

When it helps
you keep a personal graph and a team graph and want to point Claude at the right one.
Watch out
Claude only sees the graphs you picked when you connected.

Sourcegithub.com · September 30, 2026 ↗

roam_query

Runs a Roam query across the graph, the structured option that sits next to the separate raw Datalog tool.

When it helps
you want all open TODOs tagged with a given project.
Watch out
unlike the raw Datalog tool, this one respects the hidden-block filter.

Sourcegithub.com · September 30, 2026 ↗

search_templates

Looks up Roam templates by name so Claude can reuse the structure your team already set.

When it helps
you want a meeting note built on your usual template.
Watch out
template previews are not filtered, so hidden blocks inside a shared template can appear.

Sourcegithub.com · September 30, 2026 ↗

What Claude changes (9)

9 tools

Nine tools that alter pages, blocks or comments. No source describes a confirmation for any of them: the general rule below applies.

add_comment

Approval: see the rule

Attaches a comment to a block as a discussion thread, kept apart from the block's children, so the outline itself stays as it was.

What Claude asks for
Roam's documentation is silent on any prompt before a comment gets posted, which leaves the general approval rule in charge.
When it helps
you want Claude to flag a doubtful figure in a teammate's notes without rewriting them.
Watch out
like any edit, it shows up under the separate (AI) author.

Sourcegithub.com · September 30, 2026 ↗

append_to_daily_note

Approval: see the rule

Captures markdown at the end of a daily note, which is the fastest way to log something without deciding where it belongs yet.

What Claude asks for
nothing published describes a check before the capture lands on the page; the default rule below decides.
When it helps
right after a call, you dictate three takeaways and want them on today's page.
Watch out
on an encrypted graph, the directory sheet only mentions appending or capturing, nothing broader.

Sourcegithub.com · September 30, 2026 ↗

create_block

Approval: see the rule

Adds new blocks under a parent block, on a page named by its title, or on the daily note of a given date.

What Claude asks for
whether a confirmation shows up before new blocks appear is not documented, so fall back on the general rule.
When it helps
you ask for a checklist of next steps under the project block you are looking at.
Watch out
per the directory sheet, Claude follows the graph's guidelines so new blocks match your naming and page structure.

Sourcegithub.com · September 30, 2026 ↗

create_page

Approval: see the rule

Opens a new page in the graph and fills it with markdown content in one go.

What Claude asks for
no text from Roam or Anthropic covers a confirmation for new pages; the section on approvals applies.
When it helps
a recurring topic has outgrown the daily notes and deserves a page of its own.
Watch out
check the graph for a page with a similar title first, so you do not end up with two.

Sourcegithub.com · September 30, 2026 ↗

delete_block

Approval: see the rule

Removes a block from the graph when it no longer earns its place in the outline.

What Claude asks for
no source says Claude pauses before this particular deletion, so the general rule is your only safeguard here.
When it helps
a duplicate block keeps showing up in search results and you want it gone.
Watch out
Roam warns that deletions made this way can be hard or impossible to undo.

Sourcegithub.com · September 30, 2026 ↗

delete_page

Approval: see the rule

Removes a whole page from the graph.

What Claude asks for
a confirmation specific to deleting pages is described nowhere; count on the default rule and read the request before you accept.
When it helps
a test page from last year still clutters your search results.
Watch out
Roam has no classic undo history for deletions made this way, so think twice before confirming.

Sourcegithub.com · September 30, 2026 ↗

move_block

Approval: see the rule

Relocates a block elsewhere in the graph, under another parent or on another page.

What Claude asks for
the sources do not describe a prompt tied to moves; the general approval rule covers them.
When it helps
a note filed under the wrong project needs to sit with the right one.
Watch out
Roam warns that bulk operations made this way are hard to reverse, so move one block at a time when in doubt.

Sourcegithub.com · September 30, 2026 ↗

update_block

Approval: see the rule

Rewrites a block's content or properties in place.

What Claude asks for
Roam publishes nothing about a confirmation before a block is rewritten, so the rule further down applies.
When it helps
a figure in last week's notes turned out wrong and you want the block corrected.
Watch out
the edit appears under the (AI) author, which makes it easy to find and review.

Sourcegithub.com · September 30, 2026 ↗

update_page

Approval: see the rule

Renames a page or changes how its children are displayed.

What Claude asks for
no documented prompt belongs to this tool alone; renames go through the general approval rule.
When it helps
a project changed its name and the page title should follow.
Watch out
the change is signed by the (AI) author, so a teammate who cannot find the old title can trace what happened.

Sourcegithub.com · September 30, 2026 ↗

Unclear (1)

1 tool

Roam gives this tool one line, and that line does not say whether it changes anything in your account. We will not guess.

setup_new_graph

Roam's documentation gives this tool a single line: it sets up a new graph connection or lists the graphs available. No source says whether it touches anything in your account beyond that, so the page does not guess.

Watch out
whatever it does, the general approval rule covers it.
Approvals

What Claude asks before acting

By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. The request shows up in the conversation, when it matters.

On Team and Enterprise workspaces, owners decide whether a member may let certain actions through without being asked each time. They can also cap what a connector may do for the whole organization, keeping reading open and closing writing, and nobody bypasses that from their own account. Claude works with your rights and nothing more. Roam adds two controls of its own: the access level you give each graph, and the (AI) author that signs every change Claude makes.

Plans

Which plans include it

Of the 819 sheets in the official directory, none shows availability by plan. The per-connector answer is published nowhere, a real gap in the catalogue.

The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members can connect. For the current state, open the Roam Research sheet in the directory from your own account.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you; nothing starts when a page is added or a block changes.

This connector is documented only by its publisher: no page on Claude's help center or in Anthropic's developer docs covers it. The tool list is an observed floor, not a promise, since an administrator can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic states on every sheet that it does not choose the tools a publisher exposes. Plug in publishers you trust, here Roam itself.

Need help

Need help connecting Roam Research to Claude?

A person reads every message.

FAQ

FAQ on the Claude Roam Research connector

01What can Claude do with the Roam Research connector?
Claude can read, search and edit the Roam graphs you connect. On the reading side, it opens pages and blocks, follows backlinks, reads comments, loads your graph guidelines and runs Roam or Datalog queries. On the writing side, it creates pages and blocks, appends to the daily note, moves, updates or deletes blocks, updates or deletes pages and adds comments. One more tool, for setting up a graph connection, is described too briefly to classify.
02Can Claude write, change or delete things in my graph?
Yes, nine of the twenty tools change your graph. Claude can create pages and blocks, append to a daily note, update, move or delete blocks, rename or delete pages, and add comments. Roam signs each of these changes with a separate (AI) author. Its documentation also warns that edits and deletions made this way can be hard or impossible to undo, because there is no classic undo history for them.
03Does Claude ask before it changes my notes?
By default, yes: Claude asks for confirmation before each action it takes on an account for you. No source describes a confirmation specific to any Roam tool, so that default rule covers every write. On Team and Enterprise, owners decide whether members can let some actions through without being asked, and they can close writing for the whole organization. On the Roam side, a read-only access level on a graph blocks writes there.
04Which plans is it available on?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule opens remote connectors to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner must enable the connector before members can connect. The Roam Research sheet in the directory, opened from your own account, is the only place that shows the current state.
05Does Claude see all of my Roam graphs?
No. Claude only works in the graphs you picked when connecting, at the access level you set for each, and always within the rights of your Roam account. You can change a graph's access or disconnect it at any time. Inside a graph, blocks tagged to stay hidden from the AI are skipped by most reading tools, although Roam warns that the raw Datalog query does not apply that filter.
06Can I undo what Claude did in Roam?
Not reliably. Roam's documentation says changes made through its API may be difficult or impossible to undo, since there is no traditional undo history for bulk operations or deletions. What you do get is traceability: every change Claude makes is attributed to a separate (AI) author, so you can find it and fix it by hand. Before a big clean-up, a read-only pass first is the careful route, and so is setting the graph's access level to match the job.
07Claude or an automation tool for Roam Research?
They do different jobs, so choose by the task. Claude works inside a conversation: you ask, it searches, sums up or edits, and nothing moves once you stop typing. It does not react on its own when a page appears or a TODO gets done. For a job that runs in the background on an event, that is the role of an automation tool. For on-demand digging and tidying in your notes, the connector fits.