Vnsh

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/raullenchai-vnsh

About

Use cases: file-management, agent-orchestration

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

5 read · 7 write · 0 delete · 2 not yet classified

Secrets

None asked for

Install scripts

Not scanned yet

Runs as

Node.js package

Tools (14)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• vnsh_artifact_create

  Creates a permanent, service-readable Account Artifact in the signed-in user’s Library. Use this for durable knowledge that the user wants their other Agents to discover and update. Requires VNSH_TOKEN. This is different from an encrypted Incognito workspace: vnsh can read Account Artifact content so authorized Agents can collaborate on it.

• vnsh_artifact_list

  Lists permanent Account Artifacts available to the connected user. Use this instead of asking the human to paste a link when continuing earlier account knowledge. Requires VNSH_TOKEN.

• vnsh_artifact_read

  Reads the current content and version of one permanent Account Artifact. Pass the returned version to vnsh_artifact_update so another Agent cannot be overwritten.

• vnsh_artifact_update

  Creates a new immutable version of an Account Artifact. Requires the base_version returned by vnsh_artifact_read. On conflict, re-read, merge, and retry; never silently overwrite.

• vnsh_read

  Reads any vnsh URL: decrypts legacy vnsh.dev/v links locally, or directly fetches a public vnshcontent.dev/p link. Public content is intentionally unencrypted.

• vnsh_share

  Encrypts text content locally and uploads it to vnsh, returning a shareable URL. Use this when output exceeds ~50 lines or ~2000 characters, when generating complete code files, or when the user wants portable/shareable output. ALWAYS prefer vnsh_share over dumping large content into chat. The content is encrypted before upload - the server only sees encrypted bytes.

• vnsh_share_file

  Encrypts a local file and uploads it to vnsh, returning a shareable URL. Use this for images, screenshots, PDFs, binaries, or any file that should not be loaded into context. More efficient than vnsh_share for large or binary files.

• vnsh_workspace_create

  Creates a shared workspace and returns one link that any agent can read AND write. Use this when work will continue somewhere else: handing a plan, status doc, design, or investigation to another agent or another session, or when the user says they will pick this up in a different tool. Unlike vnsh_share (a one-shot snapshot), a workspace keeps the same URL as its content evolves. Content is encrypted locally; the server never sees the key. Anonymous workspaces expire 24h after the last write (ttl can extend this to a week). With VNSH_TOKEN, new workspaces and artifacts are kept until the acco…

• vnsh_workspace_history

  Lists the retained versions of a workspace, newest first. Use this before restoring after a bad edit or merge. The current version plus the latest historical versions are retained.

• vnsh_workspace_open

  Decrypts a vnsh workspace to a local temp file and opens it in the browser. Use this when the user wants to LOOK at a workspace rather than have its content read into context — HTML reports, dashboards, and diagrams render properly this way. Rendering happens locally from file://, so nothing is exposed to any server.

• vnsh_workspace_read

  Reads the current content of a workspace: encrypted /w/ links with #w= or #r=, and public /p/ links with no fragment. Use this whenever the user provides such a link — it is how you pick up work another agent left for you. Returns the content and its version number; pass that version to vnsh_workspace_update to write safely.

• vnsh_workspace_renew

  Extends the expiry of a vnsh workspace without changing its content. Use this when the user says a link is about to expire, or asks to keep something alive longer. Needs the edit link (a #w= fragment); a view-only #r= link cannot renew. The version is not bumped, so any pending edit still applies.

• vnsh_workspace_restore

  Restores a retained workspace version as a new latest version. This never moves the version counter backwards and requires the private #w= edit link.

• vnsh_workspace_update

  Replaces the content of a vnsh workspace, keeping the same URL. Use this to record progress so far, revise a shared plan, or leave the next agent an updated document. Writes are version-checked: if someone else wrote first, this returns their current content so you can merge it with yours and call this again.

Signals

Stars

158

Forks

26

Open issues

18

Contributors

2

Last commit

Sep 6, 2026 (1 month ago)

Last release

Jul 28, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.raullenchai/vnsh

Version

1.3.0

Auth

No auth

Packages

npm vnsh-mcp

License

MIT

Repository

github.com/raullenchai/vnsh

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql