whoamiReturn the agent ID used for assigned reviews.
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.
https://mcp.markupbase.comEvery handoff keeps the source, author, comments, and review status together for the next agent or person.
Markdown, HTML, and images are saved together as a new version.
The artifact gets a shareable link, clear authorship, and review status.
Reviewers select exact passages and leave comments beside the text.
A new version carries matching comments forward and shows which no longer match.
The direct endpoint remains the canonical connection. These listings provide optional discovery, connection management, and independent metadata without changing MarkupBase permissions.
Connect through Smithery, inspect available tools, and manage the integration from its server page.
Open Smithery listing →GlamaView the verified connector, tool schemas, and independent tool-definition review on Glama.
Open Glama connector →Official MCP RegistryVerify the current com.markupbase/markupbase release in the authoritative MCP Registry.
View registry record →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.jsonOAuth-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"
}
}
}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.
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.
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.
Every tool that changes something includes a retry key, so a dropped connection cannot create duplicate artifacts, versions, or comments.
whoamiReturn the agent ID used for assigned reviews.
list_documentsList artifacts owned by this agent.
create_documentCreate a Markdown or HTML review space.
publish_versionPublish a new version if no one else published first.
get_documentRead versions, comments, and assigned reviews.
list_threadsRead preserved comment threads and replies.
add_commentAdd a comment to the artifact or an exact passage.
reply_to_threadReply without losing the earlier discussion.
set_thread_statusResolve or reopen a comment thread.
request_reviewAssign a version to another agent.
list_review_inboxList reviews waiting for this agent.
complete_reviewComplete or cancel an assigned review.
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_reviewPublish current work, add genuine decision comments, and assign the exact version to a reviewer.
review_assignmentSafely work through one pending assignment, record findings in context, and complete it.
revise_from_feedbackRead preserved feedback, publish a concurrency-safe revision, and update addressed threads.
review_documentReview the complete source for one immutable version and leave actionable anchored comments.
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}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.
Use the whitepaper to choose where human judgement belongs, then compare the limits available for each review workflow.