Markbase

Technical details

How your agents share context in Markbase.

Markbase hosts the documents and files your agents use between tasks. Here is how they connect, find the right information, and update it safely.

Connect through MCP

MCP (Model Context Protocol) lets compatible AI tools read and write content in Markbase. You approve a connection using OAuth. Your agent continues to run in the tool you already use.

Setup instructions and client requirements

Save documents agents and people can read

Project briefs, decisions, and handover notes are stored as Markdown documents, organized in workspaces and folders. Agents can list and search documents, then read the relevant material before starting a task. Files such as PDFs and spreadsheets can be stored alongside the notes.

Make saving and reading part of the workflow

Markbase does not automatically watch conversations or choose what to remember. Instruct your agents to read the relevant notes before working and save decisions and progress afterward. Folder instructions in _markbase.md give connected agents a shared set of conventions to follow.

Check versions before changing a document

A document read returns an ETag identifying its current version. An agent sends that value with its update. If someone has changed the document since the read, the version check rejects the update so the agent can read the new version and reconcile its changes.

This detects conflicting edits; it does not merge them automatically. Targeted edits require a version check. Integrations should also supply version checks for whole-document updates.

Version checks and conflict handling

Review changes and manage access

Document revisions let you inspect earlier versions and compare changes. Deleted documents go to trash for a limited recovery period. You can review saved content and manage connections in the dashboard.

Team membership applies across the organization: members can read and write its workspaces. Separate folders or workspaces are not separate permission boundaries.

Team roles and access

Add structure when you need it

For recurring items such as reports or decisions, typed collections define required fields. Agents can create consistent records and filter them by those fields. Ordinary notes can remain free-form documents.

Browse the full documentation

Give your next agent a head start.

Create a free workspace. Ask your agent to save today’s decisions, then use them to start your next session.

Free plan. No card required.