INDIVIDUAL MCP TOOL

createStore

A new, empty FactoGraph store of the person's own: its private link and its MCP connector address.

factograph.appnone authenticationAvailability not checked

LIVE ENDPOINT

https://api.factograph.app/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for createStore and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.factograph-public]
url = "https://api.factograph.app/api/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: factograph-public
Remote MCP URL: https://api.factograph.app/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "factograph-public": {
      "type": "http",
      "url": "https://api.factograph.app/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "factograph-public",
  "transport": "streamable-http",
  "url": "https://api.factograph.app/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

getManual — How to ask a public store and cite its facts, and what it holds: how many facts, from which sources.
listFacts — Every fact in a public store, numbered, each number a link to the fact.
ask — Ask a question; the store answers only from its facts, each claim linked to its fact, and checks the answer against them.
getStep — Where a running step is now: its next prompt, or its result.
replyToPrompt — Answer the prompt a step is waiting on - do the model work in its `system` and `messages` first.