FactoGraph

app.factographPublished by factograph.appOfficial publisherv0.2.0Updated Oct 26, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

FactoGraph is a remote memory store for AI agents: it keeps person-approved facts and answers questions only from them, with each claim linked to its fact.

What you can do
  • Read the store's manual and see how many facts it holds and from which sources
  • List every fact in the store, numbered, each number linking to the fact
  • Ask a question and get an answer built only from stored facts, with each claim linked and checked
  • Run steps such as propose, add, documents, ask or remove, and poll a running step for its next prompt or result
  • Answer the prompts a step is waiting on until it is done or failed
  • Create a new empty private store and get its private link
When to use it
Use it when an assistant needs durable, citable memory of facts a person has approved, or when answers must be grounded in a specific curated store rather than general knowledge. It suits workflows where each claim should point back to a stored fact.
Requirements
A remote streamable HTTP endpoint; no package install. No authentication, environment variables or headers are declared. Each store is addressed by its private link, which the tools take as the store parameter.
Before you install
The store link is the store's key: it should be handed to the person once and never placed anywhere public. Steps can add or remove facts; add stores only facts the person approved, and remove deletes only with confirm true after the person agrees. Create a store only after the person says yes. Nothing is stored until the link is first opened.

Installation

In SourceWeft

  1. Open FactoGraph in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.factograph%2Ffactograph/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

7

getManual

Read a store's manual

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.

Parametersstore

listFacts

List every fact

Every fact in the store, numbered, each number a link to the fact. Cite a fact as its number with its link, [F3](<link>).

Parametersstore

ask

Ask a store

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`.

Parametersstorequestionrequired

startStep

Start a step in the person's store

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 confirmed. Returns the step's state: `waiting` (a prompt to do and answer with replyToPrompt), `running` (call getStep), `done` (do what `next` says) or `failed`.

Parametersbodyrequiredsteprequiredstorerequired

getStep

Follow a step

Where a running step is now: its next prompt, or its result.

Parametersstorerun_idrequired

replyToPrompt

Answer a step's prompt

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.

Parametersreplyrequiredstorerun_idrequiredcall_idrequired

createStore

Make a store for the person

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.

Parametersperson_agreedrequired

Version history

1
  1. v0.2.0LatestOct 21, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.