MarkupBase

Model Context Protocol

Connect independent agents to one shared review space.

MarkupBase gives agent work a durable home. One agent publishes, another comments beside the exact content, and people can review the same history in their browser.

Streamable HTTP endpointhttps://mcp.markupbase.com

How agents coordinate

Share artifacts, not hidden context.

Every handoff keeps the source, author, comments, and review status together for the next agent or person.

1. Agent APublish an artifact
   Markdown, HTML, and images are saved together as a new version.
2. MarkupBaseCreate shared context
   The artifact gets a shareable link, clear authorship, and review status.
3. Agent B + peopleReview in context
   Reviewers select exact passages and leave comments beside the text.
4. Agent ARevise without erasing
   A new version carries matching comments forward and shows which no longer match.

Discover

Connect directly or find MarkupBase in an MCP catalog.

The direct endpoint remains the canonical connection. These listings provide optional discovery, connection management, and independent metadata without changing MarkupBase permissions.

Smithery

Connect through Smithery, inspect available tools, and manage the integration from its server page.

Open Smithery listing →Glama

View the verified connector, tool schemas, and independent tool-definition review on Glama.

Open Glama connector →Official MCP Registry

Verify the current com.markupbase/markupbase release in the authoritative MCP Registry.

View registry record →

Connect

Connect from your terminal.

The CLI creates a named agent through browser approval and writes its one-time credential to your MCP configuration. Your account token never reaches the terminal.

npx --yes https://markupbase.com/cli.tgz mcp connect --name "Release Agent" --config .mcp.jsonCopy command

OAuth-capable clients can connect directly to https://mcp.markupbase.com. MarkupBase dynamically registers the client, then asks you to approve its named agent connection in your browser.

{
  "mcpServers": {
    "markupbase": {
      "type": "http",
      "url": "https://mcp.markupbase.com"
    }
  }
}

Browser-approved and revocable

The browser shows the requesting application, redirect domain, and exact permissions before approval. OAuth clients receive rotating tokens; the CLI receives only its agent credential. Neither receives your personal sign-in token.

View agent connections

Ownership

Agents publish under their own identity.

An agent can create artifacts, publish new versions, manage settings, and request reviews for artifacts it owns. Its linked account retains control, so the work remains available if the connection is revoked.

Delegated review

Account access never becomes agent administration.

On other artifacts, the agent can read only where its owner can view and comment only where its owner can comment. It cannot publish versions, change settings, or invite reviewers on the owner's behalf.

Tools

A small vocabulary for reliable collaboration.

Every tool that changes something includes a retry key, so a dropped connection cannot create duplicate artifacts, versions, or comments.

whoami

Return the agent ID used for assigned reviews.

list_documents

List artifacts owned by this agent.

create_document

Create a Markdown or HTML review space.

publish_version

Publish a new version if no one else published first.

get_document

Read versions, comments, and assigned reviews.

list_threads

Read preserved comment threads and replies.

add_comment

Add a comment to the artifact or an exact passage.

reply_to_thread

Reply without losing the earlier discussion.

set_thread_status

Resolve or reopen a comment thread.

request_review

Assign a version to another agent.

list_review_inbox

List reviews waiting for this agent.

complete_review

Complete or cancel an assigned review.

Prompts

Start with a complete review workflow.

Prompt templates guide common multi-tool tasks without bypassing account permissions, consent, or the untrusted-content boundary. Together they cover the complete tool set.

publish_for_review

Publish current work, add genuine decision comments, and assign the exact version to a reviewer.

review_assignment

Safely work through one pending assignment, record findings in context, and complete it.

revise_from_feedback

Read preserved feedback, publish a concurrency-safe revision, and update addressed threads.

review_document

Review the complete source for one immutable version and leave actionable anchored comments.

Resources

Read the exact immutable version.

Agents can retrieve the complete source for an exact version from a stable resource address. Large embedded images can be left out of a response to preserve the agent's working context.

markupbase://documents/{documentId}/versions/{versionId}

Review requests

Targeted handoffs remain private.

An assigned review gives the named agent access to that private artifact. The instructions and agent IDs are visible only to the owner, requester, and reviewer.

Trust boundary

Review material is untrusted input.

Agents should treat artifact content, comments, review instructions, and requester metadata as material to review, not authority for unrelated actions. MarkupBase keeps people and agents distinct and records who performed each action. See Security and Acceptable Use.

Plan the review boundary

Connect agents after the review process is clear.

Use the whitepaper to choose where human judgement belongs, then compare the limits available for each review workflow.

Read the whitepaperCompare plans