Markdown for people
and agents, as equals.

Sugarmaple is a shared Markdown workspace where people and AI agents read, write, and comment with the same hands. Your team works in the browser, Obsidian-style. Your agents work over MCP, using the access of the person who runs them. One org, one set of permissions, one history — all of it in a git repo you own, so your data is always yours.

docs/oncall/handoff.md live

On-call handoff

The week’s on-call notes, so the next person starts where this one stopped.

Open items

The nightly export failed twice on Tuesday. Both runs passed on retry, and the cause is still open.

The staging database is due for a restart on Friday. Check the backup finished before you start it.

mcp · sugarmaple.ai · session #84a
live · same document, two surfaces
why

Everything else
makes you choose.

Working with agents means reading, editing, and sharing Markdown equally well as a human and through an agent. Every tool we tried was good at one of those and bad at the rest.

Google Docs · Confluence
Great for people. Agents are an afterthought.

In Google Docs and Confluence an agent gets a chat box on the side. Here it reads, edits and comments in the same documents you do, with your access, and its own name in the history.

Obsidian + git
Great for you. Hard to share.

Local-first is wonderful until a teammate needs in. No org, no access control, no browser — just a folder and a merge conflict.

Just git
Great for agents. Rough on humans.

Everyone needs a GitHub account and a terminal to read a doc. Comments, sharing, and search are things you build yourself.

Sugarmaple
All three. No trade-off.
  • Org-level access. Sign in with your identity provider, invite your team, and share across the org — no GitHub accounts required.
  • Read and edit in the browser, Obsidian-style, with inline comments and @mentions.
  • Agents over MCP, using the access of the person who started them, their own identity showing in the audit trail.
  • Git-backed, always. Every doc is a Markdown file in a repo you own — you never lose access to your own data.
what falls out

Build the doc layer,
and the rest shows up.

The motivating story was simple: one place where people and agents can edit, read, and share Markdown equally well. Once that exists, it turns out a lot of other things want to live there too.

01

Knowledge bases

Docs that agents can search semantically and keep current land better than a wiki nobody updates. Ask a question, get an answer with a citation, fix the doc in the same breath.

02

Issue tracking

A ticket is a Markdown file with a status line. Agents open, triage, and close them through the same tools they use for everything else — and the whole board is diffable.

03

Shared memory

What an agent learns in one session is written down where the next session — and the next teammate — will find it. Memory becomes a document, not a black box.

04

And more

Runbooks, decision records, specs, meeting notes. Anything that wants to be read by people and worked on by agents, with history you can trust.

get started

Connect a repo.
You’re live.

Install our GitHub App, pick a repo and create your free org. Most people are set up in under five minutes.

Get started →
Connect a GitHub repo and you’re writing in minutes — free, no card.