Arc

io.github.hudsonkitPublished by GitHub account hudsonkitv0.14.1Updated Oct 29, 2026

Author, validate, lay out, render, and diff architecture diagrams as code.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Arc lets an assistant author, validate, auto-layout, render and diff architecture diagrams as code, exporting SVG, PNG, HTML, ASCII or animation.

What you can do
  • Validate diagrams and get coded diagnostics with suggested fixes
  • Auto-layout a full or minimal diagram and structurally diff two diagrams
  • Render diagrams as SVG, PNG, HTML snippets or ASCII box art
  • Render flow animations as GIF or MP4 to a given output path
  • Convert a valid diagram into a typed TypeScript module
  • Build studio handoff URLs and, with a matching studio, publish live views and saved architecture reviews
When to use it
Useful when you keep architecture diagrams as JSON in a repository and want an assistant to check, lay out, render or compare them, or to hand a diagram off to the Arc studio for viewing.
Requirements
Local stdio process run via npx or bunx; Node.js 22 or newer. No account, API key or environment configuration is required. PNG export needs a local Chrome/Chromium (override with ARC_CHROME); animation export also needs ffmpeg (ARC_FFMPEG). Live views and reviews need a matching Arc studio build, and HTTP serving needs ARC_MCP_TOKEN when bound outside loopback.
Before you install
Live-view and review tools publish diagram content to a studio and return URLs; anyone with a full viewer URL can read that diagram, and review calls return author and viewer capabilities that should be kept private. Caller-declared agent labels are not verified identities. Live sessions are in-memory and expire, so export from the studio to keep a diagram. HTTP mode requires ARC_MCP_TOKEN outside loopback.

Installation

In SourceWeft

  1. Open Arc in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Arc]

@hudsonkit/arc-mcp

MCP server for architecture diagrams as code.

Gives AI agents the full Arc toolchain over the Model Context Protocol — author, validate, lay out, render, and diff architecture diagrams from any MCP client.

[npm version] [license]

Run it

No install needed — the server runs over stdio:

bash
npx -y @hudsonkit/arc-mcp# or: bunx @hudsonkit/arc-mcp

Client setup

Requires Node.js 22 or newer. No account, API key, or environment configuration is required. PNG export needs a local Chrome/Chromium installation; animation export also needs ffmpeg.

Claude Code:

bash
claude mcp add --scope project arc -- npx -y @hudsonkit/arc-mcp

Devin:

bash
devin mcp add arc -- npx -y @hudsonkit/arc-mcp

Any MCP client (JSON config):

json
{  "mcpServers": {    "arc": {      "command": "npx",      "args": ["-y", "@hudsonkit/arc-mcp"]    }  }}

Tools

ToolWhat it does
validate_diagramCoded diagnostics for ArcDiagramData — consume by code, apply a supportedFixes entry, re-validate
auto_layoutAuto-layout a full diagram or minimal input (nodeData + connectors + connectorStyles)
diff_diagramStructural DiagramDelta — feed to <ArcDiagram data={head} delta={delta} /> for a diff render
render_svgDeterministic SVG export — eleven themes, light/dark; authored flows animate via SMIL or sample at flowTime
render_pngPNG raster via a local Chrome/Chromium binary (ARC_CHROME to override, ARC_CHROME=none to disable), sampled at flowTime
render_animationGIF/MP4 flow animation to an output path via Chrome frames + ffmpeg (ARC_FFMPEG to override)
render_htmlReact component snippet, iframe embed, or standalone HTML page
render_asciiUnicode/ASCII box-art rendering for terminals and docs
diagram_to_typescriptEmit a typed ArcDiagramData TypeScript module
editor_handoffBuild URLs that open the diagram in the Arc studio
open_live_diagramOpen a live architecture view and return its stable URL and session ID
begin_live_diagram_workDeclare work before starting it, with a summary and canvas, node, or region scope
update_live_diagramPublish a complete validated diagram revision to that view
finish_live_diagram_workFinish the current work ID and leave the view idle for the next task
end_live_diagramMark the diagram complete and retain the final view
open_architecture_reviewSave a baseline and open a durable architecture review
update_architecture_reviewSave findings, evidence, decisions, questions, and summary
resume_architecture_reviewResume an interrupted review with its author capability
revoke_architecture_review_shareInvalidate the old viewer link and return a new capability

Live architecture

Start the Arc studio with bun run dev, then call open_live_diagram with { diagram, title?, agent?: { harness, name? } }. Open the returned liveUrl once. The view starts idle. Before doing diagram work, call begin_live_diagram_work with { sessionId, summary, scope? } and retain its workId. Publish complete revisions with update_live_diagram({ sessionId, diagram, message? }); keep node IDs stable so the viewer can follow each move. In your cleanup/finally path, call finish_live_diagram_work({ sessionId, workId, message? }) when the declared work ends. This leaves the same view idle and reusable. Use end_live_diagram with { sessionId, message? } only when the entire diagram session is complete.

Scope defaults to { type: "canvas" }. Use { type: "nodes", nodeIds: ["api"] } for existing boxes, or { type: "region", x: 400, y: 80, width: 200, height: 160 } for the area where new boxes will appear. A scope accepts 1–200 unique existing node IDs, each at most 200 characters. Region coordinates must be finite and within ±100000; width and height must be positive and at most 100000. Summaries are trimmed, 1–500 characters, and cannot contain control characters. Concurrent begin calls and stale finish IDs are rejected without replacing active work.

The live view belongs to the Hudson Kit Arc studio. ARC_EDITOR_URL selects the studio base URL; open_live_diagram also accepts baseUrl for an individual view, including a deployment prefix such as /arc. The MCP client name/version comes from its initialize handshake. The displayed connection ID is generated by the server; it does not claim to be the client's conversation ID.

The optional agent object declares a harness label and, if useful, an agent name for this view. For example, agent: { harness: "Codex", name: "Reviewer" } adds actor.harness and actor.displayName. These are caller-declared labels, not verified identities. They never replace the actual MCP actor.name, actor.version, or connection actor.id, and do not carry over to other views. Both labels are trimmed, limited to 1–80 characters, and reject control characters.

The local scripts/liveDiagram.control.ts driver accepts ARC_AGENT_HARNESS and optional ARC_AGENT_NAME to send these labels. Neither has a default; ARC_AGENT_NAME requires ARC_AGENT_HARNESS. The driver accepts JSON lines such as {"type":"begin","summary":"Inspect API","scope":{"type":"nodes","nodeIds":["api"]}}, then {"type":"finish","workId":"<returned ID>","message":"API checked"}. Its status command reports local session metadata. quit closes the relay; it does not claim that unfinished work succeeded.

In stdio mode the first live view starts a loopback HTTP relay on a free port. Keep the MCP process running and open the view on the same computer. The browser may request local-network or loopback-network access when a hosted HTTPS studio connects to that relay. Allow that permission for the studio. Loopback addresses are treated specially by browser mixed-content rules; arbitrary HTTP LAN or remote relay URLs do not get the same guarantee. Browser support, enterprise policy, and the studio's CSP can still prevent the connection. An all-local studio (bun run dev, ARC_EDITOR_URL=http://localhost:5188) avoids the public website-to-loopback permission boundary. For a remote relay used from an HTTPS studio, serve the relay over HTTPS. See the Local Network Access specification and Chrome's permission guidance. HTTP mode serves the stream beside /mcp, so a configured remote relay can be used from another computer. The URL fragment carries a read capability for one diagram; anyone given the full URL can read it. Only its owning MCP connection can update it. Browser requests must come from that view's configured studio origin. The HTTP server enforces ARC_MCP_TOKEN on every MCP request when set, and requires it when binding outside loopback.

Each stream sends the latest full snapshot immediately, including after a reconnect. Invalid updates preserve the previous state. Only explicit work is working; edits outside a declared work item stay idle. Valid updates during work preserve its scope and renew a five-minute lease. Finishing marks the work complete and the session idle. Disconnect or lease expiry marks work interrupted; ending the entire session completes any active work. A later standalone edit clears previous work metadata. These calls describe declared diagram work, not unobserved harness thinking. Unfinished diagrams remain available while their owning MCP connection stays open. Completed diagrams expire one hour after completion; unfinished diagrams expire one hour after their owner disconnects. Stopping the MCP process discards ordinary in-memory live sessions. Save/export a diagram from the studio when it needs to outlive that process.

Live tools require a matching MCP build and studio build. During development, build this checkout with bun run build:mcp and configure the client to run node /absolute/path/to/arc/packages/mcp/dist/arc-mcp.mjs; run its studio with bun run dev. Listing a tool here does not mean an older published package or the currently deployed Hudson Kit website already includes it.

Saved architecture reviews (private preview)

The private preview adds a durable review to the same Hudson Kit canvas. Follow the private preview setup to build matching studio and MCP artifacts and serve them from one private address.

Open with open_architecture_review({diagram,title,question,repository?,agent?}). Repository metadata is {name,url?,revision?}. The result includes a private author resumeToken as well as the normal sessionId and read-only viewer URL. Use the existing begin/update/finish/end tools for declared work and diagrams. Save evidence through update_architecture_review with summary, findings, decisions, and openQuestions; omitted fields stay unchanged, and supplied arrays replace the full previous list.

Findings are {id,title,detail,severity,nodeIds?,sources}, with severity info|low|medium|high. Sources are {path,line?,revision?,url?}. The studio shows those references alongside the canvas, and its Save review action downloads {schemaVersion:1,baseline,snapshot,revisions} without secrets. Source claims are author-supplied evidence, not verified by Arc itself.

Reviews persist before publishing each revision. Keep ARC_REVIEW_DIR and the private server address stable to reopen the same saved viewer link after a restart. Use resume_architecture_review({sessionId,resumeToken,agent?}) after losing the author connection. Optional agent: {harness,name?} supplies caller-declared display labels alongside the new connection's actual MCP identity. Omit it to use only that connection identity. It cannot displace a live author. Completed reviews stay read-only and keep their final author and history unchanged. revoke_architecture_review_share({sessionId}) invalidates the old viewer capability. Saved reviews are not removed by the ordinary live view's one-hour expiry.

For a terminal author, scripts/review.control.ts keeps one HTTP MCP connection open and accepts JSON lines of {id?,name,arguments}. Set ARC_MCP_URL and, if configured, ARC_MCP_TOKEN in its environment. EOF disconnects the author; finish/end calls must be explicit. Keep its output private because opening a review returns author and viewer capabilities.

Resources

URIContent
arc://schema/diagramGenerated draft-07 JSON Schema for ArcDiagramData
arc://skill/diagramsArc diagram-generation skill for agents
arc://docs/llmDense LLM briefing

Self-hosting over HTTP

The published bin runs over stdio, which is all a local client needs. To serve Arc to clients on other machines, run the Streamable HTTP server from a checkout of the repo:

bash
git clone https://github.com/hudsonkit/arc && cd arcbun installARC_MCP_HOST=127.0.0.1 ARC_MCP_PORT=5190 bun run mcp:http# MCP endpoint: http://127.0.0.1:5190/mcp · health: /health
VariableDefaultPurpose
ARC_MCP_PORT5190Port to listen on
ARC_MCP_HOST127.0.0.1Interface to bind; nonloopback binds require ARC_MCP_TOKEN
ARC_MCP_PUBLIC_URLhttp://<host>:<port>Externally reachable origin used in live stream URLs and Host validation; preserve this Host through a reverse proxy
ARC_MCP_ALLOWED_ORIGINSStudio and relay originsAdditional comma-separated browser origins permitted to use /mcp
ARC_EDITOR_URLhttp://localhost:5188Studio base used by handoffs and live views
ARC_MCP_TOKENUnsetAgent bearer credential; required outside loopback
ARC_STUDIO_DIRUnsetProduction studio build to serve beside MCP
ARC_REVIEW_DIR~/.arc/reviewsPrivate durable review storage, outside the studio build

Arc doesn't run a public MCP endpoint. If you need a hosted one, open an issue at github.com/hudsonkit/arc.

MCP Registry

Arc's registry identity is io.github.hudsonkit/arc. The install metadata lives in server.json, and the npm package declares the same mcpName so the registry can verify ownership.

Maintainers can run the Publish to npm GitHub Actions workflow with package scope mcp for an MCP-only patch release, or all for a coordinated release. The workflow sets both versions before building, verifies the packed server, publishes npm, then publishes the registry metadata using GitHub OIDC. A dry run validates and packs without publishing. GitHub's curated MCP catalog requires initial onboarding after publication to the official MCP Registry.

Related packages

Studio + docs: hudsonkit.com/arc · Source: github.com/hudsonkit/arc

License

MIT

Source: packages/mcp/README.md at commit 24ea394

Tools

10

validate_diagram

Validate an ArcDiagramData document. Returns coded diagnostics — consume by `code`, apply one `supportedFixes` entry, re-validate. `ok` is false while any error-severity diagnostic remains.

Parametersdiagramrequiredseverity

diff_diagram

Structural diff of two Arc diagrams. Returns a DiagramDelta — added/removed/moved/changed nodes, connector adds/removes/changes (keyed by connector id or from→to), connectorStyles and groups deltas, layoutChanged. Feed it to <ArcDiagram data={head} delta={delta} /> for a diff render.

Parametersbaserequiredheadrequired

auto_layout

Run Arc auto-layout on a diagram. Pass a full diagram or minimal input (nodeData + connectors + connectorStyles).

Parametersinputrequired

render_ascii

Render an Arc diagram as monospace ASCII/Unicode box art.

ParameterscharsetdiagramrequiredmaxWidth

render_svg

Render an Arc diagram as deterministic SVG markup using the package export path.

ParametersmodethemediagramrequiredpaddingflowTimeincludeGridanimateFlowsbackgroundColor

render_png

Render an Arc diagram as a PNG via an installed Chrome/Chromium binary. Returns MCP image content plus render metadata. Set ARC_CHROME if Chrome is not on PATH.

ParametersmodescalethemediagramrequiredpaddingflowTimeincludeGridbackgroundColor

render_animation

Render diagram flows as a GIF or MP4 artifact. Uses deterministic frame captures through Chrome plus ffmpeg; requires an `output` path because video payloads are too large for MCP text.

ParametersfpsmodescalethemeformatoutputrequireddiagramrequiredpaddingdurationincludeGridbackgroundColor

render_html

Render an Arc diagram as a React component snippet, iframe embed, or standalone HTML page.

ParametersmodethemetitlewidthformatheightbaseUrldiagramrequiredpaddingdataNamesessionIdincludeGrid+3 more

diagram_to_typescript

Convert a valid Arc diagram JSON into a TypeScript module that exports ArcDiagramData.

ParametersdiagramrequiredexportName

editor_handoff

Build URLs to open a diagram in the Arc studio. Returns a hash-based editor URL and showcase link.

ParametersviewbaseUrldiagramrequiredsessionId

Version history

1
  1. v0.14.1LatestOct 26, 2026

Score

90% 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 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts