- Home
- Resources
- Integrations
- Roam Research
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
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.
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 Roam Research to Claude in three steps
- 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.
- 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.
- 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.
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
Tools index
What Claude reads (10)
10 toolsTen 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.
get_backlinks
Lists the references pointing to a page or a block, which is Roam's way of answering where else something came up.
get_block
Returns one block's content as markdown, ready for Claude to quote or summarize.
get_comments
Fetches the comments on a block, each with its author and date, so Claude sees the discussion and not just the text.
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.
get_page
Returns the content of a page as markdown, so Claude can read and summarize it.
list_graphs
Shows the graphs configured for the connection, with their nicknames, so Claude knows where it may look.
roam_query
Runs a Roam query across the graph, the structured option that sits next to the separate raw Datalog tool.
search
Searches pages and blocks by text across the whole graph, the quickest way in when you only remember a few words.
search_templates
Looks up Roam templates by name so Claude can reuse the structure your team already set.
What Claude changes (9)
9 toolsNine 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 ruleAttaches a comment to a block as a discussion thread, kept apart from the block's children, so the outline itself stays as it was.
append_to_daily_note
Approval: see the ruleCaptures markdown at the end of a daily note, which is the fastest way to log something without deciding where it belongs yet.
create_block
Approval: see the ruleAdds new blocks under a parent block, on a page named by its title, or on the daily note of a given date.
create_page
Approval: see the ruleOpens a new page in the graph and fills it with markdown content in one go.
delete_block
Approval: see the ruleRemoves a block from the graph when it no longer earns its place in the outline.
delete_page
Approval: see the ruleRemoves a whole page from the graph.
move_block
Approval: see the ruleRelocates a block elsewhere in the graph, under another parent or on another page.
update_block
Approval: see the ruleRewrites a block's content or properties in place.
update_page
Approval: see the ruleRenames a page or changes how its children are displayed.
Unclear (1)
1 toolRoam 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.
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.
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.
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 connecting Roam Research to Claude?
A person reads every message.

