Derive

to.derivePublished by derive.toOfficial publisherv1.0.0Updated Oct 24, 2026

Publish agent output to permanent versioned URLs, read review comments back, and revise.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & StorageCommunication & Collaboration

Overview

AI-generated overview

Derive is a hosted workspace where an assistant publishes HTML, Markdown, LaTeX or built sites to permanent versioned URLs, reads review comments and publishes.

What you can do
Publish artifacts such as HTML pages, Markdown documents, LaTeX papers, decks or whole built sites to a durable URL, with each revision kept as a new version at the same link. Read review comments and feedback pinned to exact text, then publish focused revisions in response. Organize published work in a library with live previews, pinning, collections and sharing. Manage access levels and optional password-protected public links. Work with workspace agents and scheduled jobs whose results land in the same artifact library.
When to use it
Useful when an assistant produces documents, reports, pages or sites that people need to review and keep, and you want a stable link with version history instead of pasting output into chat. Also fits teams where several people or agents comment on and revise the same work over time.
Requirements
A remote MCP endpoint over streamable HTTP with OAuth sign-in required; a Derive account and workspace are needed for permanent artifacts. The README also mentions an anonymous draft flow that needs no account and returns a live URL plus a claim link. A local stdio variant is offered as an npm package with server and token settings.
Before you install
Publishing makes content reachable at a URL, so check whether an artifact is private, workspace-visible or public before sharing. The agent acts at the role you grant: publish access writes directly and notifies the workspace, while lower scopes only suggest changes in comments. Comments, versions and content stay with the artifact and are visible to anyone it is shared with.

Installation

In SourceWeft

  1. Open Derive in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/to.derive%2Fderive/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "derive": {
      "type": "http",
      "url": "https://derive.to/mcp"
    }
  }
}

README

[Derive]

Publish, review, and own your AI artifacts.

One durable URL for every version, comment, revision, and decision. Your team reviews the work; any compatible agent can act on the feedback. Hosted, or one self-hosted container.

Try free  ·  Self-host  ·  Docs

[License: FSL-1.1-ALv2] [npm @derive-to/cli] [npm @derive-to/mcp]

[The Derive library: published artifacts with live previews]

Try it now

No account or install is needed. One request publishes a live page:

bash
curl -F [email protected] https://derive.to/v1/drafts   # or a .zip of a whole site# → a live URL, plus a claim link that turns the draft into a#   permanent, versioned artifact in your workspace

Give your agent a durable place to publish, find, and improve work:

bash
npx skills add derive-to/derive --skill derive        # any agent that reads skillsclaude mcp add --transport http derive https://derive.to/mcp   # or connect over MCP

Or paste this into a compatible coding agent and let it set itself up:

text
I'd like you to set up Derive: where the work we make gets published, reviewed, and kept.
Install the skill if I have npm: npx skills add derive-to/derive --skill deriveOtherwise, read https://derive.to/skill.md and follow it (MCP server: https://derive.to/mcp).
Then pick a plan, report, or designed page we've worked on recently and publish it. If I'm not connected to Derive, use the anonymous draft flow. It needs no account and returns a live URL with a claim link. Send me both links.

What is Derive

Derive is a workspace for work made with agents. Give an HTML page, Markdown document, LaTeX paper, deck, or built site a lasting URL and version history. Publish from the browser, CLI, HTTP API, or a compatible agent over MCP. Keep the work private or share it, leave comments, edit it directly, and publish the next version at the same URL.

The content, version history, and comments stay with each artifact. A teammate or another agent can open the same URL and see what changed without reconstructing the work from a chat.

A workspace can also keep agents: named workers with standing instructions, the sources they may use, and a model account. You ask one for work, or give it a schedule, and each piece of work is a job you can follow. A job runs on its owner's own computer, or on a Derive machine where the workspace has them, and publishes its results to the same artifact library. When a job needs a person, it waits in their Inbox.

Derive is Fair Source and self-hostable. Run it as one container on your own infrastructure or use the hosted app.

Features

[A published artifact rendered at its permanent URL]

Publish anything, get a permanent URL

HTML, Markdown, a LaTeX paper, or a whole built site. Every revision is a new version at the same URL, so a link you shared last week still resolves, and still shows its history.

Comments and changes stay with the work

Share an artifact and @mention the people or agents who should weigh in. Comments pin to the exact text, direct edits create new versions, and connected agents can read feedback and publish focused revisions. When a decision truly needs sign-off, request a formal review of that version.

 [An artifact with its comment and review panel open]
[The Derive library: every published artifact with a live preview]

A library for published work

Every artifact lands in a library with a live preview. Pin the work you use often, find work shared with you, and organize related artifacts in collections.

Also included:

  • Portable work. Content, versions, and comments stay with the artifact so another person or agent can continue the work.
  • Agents and jobs. Make an agent from Claude Code or Codex, ask it for work, put it on a schedule, or chain several into a workflow. Run it on your own machine with derive runner serve, or on a Derive machine. See Run agents.
  • Checkpoints. Save the state of ongoing work in a page that a later session can open.
  • Sandboxed viewer. Artifacts run on an opaque origin, isolated from cookies and other artifacts.
  • Flexible storage. Use SQLite and local disk, or Postgres and S3/R2 at scale.
  • Live collaboration. Comments, optional approvals, and presence update over Server-Sent Events.
  • Share previews. Links show an artifact preview in Slack, Discord, X, and Notion.
  • CLI and MCP. Publish from the terminal or connect a compatible agent.
  • Access controls. Make work private, visible to the workspace, or public. Public links can also use a password.

Roadmap

The current roadmap lives at derive.to/roadmap and keeps its history at the same URL.

Get started

Hosted

The fastest path. No install.

  1. Go to derive.to
  2. Create an account
  3. Publish your first artifact

You get a library, in-browser publishing, version history, and comments.

Self-host

One container is the whole product: API, web, sign-in, publishing, comments, and the sandboxed viewer, with SQLite and blobs in one volume.

Follow the self-hosting quick start to install a digest-pinned release or build the current checkout. It includes secure first-user bootstrap, readiness checks, and a verified first backup. See the deployment guide for Postgres, S3/R2, and cloud hosts.

Want a complete artifact rather than a blank starter? Open or publish one of the official examples: a designed launch page, a research brief, or a living status report. Each shows a different starting point.

From the terminal

bash
npm i -g @derive-to/cliderive init my-doc --template slides   # templates: md · html · slidescd my-docderive publish                         # versioned URL; the id is saved to derive.json

Connect your coding agent (MCP)

[Add to Cursor]  or one line for Claude Code: claude mcp add --transport http derive https://derive.to/mcp

bash
# Derive is a remote MCP server (OAuth). Connect either client:claude mcp add --transport http --scope project derive https://derive.to/mcpcodex mcp add derive --url https://derive.to/mcp
# or run a local stdio server (set DERIVE_SERVER; DERIVE_TOKEN for a static bearer):npx -y @derive-to/mcp

The agent acts at the role you grant. Publish access publishes directly, as a kept and restorable version with the workspace notified; a lower scope suggests changes in comments for a person to apply. Full setup and tool guidance is in packages/mcp/SKILL.md.

How it works

One Node container is the whole product; storage is pluggable behind interfaces. The same image self-hosts on SQLite and local disk, scales on Postgres and S3/R2, or runs on Cloudflare Workers.

apps/api          HTTP API, sandboxed artifact serving, viewerapps/web          web UI (TanStack Start, SPA mode, static bundle)packages/core     domain: ports, publish, markdown render, viewer shellpackages/db       MetaStore: sqlite (default) · postgres · d1packages/storage  BlobStore: fs (default) · s3/r2packages/cli      derive init (md/html/slides) · derive publish <file|dir> · derive runner serve --agent <id> (work an agent's jobs)packages/mcp      Local compatibility MCP: eight tools + derive://guide (the remote /mcp has seventeen)

Every artifact ships OG and Twitter meta plus an oEmbed document, serves a live Server-Sent Events stream, and renders under a strict sandbox CSP on an opaque origin. See the artifact authoring standard for authoring and embed details.

License

Functional Source License (FSL-1.1-ALv2), fair source. Run, modify, and self-host Derive freely for any purpose except offering it as a competing commercial product or service. Each release automatically converts to Apache-2.0 two years after it ships. See the plain-English licensing guide.

Source: README.md at commit a4aa0e4

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Derive integrations

DeriveAI x402 APIs

Published by GitHub account deriveit33z-ship-it

A remote MCP server exposing 25 pay-per-request intelligence APIs, from web scraping and domain audits to Arabic NLP, paid in USDC on Base.

Streamable HTTPWeb executable
Web Search & Scraping25 toolsOct 24, 2026