Dvt

dev.dvtPublished by dvt.devOfficial publisherv0.7.37Updated Oct 24, 2026

Dashboards as data. Author, validate, render, and share dvt dashboards from any MCP client.

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

Remote MCP endpoint for dvt that lets an assistant author, validate, render and share spec-driven data dashboards — though the service is reported shut down.

What you can do
  • Author, read, write and validate dvt dashboard specs as versioned JSON
  • Design, render and apply dashboards against a live dvt instance
  • List and verify dashboards on a connected dvt Gallery workspace
  • Retrieve the engine's own spec-authoring skill resource so authoring matches the engine's schema version
  • Critique specs and built dashboards for layout, visual design and narrative coherence
When to use it
Intended for data teams that want an assistant to build and review dvt dashboards through a spec-driven workflow. Check first whether the hosted endpoint is still reachable: the README states dvt was shut down in November 2026 and the hosted endpoint is offline.
Requirements
A remote MCP endpoint (hosted Gallery or a direct engine URL) and an OAuth bearer token in the Authorization header, created as a dvt API key in a dvt Gallery workspace. The README also describes a Claude Code plugin with a connect command; no local package is declared.
Before you install
The Authorization header carries a dvt API key that grants whatever scopes it holds; keep it out of shared files. The README reports the service was shut down and the hosted endpoint is offline, so the server may not connect at all. Dashboard writes and applies change data on the connected instance.

Installation

In SourceWeft

  1. Open Dvt 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/dev.dvt%2Fdvt/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": {
    "dvt": {
      "type": "http",
      "url": "https://mcp.dvt.dev/mcp"
    }
  }
}

README

dvt-plugin

Deprecated — dvt has been shut down (November 2026). The hosted endpoint mcp.dvt.dev is offline, so this plugin can no longer connect to dvt Gallery. This repository is being archived and is kept for reference only. To clean up, run /plugin uninstall dvt@dvt-plugin, then remove the connector /dvt:connect added: claude mcp remove dvt --scope user.

The dvt Claude Code plugin — a thin client for dvt (data viz tool).

dvt is an AI-native approach to data visualization: data teams design, generate, and deploy dashboards through a spec-driven workflow, where a dashboard is a versioned JSON spec that humans and agents author the same way. This plugin brings that workflow into Claude Code. It is a thin client — it carries no data and no compute. It bundles two things:

  • the dvt dashboard-spec authoring skill, so an agent knows how to read, write, and validate a dvt dashboard spec; and
  • an MCP client pointed at a dvt endpoint, so the agent can design, validate, render, and apply specs against a live dvt instance.

The plugin is open and ungated. It contains no secret and no entitlement logic — your access is governed entirely by the dvt endpoint and the key you connect with.

Install

In any Claude Code session:

/plugin marketplace add getdvt/dvt-plugin/plugin install dvt@dvt-plugin

Then restart Claude Code (plugins don't hot-load).

Connect

After installing, run /dvt:connect and follow the prompts. The plugin talks to a dvt endpoint over MCP; point it at one of two targets:

  • dvt Gallery (hosted) — connect to https://mcp.dvt.dev/mcp with a Gallery API key. Mint a key in your dvt workspace at https://app.dvt.dev/app/api-keys, then paste the dvt_live_… value when /dvt:connect prompts for it. The key is stored by Claude Code at user scope, never committed here.
  • Direct engine URL — point the client at a dvt engine URL you already have (e.g. http://localhost:8001/mcp).

/dvt:connect registers a user-scoped dvt MCP server with your endpoint and (for Gallery) your key, then verifies the connection by listing your dashboards. Once connected, just ask the agent to build a dashboard.

The plugin bundles the authoring skill so it works offline, but a connected engine also serves its own copy — matched to the spec version that engine speaks — at the MCP Resource dvt://skill/spec-authoring. When that revision is at least as new as the bundled one, /dvt:connect prefers it for the session (and tells you), so authoring stays correct as the schema evolves without a re-install. If the engine doesn't serve it, the bundled copy is always a valid fallback (ADR-0047).

The plugin never embeds a key or any entitlement check. What you can do is decided by your dvt endpoint and the scopes on the key you provide.

What's inside

.claude-plugin/  marketplace.json              single-plugin marketplace so /plugin marketplace add resolves this repoplugins/dvt/  .claude-plugin/plugin.json    plugin manifest (name "dvt", semver)  commands/connect.md           /dvt:connect — first-run setup + verify (registers the MCP server)  commands/dvt-review.md        /dvt:dvt-review — critique a spec or a built dashboard, GO / REVISE  agents/dvt-layout-critic.md   layout, visual design, readability — PASS / NEEDS ATTENTION / SIGNIFICANT ISSUES  agents/dvt-narrative-critic.md  analytical story coherence — COHERENT / PARTIALLY COHERENT / INCOHERENT  skills/dvt-spec-author/       dvt dashboard-spec authoring skill (generated at publish time)  icon.svg  README.md  SETUP.md                      connecting from Cowork (GUI-only environments).github/workflows/  plugin-release.yml            tags each published version v<semver>RELEASING.md                    version + tag convention (semver in plugin.json)LICENSE                         Apache-2.0

This repo is publish-only — do not send pull requests here. Every file above is rendered from plugins/** in the private getdvt/dvt repo and pushed by the dvt-publisher GitHub App, so a commit made directly to this repo is overwritten by the next publish. Issues and discussions are closed for the same reason. To propose a change, talk to us at dvt.dev. Security reports go to [email protected] (also dvt.dev/.well-known/security.txt), or via GitHub private vulnerability reporting on this repo.

The bundled spec-authoring skill has a single canonical source in getdvt/dvt (web/public/dvt-spec-authoring-skill.md plus its references/ dir) and is generated into the tree at publish time, so the published copy cannot drift from it. SKILL.md is the authoring method; references/ holds the detail it loads on demand (panel types, layout modes, theme, data sources, exports and email).

Maintainers: see RELEASING.md for the version + tag flow.

License

Apache-2.0. dvt is an open funnel artifact — this plugin matches the spec and SDK licensing.

Source: README.md at commit c82b2cd

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

35
  1. v0.7.37LatestOct 17, 2026
  2. v0.7.36Oct 16, 2026
  3. v0.7.33Oct 16, 2026
  4. v0.7.32Oct 16, 2026
  5. v0.7.29Oct 16, 2026
  6. v0.7.27Oct 15, 2026
  7. v0.7.25Oct 13, 2026
  8. v0.7.24Oct 13, 2026
  9. v0.7.23Oct 13, 2026
  10. v0.7.18Oct 13, 2026
  11. v0.7.15Oct 12, 2026
  12. v0.7.14Oct 12, 2026
  13. v0.7.9Oct 12, 2026
  14. v0.7.8Oct 11, 2026
  15. v0.7.4Oct 10, 2026
  16. v0.7.3Oct 7, 2026
  17. v0.7.1Oct 7, 2026
  18. v0.7.0Oct 3, 2026
  19. v0.6.5Oct 2, 2026
  20. v0.6.4Oct 1, 2026
  21. v0.6.3Sep 28, 2026
  22. v0.6.2Sep 28, 2026
  23. v0.6.1Sep 27, 2026
  24. v0.6.0Sep 25, 2026
  25. v0.5.59Sep 25, 2026
  26. v0.5.58Sep 24, 2026
  27. v0.5.57Sep 23, 2026
  28. v0.5.55Sep 23, 2026
  29. v0.5.54Sep 21, 2026
  30. v0.5.53Sep 20, 2026
  31. v0.5.49Sep 20, 2026
  32. v0.5.48Sep 19, 2026
  33. v0.5.47Sep 19, 2026
  34. v0.5.46Sep 18, 2026
  35. v0.5.45Sep 16, 2026

Score

85% 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