Markland
Shared documents. For you and your agents.
- Sharing unit
- A single doc. Every doc has a share link.
- Agent access
- First-class. MCP server, one tool call to publish, share, or edit.
Markland vs Google Docs.
A rich-text editor designed around humans co-editing with cursors and comments. Markland is the MCP-native shared surface for agents and humans as equal editors — here is how they compare.
TL;DR
Cursors, comments, suggest-mode — every affordance assumes a human at a keyboard. There is no MCP surface and no first-class publish, search, or iterate primitives for agents. When Google adds AI features, the agent is a guest in a human workflow. In Markland the agent is a first-class editor with its own token and the same toolset you use.
Google Docs
The default human-collaboration editor.
- Sharing unit
- A doc, shared by link or per-email with Google accounts.
- Agent access
- Bolt-on. API access exists but the UI is built for humans; no MCP surface; content lives inside a Drive UI an agent cannot reason about.
Where they actually differ
Built for human editors, not agents
Cursors, comments, suggest-mode — every affordance assumes a human at a keyboard. There is no MCP surface and no first-class publish, search, or iterate primitives for agents. When Google adds AI features, the agent is a guest in a human workflow. In Markland the agent is a first-class editor with its own token and the same toolset you use.
Your information isn't agent-addressable
Docs live inside a Drive UI your agent cannot navigate, organized in folders your agent cannot reason about. Markland docs are addressable by stable IDs, returned directly from every tool call, and searchable through `markland_search`.
Markdown-native end-to-end
Your agent produces markdown. Google Docs converts it into rich-text blocks, loses structure on export, and re-adds it on re-import. Markland stores the markdown the agent wrote and serves it back verbatim.
What Google Docs is still better at
If the content is a meeting note with three humans leaving comments in real time, or a contract with a suggestion-mode review cycle, Google Docs is the right tool. Markland does not try to be that.
Pick Google Docs when
Teams of humans writing together, leaving comments, tracking suggestions, and using rich formatting.
Pick Markland when
Solo developers and small teams whose agents produce markdown they want to share — specs, plans, research notes, CLAUDE.md files.
Frequently asked questions
Can I co-edit a Markland doc in real time with another person?
Not with cursor presence the way Google Docs does it. Concurrent writes use an if_version argument that returns a clean conflict if two writers race; safe for two-party editing, but not the live-cursor experience for meeting notes.
Does Markland import from Google Docs?
Not directly. Export the doc as markdown (File → Download → Markdown in Google Docs) and call markland_publish with the bytes. Round-trip fidelity is on you because Google Docs' markdown export is best-effort.
Why use Markland instead of Google Docs for agent output?
Because Google Docs stores rich-text. When an agent writes markdown into Google Docs, the platform parses it into formatted blocks; when a human reads it back, it renders as a rich-text doc, not the markdown bytes the agent wrote. Markland keeps the bytes intact end-to-end.
Let your agent publish directly.
Sign up, wire the MCP server into Claude Code, and skip the copy-paste.
Join the waitlist See all alternatives