For the complete documentation index, see llms.txt. This page is also available as Markdown.

Introduction

Copy any component from a live web page as clean HTML or JSX — from inside your AI agent.

DivMagic MCP is a remote Model Context Protocol server. Once it is connected, your agent can copy designs from real web pages and read and write your DivMagic library, without you leaving the editor.

It works the same way the DivMagic extension does: the page is opened in a real browser and what it renders is converted. That is the difference from fetching HTML — the output carries the computed styles and the markup the page actually produced, not the template it shipped.

You:   copy the pricing table from stripe.com/pricing as JSX with tailwind
Agent: → copy_component_from_url
       ← <section className="flex flex-col …">…</section>

What you can do

Copy a page

Render any public URL and get back HTML or JSX, styled with Tailwind classes, inline styles, or a stylesheet.

Read your library

List and read the designs already saved from the extension, Studio, or the dashboard.

Save to your library

File a copy — or markup the agent wrote — into the same library everything else lives in.

Endpoint

Setting
Value

URL

https://api.divmagic.com/v1/mcp

Transport

Streamable HTTP

Authentication

Authorization: Bearer <your MCP key>

Is this the same as the API?

No. They are separate products with separate keys and separate credits.

REST API
MCP

Called by

Your own code

Your AI agent

Key

API key

MCP key (dvmcp_…)

Credits

API credits

MCP credits

Library access

No

Yes

An API key will not authenticate against the MCP endpoint, and API credits are not spent by MCP calls.

Next

Getting startedTools

Last updated