Shared memory for your agents.
A hosted Markdown MCP your agents actually share. Built for agents, not humans — with ETag concurrency so two agents working the same file never clobber each other. In private preview, by invitation.
Already invited? Log in
Why Markbase
The bottleneck isn't the agents anymore.
Modern agentic workflows aren't one model doing one thing. They're a fleet. Claude Code for the engineering. Claude.ai for the thinking. Other harnesses and other models for other specialties. Almost all of them speak MCP.
The real bottleneck is the memory they share — the place each agent reads from and writes to so the next one can pick up where the last one left off.
Local markdown folders break the moment a second agent shows up. Notion is built for humans collaborating, not agents. Obsidian was never meant to be a public API. So we built the thing those tools aren't.
What you get
Four things, no surprises.
Hosted & secure
A real MCP endpoint over HTTPS with OAuth 2.1. No local app to babysit, no port-forwarding tricks.
Pure markdown
UTF-8 .md files in hierarchical folders, with frontmatter. No blocks, no proprietary schema. What you write is what's on disk.
Agent-native surface
A small set of tools — read, write, search, plus typed-collection ops where you need them — designed for how agents work, not retrofitted from a human collaboration tool.
Conflict-free by design
Every read returns an ETag; every write asserts the one it expects. Parallel agents can't overwrite each other.
How it works
One service, two backing stores.
Agent
Any MCP client
Markbase
Hosted MCP · always on
Search index
Full-text search across your docs
Object storage
Documents · versioning on
Small, boring infrastructure — and we run all of it. No containers, no servers for you to manage.
Yours to shape
Tell your agents how to use it.
Drop a _markbase.md at any folder root and you've defined the contract for that subtree — what it's for, what the frontmatter is, what's append-only, who writes here. Agents read the _markbase.md chain root-to-leaf before they act and apply what they find. The opinion lives inside the store, not in a CLAUDE.md replicated into every harness. You write the rules once; every agent picks them up.
Typed collections
A table when you need one. Still just Markdown.
Drop a _schema.md in any folder and that folder becomes a typed collection. Records stay ordinary .md files — Markdown with YAML frontmatter — but every write conforms to the shape you defined, and agents can filter, sort, and paginate the collection by field. Use it for the things that keep recurring: decisions, RFCs, postmortems, customer interviews. The shape is yours to author, not baked into the product.
---
collection: Decisions
required:
title:
type: string
max_length: 200
status:
type: enum
values: [Proposed, Accepted, Superseded]
summary:
type: string
max_length: 1000
optional:
date:
type: date
superseded_by:
type: path
---
# Decisions
One record per choice we make.Knowledge that crosses projects
Past work becomes context for new work.
Each project's memory lives in its own Markbase workspace, but knowledge doesn't have to stay there. Ask an agent to design a feature in your new project using the architecture decisions from your old one — it can read both in the same conversation. What you figured out once becomes a resource for every project that benefits from it, instead of staying with the one it was written for.
Conflict-free by design
Many agents, one file, no clobbering.
Every successful write produces a new version under the hood — nothing is destructively overwritten. If agents race, every loser gets a clean etag_mismatch back with the current ETag. Each one re-reads, re-applies, retries. No silent loss, no merge dialog.
Version history
Every write is a version. None are lost.
Every update is versioned and retained for 365 days. Agents can read any past state by ID — useful for audits, understanding why something changed, and catching mistakes before they compound.
Getting access
Hosted, by invitation.
Markbase is in private preview. Tell us what your agents are doing and we'll set you up with a workspace and an endpoint.
- 1 Email us about what you're building
- 2 We provision your workspace and credentials
- 3 Point your MCP client at your endpoint
// Point any MCP client at the hosted endpoint
{
"mcpServers": {
"markbase": {
"url": "https://api.markbase.cloud/mcp"
}
}
}What's in the box
No surprises.
- A stable, versioned MCP API.
- Markdown documents kept in versioned object storage.
- Optimistic concurrency via
ETag— no clobbered writes. - Per-folder
_markbase.mdgovernance — your conventions, inside the store. - Sign in with Google — authentication handled for you.
- Hosted and operated by us — nothing for you to run.