Designvault

net.designvaultPublished by designvault.netv0.1.3Updated Oct 24, 2026

Search, browse and manage your DesignVault design-asset library from any MCP client.

VerifiedSTDIODesktop onlyFiles & StorageKnowledge & Memory

Overview

AI-generated overview

An MCP server for DesignVault that lets an assistant search, browse and manage an organization's design-asset library.

What you can do
Search and browse assets in a DesignVault design-asset library. Manage existing asset records, with create, update and delete tools registered only when write mode is explicitly enabled. Point the client at a preview deployment or local development API through an environment variable.
When to use it
Use it when you want an assistant to look up, browse or tidy a DesignVault asset library without switching to the web interface; enable the write tools only if the assistant should also create, update or delete assets.
Requirements
Runs locally over stdio from the npm package designvault-mcp, so Node.js is needed. Requires the DESIGNVAULT_API_KEY environment variable, an organization-level API key generated under Settings → API keys. Optional DESIGNVAULT_BASE_URL overrides the API address, which defaults to the DesignVault service and needs network access.
Before you install
Requires an organization-level API key in DESIGNVAULT_API_KEY, so keep it private. Write tools are off by default; setting DESIGNVAULT_ENABLE_WRITE lets the assistant create, update and delete assets, which changes shared library data, so enable it only when needed. DESIGNVAULT_BASE_URL can point at a custom or local endpoint, so confirm it is trusted.

Installation

In SourceWeft

  1. Open Designvault 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

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • 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 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.