Context Base
Connect every SaaS data source, govern access per agent, and version every change. Your agents read and write through Bash, MCP, or REST — all backed by Git-style version control.
What is it
Context Base is the file-based workspace that sits between your data sources (Notion, Slack, Gmail, Postgres, GitHub) and your agents (Claude, Cursor, n8n, custom code). It ingests data into a unified file system, exposes it through Bash, MCP, and REST APIs, scopes permissions per agent, and tracks every read and write with Git-style commits. Think of it as the persistent, multi-tenant file system your AI pipeline never had — built from day one for agents that share, collaborate, and need to roll back.
Capabilities
Pre-built connectors for Notion, Slack, Gmail, Google Sheets, Postgres, MongoDB, Linear, Jira, and Airtable. Push arbitrary data via API for anything else.
Each agent gets an Access Point with explicit read/write paths. An untrusted agent reads /shared, your orchestrator owns the whole workspace. Changes apply instantly.
Every write is a commit with author, timestamp, and diff. Branch before risky operations, merge when done, roll back any file in milliseconds.
Expose your entire workspace as a Model Context Protocol server. Plug it into Claude, Cursor, or any MCP-compatible client without writing glue code.
Multiple agents share the same workspace without overwriting each other. Path isolation prevents conflicts, branches enable safe parallel writes.
Deploy with Docker into your own VPC for full data sovereignty, or use our managed cloud. Same API, same MCP server, same Bash interface.
How it works
Step 01
Authenticate Notion, Slack, Gmail, Postgres, or any of our pre-built connectors. Data is synced into a structured file tree (.json, .md, folders) your agents can read.
Step 02
Create an Access Point per agent. Choose which paths it can read, which it can write, and which are hidden. Permissions take effect immediately.
Step 03
Pick an interface: Bash for container-based agents, MCP for Claude / Cursor, or REST API for anything else. All three share the same permission model.
Step 04
Every write is auto-committed with the agent's identity. Branch before risky changes, query the audit log, or roll back any file with a single API call.
Use Cases
Background agents that crawl, summarize, and cite sources for days. Context Base preserves every output, so a session crash doesn't lose a week of work.
Claude does research, GPT drafts, a custom agent runs analytics. They share files in one workspace, each scoped to its own paths, with full audit history.
Plug your internal Slack, Notion, and databases into one queryable file tree. Agents read structured files via Bash and MCP — no custom ETL pipelines.
Use Context Base as the persistent storage layer for retrieval pipelines. Documents are versioned, permissions are scoped, embeddings refresh automatically.
Integrations
Native support for the most common AI agent runtimes and SaaS data sources. More added every week.
FAQ
Context Base is a file-based workspace built specifically for AI agents. It ingests SaaS data into a unified file system, lets multiple agents collaborate with per-agent permissions, and tracks every change with Git-style version control. Agents access it through Bash, MCP, or REST API.
Free to start. Self-hosted or cloud. Open-source on GitHub.