BrainGraph for AI agents
BrainGraph builds a searchable knowledge graph from documents, recordings, and web pages that teams use to ground AI answers in their own source material. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in BrainGraph.
Search the knowledge graph
Run a read-only search across a brain's ingested documents and graph patterns to answer a question.
Ingest a new source document
Upload a document or ingest a web page or video into a brain after the user approves the source.
Check ingestion progress
Look up a document's ingestion progress before relying on it as the basis for a search.
10 BrainGraph actions, graded by risk.
Every BrainGraph action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- braingraph.list_brainsList Brains
- braingraph.search_brainSearch Brain
- braingraph.list_patternsList Graph Patterns
- braingraph.list_documentsList Documents
- braingraph.get_document_progressGet Document Progress
- braingraph.resolve_entityResolve Entity
write
4Create and change things. Allow, or ask the user first.
- braingraph.ingest_web_pageIngest Web Page
- braingraph.upload_documentUpload Document
- braingraph.transcribe_audioTranscribe Audio
- braingraph.ingest_youtube_videoIngest YouTube Video
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
BrainGraph in three steps.
- 01Your users connect BrainGraphThey add their BrainGraph api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “ingest Web Page” can wait for the user to approve.
- 03Any agent can actYour agent calls BrainGraph through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('braingraph', { read: 'allow', write: 'ask', // ingest_web_page destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How BrainGraph connects.
Users add their BrainGraph api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same BrainGraph connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use BrainGraph from any agent.
BrainGraph and Arc0, answered.
Can I use BrainGraph with Claude, ChatGPT or Cursor?
Yes. Connect BrainGraph to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the BrainGraph actions you allow.
How do users connect BrainGraph?
Users add their BrainGraph api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which BrainGraph actions can my agent take?
10 in total: 6 read, 4 write and 0 destructive, such as “ingest Web Page”. Your policies decide which of them each agent may call.
Can I make my agent read-only in BrainGraph?
Yes. Allow read actions and deny writes in the BrainGraph policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call BrainGraph too?
Yes. The same BrainGraph connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug BrainGraph into your agent.
Your users connect BrainGraph once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan