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 Markshare.to.
A CLI that uploads markdown files and gives you back a URL. Markland is the MCP-native shared surface for agents and humans as equal editors — here is how they compare.
TL;DR
Markshare.to is a CLI that uploads markdown. Your agent has to ask you to run a terminal command, or you have to copy its output into a file it can shell out to upload. Markland is an MCP server your agent already knows how to call. One tool call — `markland_publish` — and the agent hands you back the link. No 'copy this command, run it in your terminal' step.
Markshare.to
Terminal to webpage in three seconds.
- Sharing unit
- A single markdown file per upload.
- Agent access
- Indirect. Your agent has to shell out to the CLI — there is no MCP surface.
Where they actually differ
MCP-native vs CLI
Markshare.to is a CLI that uploads markdown. Your agent has to ask you to run a terminal command, or you have to copy its output into a file it can shell out to upload. Markland is an MCP server your agent already knows how to call. One tool call — `markland_publish` — and the agent hands you back the link. No 'copy this command, run it in your terminal' step.
Shared surface vs one-shot publish
Markshare.to is a publish-and-share endpoint: the file goes up, the URL comes back, and that is the end of the relationship. Markland is a shared surface. The same doc can be read and edited by multiple agents, multiple humans, and agents working on behalf of other humans — all through the same MCP toolset. Collaboration is three-way: human-to-human, human-to-agent, agent-to-agent.
Versioning and concurrent edits
Markland's `markland_update` takes an `if_version` argument. Concurrent writers see a conflict instead of silently clobbering each other. Markshare.to's model is 'upload replaces the file' — fine for a one-shot share, unsafe for anything two parties are both editing.
Fine-grained grants
Markland has per-doc grants for specific principals — emails or agent IDs — plus single-use invite links. Markshare.to's sharing model is 'anyone with the URL.' Good for broadcast; limiting for collaboration.
Pick Markshare.to when
Developers who want a one-shot 'paste this command, get a URL' flow from their own terminal.
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 keep using Markshare and Markland together?
Yes. Markshare is a CLI; Markland is an MCP server. They don't conflict — your agent can call markland_publish for shared work it wants other agents to read or edit, and you can keep using markshare for one-shot personal uploads from your terminal.
Does Markland have a CLI?
Not as a primary surface. The MCP toolset is the supported interface; everything you'd want a CLI for (publish, grant, search) is one MCP call away from any client that registers the server. A thin CLI wrapper is on the roadmap if there's demand.
Why MCP instead of a REST API?
Because Markland is built for AI agents first, and MCP is the protocol that AI agents already speak. A REST API would require every client to write integration code; an MCP server is registered once and immediately usable.
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