Log inSubmit server
Vnsh logo

Vnsh

Shares encrypted, versioned workspaces and one-shot content between AI agents with 24-hour expiration.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Vnsh

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "vnsh": {
      "command": "npx",
      "args": [
        "-y",
        "vnsh-mcp@1.9.0"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 14 tools correctly (Today).

Overview

The vnsh MCP server gives AI agents shared workspaces for reading, writing, versioning, and handing off content through links. It runs as an npm-based MCP process and exposes workspace, artifact, sharing, history, restore, and renewal operations. Encrypted workspaces keep keys in URL fragments so the service stores ciphertext, while public workspaces trade privacy for ordinary HTTP access. Reach for it when multiple agents or people need to work from the same evolving document instead of exchanging snapshots.

Use cases

  • Share incident reports between agents and people
  • Hand off evolving documents between AI coding tools
  • Upload build output or failing test logs from CI
  • Exchange files through encrypted, expiring links
  • Restore an earlier workspace version after an edit

Key features

  • Encrypted AES-256-GCM workspaces
  • Version-checked concurrent updates
  • Workspace history and restoration
  • One-shot content and file sharing
  • Configurable expiration and renewal
  • Public HTTP-readable workspaces

Tools14

What Vnsh lets your agent do. Expand a tool for its parameters.

Verified live~2.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/5 checks healthy over the last 40d

What it can do

From the 14 tools this server returned when we ran it.

Makes network requests · 5Read-only tools · 14
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age272 days
Maintainers1

Observed 2026-10-24 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · vnsh-mcp@1.9.0 (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars158Stargazers on the source repository.
npm downloads323Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed14Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Vnsh works

What vnsh does

The vnsh MCP server provides a shared address for content that AI agents and people can read or update. It supports persistent workspaces as well as one-shot links for individual content. A workspace keeps versions at one URL, allowing a later agent to continue from the current document rather than creating another copy.

Encrypted workspaces are protected in the client before upload. The root secret stays in the URL fragment, which is not sent in HTTP requests. vnsh stores ciphertext, an encrypted filename, and a SHA-256 hash derived from the write token. Workspaces are deleted 24 hours after the last edit by default, and their lifetime can be extended within the documented limit.

The service also supports public workspaces. These are stored and served as ordinary documents that an HTTP client can read without a key, but vnsh can read their contents. Public visibility is selected when the workspace is created and is not the default.

How it works

The vnsh MCP server uses separate derived values for encryption and writing. A random root secret produces an AES-256-GCM content key and a write token through HKDF-SHA256. The server retains only a hash of the write token, so possession of the encrypted content does not provide the key needed to decrypt it.

Each update includes the version the client previously read. An unconditional update is rejected, and an update based on an older version returns a conflict instead of silently replacing newer content. Agents can then reread the workspace, merge their changes, and retry.

View-only links carry a content key but not the root secret needed to derive the write token. Edit links carry the root secret and therefore allow both reading and writing. Public content is delivered from the separate vnshcontent.dev domain and uses a sandbox content-security policy.

Setup and configuration

Install the MCP server through npm with npx -y vnsh-mcp@1.9.0, or configure it through an MCP client such as Claude Code, Cursor, Cline, Windsurf, or Zed. The README also provides an llms.txt setup guide that agents can use to install the server and add a standing workspace instruction to their own instruction file.

The command-line package can create workspaces from files or standard input, read links, replace content without clobbering newer versions, list retained history, restore a prior version as the latest version, and initialize project instructions. The browser interface at vnsh.dev can also create links from pasted content or files.

Workspace lifetimes can be set with --ttl for up to 168 hours. The --public option creates an unencrypted workspace, while --blob explicitly creates a one-shot link. No environment variables are documented as required.

Tools and capabilities

The vnsh MCP server exposes tools for:

  • Creating, listing, reading, and updating artifacts.
  • Creating, reading, updating, opening, and renewing workspaces.
  • Listing workspace history and restoring retained versions.
  • Sharing content or files through one-shot links.
  • Reading workspace, public, and legacy blob URLs.

A separate GitHub Action can upload build output or failing test logs and print a link in a job summary, but that workflow is outside the MCP server itself.

Limitations and notes

Encrypted workspace links require a client that can perform the documented key derivation and AES-256-GCM operations. The dependency-free shell installer handles one-shot links only; workspace operations require Node when the local OpenSSL does not provide the necessary cryptography.

The view-only behavior is derived from the link material rather than enforced as a server-side account permission. Anyone holding an edit link can read and write, while anyone holding a view-only link can read but not write. Public workspaces should therefore be used only for content that may be exposed to vnsh and ordinary HTTP readers.

The server does not silently merge concurrent edits. A stale write produces a conflict, so the client or agent must reread and resolve the changes. Workspace links also expire after inactivity according to their configured lifetime, with renewal available through the workspace renewal operation.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Vnsh

vnsh is an MCP server that connects AI agents to shared, expiring workspaces and one-shot content links. Its main tools create, list, read, update, open, renew, and restore workspaces, manage artifacts and history, and share or read files and content. Encrypted workspaces keep keys in URL fragments.

Install it with `npx -y vnsh-mcp@1.9.0` in an MCP client configuration. The README also provides an `llms.txt` setup guide for agents and shows a Claude Code command that registers vnsh with the client.

Yes, vnsh lists Cursor among the MCP-capable agents it can be set up for. Configure the npm-based `vnsh-mcp` process in Cursor using the client’s MCP setup flow.

vnsh requires updates to identify the version that was read. Unconditional writes are refused, and stale writes return a conflict so the agent can reread, merge, and submit an update without silently clobbering newer content.

Encrypted workspaces use client-side AES-256-GCM encryption, with keys kept in the URL fragment rather than sent to the server. Public workspaces are different: they are stored as readable documents and can be accessed by vnsh.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewVnsh AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/vnsh?style=directory)](https://allmcps.com/mcp/vnsh)
HTML Embed
<a href="https://allmcps.com/mcp/vnsh"><img src="https://allmcps.com/api/badge/vnsh?style=directory" alt="Vnsh on AllMCPs" /></a>