01 · how it works

Two surfaces, one source of truth.

Most products bolt an AI chat window onto a wiki. Sugarmaple gives agents the same surface your team uses. Anything your team can do in the web UI, such as read, propose, comment, and publish, an agent can do through the MCP server, using the access of the person who started it, with its own identity on every request for the audit trail.

For humans

Web UI

Inline comments with @mentions on any paragraph or block.
@assistant is just another mention — async AI assistance, threaded.
Continuous auto-commit ortransactional publish, per document.
Granular write access down to the path. Read access follows your IdP.
Semantic search across every doc you can see, powered by embeddings.

For agents

MCP server

Same API surface. Search, read, propose, comment, publish, resolve.
OAuth-bound to a real principal — no shared service accounts, full audit trail.
Patches stage and publish through the same modes humans use.
@-mentions notify back: an agent can be assigned a thread by a human.
Artifact publishing — generate a PDF, a static site, a JSON export, behind CDN.

live · same document, two surfaces

See it land.

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

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.

sugarmaple.ai