raphdocs
Documentation hub

Documentation with room to explain the system.

raph indexes local code, docs, and scoped memory into a graph under ~/.raph/, then exposes that graph through MCP and Studio so coding agents can search, traverse, and keep context close to the repo.

Start here Set up MCP See commands
Local first

Single-binary graph storage

The graph lives locally, uses an embedded SQLite-compatible backend, and does not need a hosted graph service to start working.

Agent ready

MCP tools for memory and retrieval

Agents can store scoped memory, run hybrid search, index codebases, crawl docs, and walk related nodes from the same local store.

Inspectable

Studio for graph exploration

Open the local UI to inspect nodes, tables, metadata, neighbor relationships, and maintenance actions without leaving your machine.

Why the docs changed

One landing page, several focused guides.

The docs are now broken into topic pages so each area can be more descriptive without forcing readers through one long scroll. Use the pages below as your entry points.

Guide 01

Getting started

Install raph, initialize config, index a repository, start the MCP server, and open Studio.
Guide 02

MCP and coding agents

See the MCP tools, supported agent config targets, and the exact config shape each agent expects.
Guide 03

Studio

Understand the graph explorer, local maintenance actions, and what to expect when inspecting nodes and tables.
Guide 04

Reference and troubleshooting

Use the command cheat sheet, install options, update behavior, and quick fixes for common setup issues.
Current shape

What ships in this repository

  • A Go CLI in cmd/raph.
  • Config bootstrapping in internal/config.
  • An embedded local database in internal/db.
  • A workspace indexer in internal/indexer.
  • A background repository synchronizer in internal/syncer.
  • An MCP server in internal/mcp.
  • A zero-dependency Studio UI in internal/studio.
  • Scoped durable memory plus searchable non-Go document chunks.
Storage note

SQLite-compatible for now

The first implementation stays local-first with a pure-Go embedded backend so macOS, Linux, and Windows builds work cleanly from day one.