Get started

Your first fact, shared by two agents, in a few minutes.

Pick how you'll work with Factbed. Every method reads and writes the same record, so you can mix them: agents over MCP, services over the API, people in the dashboard.

1
Create your workspace
Sign up with your work email. You land in the dashboard with a workspace and a first API key for the API and CLI. MCP clients sign in with your account instead. Name each agent, so the history shows which agent wrote what.

Dashboard · API keys

Workspaceacme

Key namerenewals-agent

API keyfb_live_••••3f9a
2
Add Factbed to your AI client
Add this server URL to Claude, ChatGPT, Cursor or any MCP client, then sign in with your Factbed account. There's no key to paste. Steps for each client are below.
Server URLMCP
```
https://mcp.factbed.io/mcp

# Your agent gets four tools
get_fact   set_fact   search_facts   fact_history
```

Write your first fact

Ask your agent to save something it knows. It records the value with a source and a date, under a name like doc#fact that any agent can ask for.

renewals-agentMCP

You: Save that Northwind renews on 2027-03-01.
     It's in the CRM note.

→ set_fact
    name     customer.northwind#renewal_date
    value    2027-03-01
    source   CRM note
✓ Saved as v1

Read it from a second agent

Connect another agent and ask it. It answers from the same fact instead of searching again.

support-agentMCP

You: When does Northwind renew?

→ get_fact customer.northwind#renewal_date

Agent: On 2027-03-01, according to a CRM note
       saved by renewals-agent today.

5
See it in the dashboard
Open the Northwind account doc and select the fact to see its value, source and date, every earlier version, and which agents have read it. Anyone on your team can confirm or correct it from here.

Dashboard · Fact history

Factcustomer.northwind#renewal_date

In docNorthwind account

Value2027-03-01 · v1 · Current

SourceCRM note · 2026-11-09

Read byrenewals-agent, support-agent

1
Create a workspace and a key
Sign up with your work email and copy the API key from the dashboard. Make one key per service or agent, so the history shows which one wrote what.

Dashboard · API keys

Workspaceacme

Key namerenewals-service

API keyfb_live_••••3f9a

Write your first fact

Send the value with a source. Factbed stamps the date and saves it as a new version under the fact's name.

renewals-serviceAPI

$ curl -X PUT https://api.factbed.io/v1/facts/customer.northwind%23renewal_date \
    -H "Authorization: Bearer $FACTBED_KEY" \
    -d '{"value": "2027-03-01", "source": "CRM note"}'
{ "version": 1, "status": "current" }

Read it from a second service

Any other key in the workspace reads the same fact, with its source, date and version.

support-serviceAPI

$ curl https://api.factbed.io/v1/facts/customer.northwind%23renewal_date \
    -H "Authorization: Bearer $FACTBED_KEY"
{ "value": "2027-03-01", "version": 1,
  "source": "CRM note", "dated": "2026-11-09",
  "written_by": "renewals-service" }

4
See it in the dashboard
Open the Northwind account doc to see the value, its history and who read it. Anyone on your team can confirm or correct it from there.

Dashboard · Fact history

Factcustomer.northwind#renewal_date

Value2027-03-01 · v1 · Current

Read bysupport-service

1
Install and sign in
Install the CLI, then sign in with your Factbed account. In CI, set an API key in the environment instead.
terminalCLI
```
$ npm install -g @factbed/cli
$ factbed login
✓ Signed in to acme

# In CI
$ export FACTBED_KEY=fb_live_…
```
2
Write your first fact
Set a value with its source. Load a whole price list or policy with import; each row becomes a fact linked back to the file.
terminalCLI
```
$ factbed set customer.northwind#renewal_date 2027-03-01 \
    --source "CRM note"
✓ Saved as v1
```

Read it anywhere

Read it back from a script or a CI job, or check its history before a deploy goes out.

ci jobCLI

$ factbed get customer.northwind#renewal_date
2027-03-01  v1 · CRM note · 2026-11-09

$ factbed history customer.northwind#renewal_date
v1  2027-03-01  CRM note  current

MCP setup

Add Factbed to your AI client.

One server URL works everywhere: https://mcp.factbed.io/mcp. You sign in with your Factbed account, so there's no key to paste.

Claude

Web, desktop and mobile apps

Open Customize › Connectors.
Click Add, then Add custom connector.
Name it Factbed and paste the server URL.
Click Add, then Connect, and sign in to Factbed.
In a chat, turn Factbed on from the + menu under Connectors.

On Team and Enterprise plans, an Owner adds the connector once under Organization settings › Connectors. Members then connect with their own Factbed account.

Add custom connectorClaude

# Name
Factbed

# Remote MCP server URL
https://mcp.factbed.io/mcp

ChatGPT

Web and desktop apps

Open Settings › Apps & Connectors.
Under Advanced settings, turn on Developer mode.
Click Create, name it Factbed and paste the server URL.
Choose OAuth, then sign in to Factbed.
In a chat, pick Factbed from the + menu.

On Business and Enterprise workspaces, an admin may need to allow custom connectors first.

New connectorChatGPT

# Name
Factbed

# MCP server URL
https://mcp.factbed.io/mcp

# Authentication
OAuth

Claude Code

Terminal and IDE extensions

Run the command on the right in your project.
Start Claude Code and run /mcp.
Select factbed and sign in to Factbed in your browser.

Add --scope project to share the server with your team through .mcp.json. Each person still signs in with their own account.

terminalClaude Code

$ claude mcp add --transport http factbed https://mcp.factbed.io/mcp

# then, inside Claude Code
/mcp

Cursor

Editor and agent

Open ~/.cursor/mcp.json, or .cursor/mcp.json in your project.
Add the factbed server shown on the right.
Open Settings › MCP and click Connect next to factbed.
Sign in to Factbed in your browser.

mcp.jsonCursor

{
  "mcpServers": {
    "factbed": { "url": "https://mcp.factbed.io/mcp" }
  }
}

VS Code

GitHub Copilot agent mode

Create .vscode/mcp.json in your project.
Add the factbed server shown on the right.
Click Start above the server entry.
Sign in to Factbed when VS Code asks.

.vscode/mcp.jsonVS Code

{
  "servers": {
    "factbed": {
      "type": "http",
      "url": "https://mcp.factbed.io/mcp"
    }
  }
}

Other clients

Any client that supports remote MCP servers

Add a remote server using Streamable HTTP.
Use the server URL on the right.
Sign in to Factbed when the client opens the OAuth window.

If your client can't do OAuth, use the API with a key instead.

Remote MCP serverAny client

# Transport
Streamable HTTP

# URL
https://mcp.factbed.io/mcp

# Auth
OAuth (sign in with Factbed)

What next

Load a workflow

Start from ready-made docs for renewals, support or vendor onboarding.

See workflows

Invite your team

Let colleagues review and correct facts in the dashboard, and connect their own agents.

Invite people

Read the reference

Every MCP tool, API endpoint and CLI command, with fact kinds, naming rules and error codes.

Open reference

Your first fact, shared by two agents, in a few minutes.

Create your workspace

Add Factbed to your AI client

Write your first fact

Read it from a second agent

See it in the dashboard

Create a workspace and a key

Write your first fact

Read it from a second service

See it in the dashboard

Install and sign in

Write your first fact

Read it anywhere

Create your workspace

Write a doc

Review what agents change

Add Factbed to your AI client.

Claude

ChatGPT

Claude Code

Cursor

VS Code

Other clients

What next

Load a workflow

Invite your team

Read the reference