Derive logo

Derive

Publishes agent-created artifacts to versioned URLs, retrieves review feedback, and supports revisions through Derive.

Install Derive

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "derive": {
      "command": "npx",
      "args": [
        "-y",
        "@derive-to/mcp"
      ],
      "env": {
        "DERIVE_SERVER": "YOUR_VALUE_HERE",
        "DERIVE_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Derive MCP server connects compatible agents to a workspace for publishing HTML, Markdown, LaTeX, decks, and built sites. Agents can create versioned artifacts, read comments and review feedback, and publish revisions to the same durable URL. Use it when work needs persistent history and human or agent review instead of remaining in a chat session. Hosted MCP access uses HTTP and OAuth; a local stdio package is also available.

Use cases

  • Publish generated reports as versioned URLs
  • Read teammate comments before revising a document
  • Create reviewable previews of websites and slides
  • Carry artifact history between agent sessions

Key features

  • Versioned artifact URLs
  • Comment and review feedback access
  • Agent-driven revisions
  • HTML, Markdown, LaTeX, deck, and site publishing
  • Hosted HTTP and local stdio MCP modes
  • Private, workspace, and public sharing

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 39d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · @derive-to/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars30Stargazers on the source repository.
npm downloads241Package downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.

How Derive works

What Derive MCP server does

The Derive MCP server gives compatible agents a way to publish work into the Derive artifact library. Supported content includes HTML pages, Markdown documents, LaTeX papers, presentations, and complete built sites. Each artifact receives a durable URL, while later publications become new versions under that same URL.

Agents can use Derive to retrieve comments and review feedback attached to an artifact, then produce a focused revision. Comments remain associated with the relevant work and can refer to specific text. Depending on the granted role, an agent can publish directly or suggest changes for a person to apply.

The workspace can keep artifacts private, share them with workspace members, or expose them publicly. Public links may also be protected with a password. Derive stores the content, version history, and comments together so another person or agent can continue from the artifact rather than reconstructing context from a conversation.

How it works

The hosted MCP endpoint is available at https://derive.to/mcp and uses remote HTTP with OAuth. A compatible coding agent connects to that endpoint and acts with the role assigned by the workspace. Publishing access creates a retained, restorable version and notifies the workspace; lower access can limit the agent to proposing changes through comments.

Derive can also run as a local stdio MCP server. The repository provides the @derive-to/mcp npm package for this mode. The broader product can be hosted by Derive or self-hosted in one container. Self-hosting supports SQLite and local disk by default, with Postgres and S3/R2 available for larger deployments.

Setup and configuration

For the hosted option, connect the agent to https://derive.to/mcp. Claude Code can be configured with claude mcp add --transport http derive https://derive.to/mcp; Codex can use codex mcp add derive --url https://derive.to/mcp. Cursor has a provided MCP installation link in the project documentation.

For local stdio operation, run npx -y @derive-to/mcp. Set DERIVE_SERVER to identify the Derive server, and use DERIVE_TOKEN when authentication should use a static bearer token.

A hosted account is not required for the anonymous draft flow. An uploaded draft can return a live URL and a claim link; claiming it turns the draft into a permanent, versioned artifact in a workspace. Authenticated workspace use provides the library, access controls, comments, and version history.

Tools and capabilities

The Derive MCP server supports workflows built around these capabilities:

  • Publish an artifact or a new version to a durable URL.
  • Read comments and review feedback attached to published work.
  • Revise an artifact in response to feedback.
  • Work with private, workspace-visible, or public artifacts.
  • Preserve content, comments, and version history for later sessions.
  • Use Derive’s live artifact previews and shared review workflow.

The repository excerpt does not list individual MCP tool names or their full input schemas, so integrations should rely on the server’s published MCP instructions for exact calls.

Limitations and notes

Derive is licensed under FSL-1.1-ALv2. The hosted endpoint requires the client to support the documented remote connection and OAuth flow. Local operation requires Node.js tooling capable of running the npm package.

The anonymous draft path is useful for publishing without an account, but the README distinguishes drafts from artifacts claimed into a workspace. Review, persistent ownership, and workspace access controls therefore depend on using the hosted service or a configured self-hosted instance.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Derive

Derive is an MCP server that connects compatible coding agents to the Derive workspace. Its main tools support publishing HTML, Markdown, LaTeX, decks, and built sites, reading comments and review feedback, and publishing revised versions to the same durable URL. Hosted access uses HTTP and OAuth; local use runs through an npm package.

Install the local server with `npx -y @derive-to/mcp`, or connect a client to `https://derive.to/mcp` for the hosted HTTP service. Claude Code and Codex have documented commands, and Cursor has a provided MCP installation link.

Yes, Derive works with Cursor through its hosted MCP endpoint. The README provides a Cursor MCP installation link configured for `https://derive.to/mcp`; the connection uses the remote HTTP service.

Yes, Derive can read comments and review feedback attached to an artifact and publish a focused revision. Each revision becomes a new version while keeping the artifact’s durable URL and history.

Yes, Derive can run as one self-hosted container. The default deployment uses SQLite and local disk, while Postgres and S3/R2 are supported for larger setups; the self-hosting quick start covers installation and first-user bootstrap.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDerive AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/derive?style=directory)](https://allmcps.com/mcp/derive)
HTML Embed
<a href="https://allmcps.com/mcp/derive"><img src="https://allmcps.com/api/badge/derive?style=directory" alt="Derive on AllMCPs" /></a>