Potencia tu agente
Instalación del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
Aún no hay una versión empaquetada en el registro. Sigue el README del repositorio.
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
HyperWeave is a visual CLI for agents. Structured spec in, deterministic SVG out. Artifact classes include diagrams, charts, tables, and more. Each SVG is self-contained, with layout, theme, and machine-readable metadata compiled into the file.
Visual CLI for agents. Deterministic SVG diagrams, tables, and charts with embedded structured metadata. Zero JavaScript. Renders anywhere markdown does.
Why It Exists
Humans can't keep pace with the volume of text agents produce. Pictures are the obvious fix, and every picture format gives something up. Markdown is portable but flat. HTML is expressive but fragile. Raster images travel well but discard their structure. Model output is flexible but never twice the same.
A HyperWeave artifact carries its own spec, so the thing your agent drew is the thing your agent can read back. Useful as:
The picture is the record.
Philosophy
<img> tag does.Artifact Format Comparison
✓ full · ~ partial · ✗ none
Diagrams encode topology, not pixels. HyperWeave supports the following diagram types: pipeline, fanout, fanin, hub, cycle, loop, dag, lanes, state-machine, sequence, tree, and comparison. Nodes carry brand logo glyphs, labels, and tags. Edges carry labels and motion to help process information better. Every diagram renders as a self-contained SVG with its full spec and hash-verified digest embedded for agents to read directly. Render them in a markdown file, send to Slack as an image, or render directly in your terminal.
hyperweave compose diagram --spec-file /dev/stdin -g primer --variant porcelain --surface inlay --face light -o provider-router-light.svg <<'JSON'
{
"topology": "fanout",
"orientation": "horizontal",
"title": "One call, best model",
"subtitle": "Fanout · horizontal",
"zones": ["router", "providers"],
"node_style": "card+glyph",
"glyph_tint": "full",
"nodes": [
{ "id": "router", "label": "model router", "desc": "1 call, best model\ncapability-routed", "role": "hero", "kind": "router", "gather": true },
{ "id": "claude", "label": "Claude", "desc": "long-context", "glyph": "anthropic" },
{ "id": "gemini", "label": "Gemini", "desc": "multimodal", "glyph": "gemini" },
{ "id": "openai", "label": "OpenAI", "desc": "tool-use", "glyph": "openai" },
{ "id": "deepseek", "label": "DeepSeek", "desc": "reasoning", "glyph": "deepseek" },
{ "id": "kimi", "label": "Kimi", "desc": "agentic", "glyph": "kimi" },
{ "id": "qwen", "label": "Qwen", "desc": "multilingual", "glyph": "qwen" }
],
"edges": [
{ "source": "router", "target": "claude", "label": "route", "label_style": "chip", "relation": "drift", "marker": "arrow" },
{ "source": "router", "target": "gemini", "relation": "drift", "marker": "arrow" },
{ "source": "router", "target": "openai", "relation": "drift", "marker": "arrow" },
{ "source": "router", "target": "deepseek", "relation": "drift", "marker": "arrow" },
{ "source": "router", "target": "kimi", "relation": "drift", "marker": "arrow" },
{ "source": "router", "target": "qwen", "relation": "drift", "marker": "arrow" }
]
}
JSON
hyperweave extract broadcast-split-light.svg --respond payload > broadcast-split.json
hyperweave compose diagram --spec-file broadcast-split.json -g primer --variant porcelain --surface inlay --face light -o broadcast-split-light.svg
hyperweave extract compose-gate-light.svg --respond payload > compose-gate.json
hyperweave compose diagram --spec-file compose-gate.json -g primer --variant porcelain --surface inlay --face light -o compose-gate-light.svg
hyperweave compose diagram --spec-file pipeline-row -g primer --variant space --surface inlay --face light -o mcp-gateway-light.svg
pipeline-row is a bundled preset; the URL API renders it by name at /v1/diagram/pipeline-row/primer.static.
hyperweave extract verbs-mouth-light.svg --respond payload > verbs-mouth.json
hyperweave compose diagram --spec-file verbs-mouth.json -g primer --variant porcelain --surface inlay --face light -o verbs-mouth-light.svg
hyperweave compose diagram --spec-file dag-providers -g primer --variant noir --surface inlay --face light -o frontier-serving-light.svg
dag-providers is a bundled preset; the URL API renders it by name at /v1/diagram/dag-providers/primer.static.
hyperweave compose diagram --spec-file cycle-flow -g primer --variant porcelain --surface inlay --face light -o cycle-flow-light.svg
cycle-flow is a bundled preset; the URL API renders it by name at /v1/diagram/cycle-flow/primer.static.
hyperweave compose diagram --spec-file loop-hillclimb-turn -g primer --variant porcelain --surface inlay --face light -o loop-hillclimb-turn-light.svg
loop-hillclimb-turn is a bundled preset; the URL API renders it by name at /v1/diagram/loop-hillclimb-turn/primer.static.
hyperweave compose diagram --spec-file tree-health -g primer --variant porcelain --surface inlay --face light -o tree-health-light.svg
tree-health is a bundled preset; the URL API renders it by name at /v1/diagram/tree-health/primer.static.
Twelve layouts, fifty-nine bundled presets, one spec vocabulary. Variations are values of orientation, not layouts of their own:
Render any preset by name at /v1/diagram/{preset}/primer.static, or run hyperweave discover diagram for every preset, orientation and field.
HyperWeave matrices are structured tables rendered as portable SVGs. A single JSON description can produce comparison grids, registries, tiers, benchmark tables, heatmaps, chips, glyphs, bars, and status maps, while carrying a machine-readable payload for agents.
hyperweave compose matrix --spec-file /dev/stdin -g primer --variant porcelain -o one-artifact.svg <<'JSON'
{
"title": "One artifact. Many readers.",
"subtitle": "how each consumer ingests the same SVG",
"columns": [
{
"id": "reader",
"label": "READER",
"role": "label"
},
{
"id": "mark",
"label": "",
"kind": "glyph",
"glyph_tint": "full"
},
{
"id": "pixels",
"label": "PIXELS",
"kind": "check"
},
{
"id": "motion",
"label": "MOTION",
"kind": "pill"
},
{
"id": "via",
"label": "READS VIA",
"kind": "chip"
}
],
"rows": [
{
"label": "GitHub README",
"cells": [
{
"glyph": "github"
},
{
"state": "full"
},
{
"state": "on"
},
{
"chips": [
"camo",
"css animation"
]
}
]
},
{
"label": "VS Code preview",
"cells": [
{
"glyph": "vscode"
},
{
"state": "full"
},
{
"state": "on"
},
{
"chips": [
"markdown preview"
]
}
]
},
{
"label": "Slack unfurl",
"cells": [
{
"glyph": "slack"
},
{
"state": "partial"
},
{
"state": "off"
},
{
"chips": [
"image proxy"
]
}
]
},
{
"label": "Gmail body",
"cells": [
{
"glyph": "gmail"
},
{
"state": "partial"
},
{
"state": "off"
},
{
"chips": [
"img tag"
]
}
]
},
{
"label": "Agent",
"cells": [
{
"glyph": "mcp"
},
{
"state": "none"
},
{
"state": "off"
},
{
"chips": [
"hw:payload",
"hwz/1",
"markdown twin"
]
}
]
}
],
"notes": "pixels for humans · hw:payload for agents"
}
JSON
# Connectors preset
https://hyperweave.app/v1/matrix/connectors/primer.static?variant=porcelain
# Any table, one URL: base64url MatrixSpec JSON (8 KB cap)
https://hyperweave.app/v1/matrix/custom/primer.static?spec=<base64url>
# CLI, with the markdown twin alongside
hyperweave compose matrix --spec-file table.json -g primer --variant porcelain --markdown-out table.md
Another matrix configuration for visualizing benchmarks:
SWE-bench Verified % · USD per Mtok · current flagships, jun 2026 · sources: vals.ai · artificialanalysis.ai · model cards
hyperweave compose matrix --spec-file /dev/stdin -g primer --variant cream --surface twin --faces -o frontier-benchmarks.svg <<'JSON'
{
"title": "Frontier vs Open",
"subtitle": "coding & price · SWE-bench Verified against price per million tokens · current flagships, jun 2026",
"columns": [
{
"id": "model",
"label": "MODEL",
"kind": "text",
"align": "left",
"role": "label"
},
{
"id": "mark",
"label": "",
"kind": "glyph",
"align": "center",
"glyph_tint": "full"
},
{
"id": "swe",
"label": "SWE-bench Verified",
"kind": "numeric",
"align": "center",
"polarity": "higher",
"unit": "%"
},
{
"id": "pin",
"label": "INPUT",
"sublabel": "per Mtok",
"kind": "numeric",
"align": "center",
"polarity": "lower",
"unit": "$"
},
{
"id": "pout",
"label": "OUTPUT",
"sublabel": "per Mtok",
"kind": "numeric",
"align": "center",
"polarity": "lower",
"unit": "$"
}
],
"rows": [
{
"label": "Claude Fable 5",
"cells": [
{
"glyph": "anthropic"
},
{
"value": 95.0
},
{
"value": 10
},
{
"value": 50
}
],
"section": "FRONTIER · CLOSED WEIGHTS"
},
{
"label": "Claude Opus 4.8",
"cells": [
{
"glyph": "anthropic"
},
{
"value": 88.6
},
{
"value": 5
},
{
"value": 25
}
],
"section": "FRONTIER · CLOSED WEIGHTS"
},
{
"label": "GPT-5.5",
"cells": [
{
"glyph": "openai"
},
{
"value": 82.6
},
{
"value": 5
},
{
"value": 30
}
],
"section": "FRONTIER · CLOSED WEIGHTS"
},
{
"label": "Gemini 3.1 Pro",
"cells": [
{
"glyph": "gemini"
},
{
"value": 80.6
},
{
"value": 2
},
{
"value": 12
}
],
"section": "FRONTIER · CLOSED WEIGHTS"
},
{
"label": "DeepSeek V4-Pro",
"cells": [
{
"glyph": "deepseek"
},
{
"value": 80.6
},
{
"value": 0.44
},
{
"value": 0.87
}
],
"section": "OPEN WEIGHTS"
},
{
"label": "Kimi K2.6",
"cells": [
{
"glyph": "kimi"
},
{
"value": 80.2
},
{
"value": 0.95
},
{
"value": 4.0
}
],
"section": "OPEN WEIGHTS"
},
{
"label": "GLM-5",
"cells": [
{
"glyph": "zai"
},
{
"value": 77.8
},
{
"value": 1.0
},
{
"value": 3.2
}
],
"section": "OPEN WEIGHTS"
},
{
"label": "Mistral Medium 3.5",
"cells": [
{
"glyph": "mistral"
},
{
"value": 77.6
},
{
"value": 1.5
},
{
"value": 7.5
}
],
"section": "OPEN WEIGHTS"
}
],
"sections": [
"FRONTIER · CLOSED WEIGHTS",
"OPEN WEIGHTS"
],
"notes": "SWE-bench Verified % · USD per Mtok · current flagships, jun 2026 · sources: vals.ai · artificialanalysis.ai · model cards"
}
JSON
--markdown-out on the CLI, respond:"json" over HTTP, render_target="markdown" over MCP.Hyperweave parses agent session telemetry into a portable receipts that include model usage, tool calls stats, token spend, and context window visualization. Install the hook once and every session emits one:
uv tool install hyperweave # or: pip install hyperweave
hyperweave install-hook
The hook reads your session's JSONL transcript from disk and detects the harness automatically (Claude Code or Codex). Theme it with any of the 8 primer themes, or the paper receipt style above.
hyperweave install-hook --genome cream # any primer theme
hyperweave install-hook --genome raw # the paper receipt
Open an issue to request a missing agent harness.
Every HyperWeave artifact is a re-ingestible object, not just an image. It carries its full spec (hw:payload) and a hash-verified digest (hwz/1 envelope), so an agent can work with it directly, never parsing pixels. Two tiers, two jobs. Here they are inside a diagram artifact:
recreate & modify: the complete spec
<hw:payload schema="diagram/1" media-type="application/json">
{
"spec": {
"title": "Service dependencies",
"subtitle": "Service dependencies · a gateway fans to domain services, each grounding on its store",
"topology": "dag",
"zones": ["subsystems"],
"nodes": [
{ "id": "web", "label": "web", "desc": "React SPA", "glyph": "react" },
{ "id": "gateway", "label": "API gateway", "role": "hero", "kind": "router" },
{ "id": "auth", "label": "Auth", "desc": "tokens", "kind": "shield" }
],
"edges": [
{ "source": "web", "target": "gateway", "relation": "assert" },
{ "source": "gateway", "target": "auth", "relation": "assert" },
{ "source": "auth", "target": "postgres", "label": "reads", "label_style": "chip", "relation": "assert" }
]
}
}
</hw:payload>
the ≈200-token digest: know what an artifact is without opening it
<hw:envelope format="hwz/1" media-type="application/json">
{
"v": "hwz/1",
"id": "sha256:48b3de6494886c678f4c8efab4f0aa105922e315f8f62145548e17935175fb11",
"k": "diagram",
"title": "Service dependencies",
"intent": "topology diagram: Service dependencies",
"state": "active",
"data": {
"pattern": "dag",
"n": 8,
"hero": "API gateway",
"nodes": { "web": "React SPA", "API gateway": "", "Auth": "tokens", "Orders": "Python svc", "Search": "query svc", "Postgres": "primary", "Kafka": "events", "Redis": "cache" },
"edges": ["web → API gateway", "API gateway → Auth", "API gateway → Orders", "API gateway → Search", "Auth → Postgres (reads)", "Orders → Postgres", "Orders → Kafka (emits)", "Search → Redis (cache)", "API gateway → Postgres (direct read)"]
},
"frames": [{ "t": "diagram", "l": "Service dependencies" }],
"prov": { "by": "hyperweave", "ver": "0.4.6", "genome": "primer.porcelain", "ts": "2026-07-15T02:01:15.613547+00:00" }
}
</hw:envelope>
The envelope is the lossy digest; only the payload round-trips.
hw:payload, edit the JSON, POST /v1/compose with it as diagram: byte-identical re-render. The envelope's id is the sha256 of the payload, so an agent verifies "this artifact really is this data" before trusting either.prov.genome: "primer.porcelain" names the aesthetics; payload plus that one string is the entire recreation recipe.Pixels for humans, compact JSON for agents. The verb algebra is the read/write grammar over the two tiers: every verb picks how much of the artifact to load, from the ≈200-token envelope to the full payload, and no verb ever parses pixels. The verbs, split two ways.
Write · mints a new artifact, returns a content-addressed link (/v1/a/{id}), never inline SVG:
Read · never mutates the artifact:
Every verb runs the same over the CLI (hyperweave {verb}), HTTP (POST /v1/{verb}), and MCP (hw_{verb}):
# compose an artifact, then read its spec straight back, no rendering
hyperweave compose matrix --spec-file table.json -g primer -o table.svg
curl -X POST https://hyperweave.app/v1/extract \
-H 'Content-Type: application/json' \
-d '{"source": "<svg or /v1/a/{id} url>", "respond": "payload"}'
Compose a bundled preset (or your own spec). This is the diagram whose payload and envelope appear above:
hyperweave compose diagram --spec-file dag-mesh -g primer --variant porcelain --surface inlay --face light -o services.svg
Transform it through the artifact itself. transform verifies the hash, applies the patch to the embedded spec, re-validates, and mints a new artifact with a lineage entry recording exactly what changed:
hyperweave transform services.svg -o services-billing.svg --patch-json '[
{"op": "add", "path": "/nodes/-", "value": {"id": "billing", "label": "Billing", "desc": "invoices", "glyph": "stripe"}},
{"op": "add", "path": "/edges/-", "value": {"source": "gateway", "target": "billing", "relation": "assert"}},
{"op": "add", "path": "/edges/-", "value": {"source": "billing", "target": "postgres", "label": "writes", "label_style": "chip", "relation": "assert", "exit": "bottom", "entry": "right"}}
]'
The result is a new artifact: new id, one more service in the fan, the envelope and lineage on stdout. -o writes the new pixels to services-billing.svg:
Flip it, and redress it. Layout is a field, so one op turns the whole graph. The look is a separate pointer, so the same graph re-renders in any variant:
hyperweave transform services-billing.svg -o services-vertical.svg \
--patch-json '[{"op": "add", "path": "/orientation", "value": "vertical"}]'
hyperweave extract services-vertical.svg --respond payload \
| hyperweave compose diagram --spec-file - --variant noir -o services-noir.svg
-o at the same path to overwrite in place; you keep the record of where it came from, not the old render.horizontal returns the landscape diagram to the pixel.porcelain to noir re-renders the same spec in a different look, structure untouched.A genome is a portable, machine-readable aesthetic specification. It encodes the complete visual identity (chromatic system, surface material, motion vocabulary, geometric form language) as a set of CSS custom properties that any agent can consume and apply consistently across every artifact type.
Four built-in genomes ship today. Custom brand dna generation via agnet SKILL.md files coming soon!
Every broken <img> URL renders the SMPTE RP 219 test pattern with ERR_NNN matching the HTTP status, instead of a browser broken-image icon.
Surface modes. A genome renders onto one of three surfaces: plate (opaque, its own background), inlay (bare, borrows the host page's light/dark), or twin (opaque and scheme-aware). Standalone, slide, and raster destinations take plate. For a GitHub README, bake a pair instead of shipping one scheme-adaptive file: GitHub serves README images through Camo as a plain <img>, so a prefers-color-scheme rule inside the SVG answers to the reader's operating system, not the GitHub theme toggle. --face light|dark bakes one scheme per file and <picture> chooses between them. The CLI exposes --surface/--ground/--palette, and --faces writes both files in one call (<out>-light.svg / <out>-dark.svg).
uv add hyperweave # CLI + SVG rendering (the base)
uv add 'hyperweave[serve]' # + HTTP server (hyperweave serve)
uv add 'hyperweave[mcp]' # + MCP server (hyperweave mcp)
uv add 'hyperweave[all]' # + both servers
# or swap `uv add` for `pip install`
uv tool install hyperweave # standalone `hw` CLI: uv provisions Python itself
Requires Python 3.10+
Four interfaces, one pipeline. Every path produces the same artifact through the same compositor.
{
"mcpServers": {
"hyperweave": {
"command": "hyperweave",
"args": ["mcp"]
}
}
}
# Static badge
hw_compose(type="badge", title="BUILD", value="passing", genome="brutalist")
# Data-driven badge - unified token grammar (gh:owner/repo.metric, pypi:pkg.metric, ...)
hw_compose(type="badge", title="STARS", data="gh:anthropics/claude-code.stars", genome="brutalist")
# Strip with multiple live metrics
hw_compose(type="strip", title="readme-ai",
data="gh:eli64s/readme-ai.stars,gh:eli64s/readme-ai.forks,pypi:readmeai.version",
genome="chrome")
# Marquee with mixed text + live tokens
hw_compose(type="marquee",
data="text:NEW RELEASE,gh:anthropics/claude-code.stars,text:DOWNLOAD",
genome="brutalist")
# Read or edit an existing artifact - the verb algebra
hw_extract(svg_or_url="<svg or /v1/a/{id} url>", respond="payload")
hw_transform(svg_or_id="<svg or /v1/a/{id} url>",
mutations=[{"op": "replace", "path": "/title", "value": "SHIPPED"}])
# Return the SVG bytes inline instead of a hosted url (default respond="url")
hw_compose(type="badge", title="BUILD", value="passing", genome="brutalist", respond="svg")
hw_discover(what="all") # the capability registry; full agent contract at /llms-full.txt
# Badge
hyperweave compose badge "build" "passing" --genome brutalist
# Strip with metrics
hyperweave compose strip "readme-ai" "STARS:2.9k,FORKS:278" -g brutalist
# Live data through the unified --data token grammar
hyperweave compose badge "STARS" --data 'gh:anthropics/claude-code.stars' -g brutalist
# Marquee with mixed text + live tokens
hyperweave compose marquee --data 'text:NEW RELEASE,gh:owner/repo.stars,text:DOWNLOAD' -g brutalist
# Session receipt from an agent transcript (Claude Code / Codex)
hyperweave compose receipt session.jsonl -o receipt.svg
# Validate a spec without rendering
hyperweave validate spec.json
# Profile card (live GitHub data, path-segment identity; 'stats' stays an alias)
hyperweave compose card eli64s -g chrome -o card.svg
# Star history chart
hyperweave compose chart stars eli64s/readme-ai -g brutalist -o chart.svg
# Custom genome from a local JSON file (validated against the profile contract)
hyperweave compose badge "DEPLOY" "live" --genome-file ./my-genome.json
hyperweave validate-genome ./my-genome.json
# The verbs: read or transform any artifact by handle, file, URL, or digest
hyperweave extract diagram.svg # the hw:payload seed as JSON
hyperweave diff v1.svg v2.svg --exit-code # structural diff, git-style exit
hyperweave verify diagram.svg # payload ↔ envelope integrity
hyperweave query diagram.svg 'nodes[0].label' # read one field
hyperweave transform diagram.svg --patch patch.json # mint a new artifact + lineage
The same CLI runs as a machine-readable loop: learn what the install can do, validate before composing, compose with an inspection record, and say why each edit happened.
# Capability capsule for an agent context: caps, legality, vocabulary, presets + a digest
hyperweave discover --agent
hyperweave discover --agent --topology hub # scoped to one topology family
# Install readiness before composing: formats, fonts, genomes, telemetry wiring
hyperweave doctor
# Machine-readable validation report, the same report every surface returns
hyperweave validate spec.json --json
# Proof sidecars beside the SVG: measured geometry, diagnostics, verdicts,
# a motion-stripped resting frame, and a png when the raster extra is installed
hyperweave compose diagram --spec-file pipeline-head -o out.svg --proof
# One bounded JSON report on stdout instead of SVG bytes: ok, artifact, integrity, diagnostics, next
hyperweave compose badge build passing --respond report
# Say why a patch happened; the reason is recorded in the new artifact's lineage
hyperweave transform out.svg --patch patch.json --intent "rename entry node"
# URL grammar: /v1/{type}/{title}/{value}/{genome}.{motion}
curl 'https://hyperweave.app/v1/strip/readme-ai/brutalist.static?value=STARS:2.9k,FORKS:278'
# Live data via the unified ?data= grammar (works on badge / strip / marquee)
curl 'https://hyperweave.app/v1/badge/STARS/chrome.static?data=gh:anthropics/claude-code.stars'
curl 'https://hyperweave.app/v1/strip/readme-ai/brutalist.static?data=gh:eli64s/readme-ai.stars,gh:eli64s/readme-ai.forks'
curl 'https://hyperweave.app/v1/marquee/SCROLL/brutalist.static?data=text:NEW%20RELEASE,gh:anthropics/claude-code.stars'
# Chromatic variants (automata: 16 solo tones, pair any two via &pair=...; chrome: horizon/abyssal/lightning/graphite/moth)
curl 'https://hyperweave.app/v1/badge/PYPI/automata.static?variant=teal&pair=violet&data=pypi:hyperweave.version'
curl 'https://hyperweave.app/v1/badge/build/passing/automata.static?size=compact'
# Genome-themed dividers
curl 'https://hyperweave.app/v1/divider/band/chrome.static'
curl 'https://hyperweave.app/v1/divider/seam/brutalist.static'
curl 'https://hyperweave.app/v1/divider/dissolve/automata.static'
# Genome-agnostic dividers
curl 'https://hyperweave.app/a/inneraura/dividers/zeropoint'
# Structured frames: /v1/{matrix|diagram}/{preset}/{genome}.{motion}
# (preset 'custom' takes a base64url ?spec=)
curl 'https://hyperweave.app/v1/matrix/connectors/primer.static?variant=porcelain'
curl 'https://hyperweave.app/v1/diagram/pipeline-head/primer.static?variant=porcelain'
# POST compose
curl -X POST https://hyperweave.app/v1/compose \
-H "Content-Type: application/json" \
-d '{"type":"strip","title":"hyperweave","genome":"brutalist","value":"STARS:2.9k"}'
# Verb algebra over an existing artifact: extract · verify · transform · diff · query
curl -X POST https://hyperweave.app/v1/extract \
-H "Content-Type: application/json" \
-d '{"source":"<svg or /v1/a/{id} url>","respond":"payload"}'
# Local server
hyperweave serve --port 8000
Compose once, export to any of these (same artifact, same metadata):
Visual CLI for agents. Deterministic SVG diagrams, tables, and charts with embedded structured metadata. Zero JavaScript. Renders anywhere markdown does.
Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Hyperweave se ejecuta localmente por stdio.
Última comprobación: 2026-10-28. Visual CLI for agents. Deterministic SVG diagrams, tables, and charts with embedded structured metadata. Zero JavaScript. Renders anywhere markdown does.
