All servers · Shops & products

FactoGraph

app.factograph/factograph · v0.2.0

Measured by MCP Station

Description written by the publisher, not verified

Memory for AI agents: facts a person approved, each with a link, and answers that cite them.

Connect

claude mcp add --transport http factograph https://api.factograph.app/api/mcp

{
  "mcpServers": {
    "factograph": {
      "url": "https://api.factograph.app/api/mcp"
    }
  }
}

Tools as reported by the server

• getManual
  The store's manual - how to run its steps and cite its facts - and what it holds: how many facts, from which sources. Read it before the store's other tools, and follow it.
• listFacts
  Every fact in the store, numbered, each number a link to the fact. Cite a fact as its number with its link, [F3](<link>).
• ask
  Ask a question; the store answers only from its facts, each claim linked to its fact, and checks the answer against them. Stores nothing. Returns the step's state: `waiting` (a prompt to do and answer with replyToPrompt), `running` (call getStep), `done` (do what `next` says) or `failed`.
• startStep write/delete
  Start a step - propose, add, documents, ask or remove - in a private store, with its JSON body, as the manual says. propose stores nothing; add stores only facts the person approved, with propose's proposal_id and their reply as confirmation; remove deletes only with confirm true, after the person c
• getStep
  Where a running step is now: its next prompt, or its result.
• replyToPrompt write/delete
  Answer the prompt a step is waiting on - do the model work in its `system` and `messages` first. Keep answering until the step is done or failed.
• createStore
  A new, empty FactoGraph store of the person's own: its private link, which these tools take as `store`. Only after the person said yes to having one. Nothing is stored until the link is first opened. The link is the store's key: give it to them once, and never put it anywhere public.

Website · JSON · Text for agents · Registry updated 2026-10-21