MCP Resources
MCP resources expose read-only graph data for browsing without making tool calls.
What Are Resources?
Resources are read-only data endpoints that MCP clients can discover and read. Unlike tools, resources do not modify state. They let agents browse the graph structure before deciding what to query.
LocusGraph currently exposes one resource via resources/list.
Available Resource
URI: locusgraph://contexts
This resource returns the contexts linked into the selected graph. Each item includes:
context_idreference_count
Example resources/read
{
"jsonrpc": "2.0",
"id": 1,
"method": "resources/read",
"params": {
"uri": "locusgraph://contexts"
}
}Resources are graph-scoped. The auth worker injects the selected graph into the proxied MCP request, so resources/read operates on the graph chosen during OAuth authorization.
When to Use Resources vs. Tools
| Use Case | Approach |
|---|---|
| Browse what context IDs exist in the selected graph | Read resources |
| Search for specific wisdom | Call retrieve_memories tool |
| Store new knowledge | Call store_event tool |
| Explore before filtering tools | Read resources, then query with tools |
Resources are best for orientation. Tools are best for action.
Prompts
The same MCP surface also exposes one prompt through prompts/list and prompts/get:
auto_capture— a reusable prompt that instructs the client to store new knowledge immediately withstore_event