Skip to content

vaultbase-sh/mcp

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

@vaultbase/mcp

Stdio↔HTTP bridge for the Vaultbase MCP server.

Vaultbase ships a first-party Model Context Protocol server. When you run vaultbase locally you can wire it up over stdio with vaultbase mcp. When the deployment lives on a remote host (or you don't want to install the binary on every developer machine), this package bridges the local MCP client (Claude Desktop, Cursor, Continue, Cline, Zed, …) to Vaultbase's HTTP+SSE transport at /api/v1/mcp/.

client (stdio) ⇄ @vaultbase/mcp ⇄ vaultbase (HTTPS + SSE)

Pure TypeScript, ships as a single npm bin, requires Node ≥ 18. No Bun runtime needed on the client.

Install

npm install -g @vaultbase/mcp
# or use directly via npx
npx @vaultbase/mcp --url https://api.example.com --token vbat_…

Claude Desktop config

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "vaultbase": {
      "command": "npx",
      "args": ["-y", "@vaultbase/mcp"],
      "env": {
        "VAULTBASE_URL": "https://api.example.com",
        "VAULTBASE_MCP_TOKEN": "vbat_eyJhbGciOiJIUzI1NiIs…"
      }
    }
  }
}

Mint a token via the admin UI (/_/api-tokens) or the CLI on the host:

vaultbase token mint --name "Claude Desktop" --scope mcp:read --ttl 1y

Cursor / Continue / Cline / Zed

Same pattern — each editor has an MCP-server config block. Use command: "npx", args: ["-y", "@vaultbase/mcp"], supply VAULTBASE_URL + VAULTBASE_MCP_TOKEN env vars.

Programmatic usage

import { runBridge } from "@vaultbase/mcp";

const handle = runBridge({
  url: "https://api.example.com",
  token: process.env.VAULTBASE_MCP_TOKEN!,
});
await handle.done;

The bridge does not parse or rewrite MCP messages — it only frames them for whichever transport is on the other side. All MCP semantics (tools, resources, prompts, scope enforcement, audit logging) stay in the Vaultbase server.

Compatibility

@vaultbase/mcp Vaultbase server
0.1.x >= 0.10.0

The Phase-3 HTTP+SSE transport ships in Vaultbase 0.10. Earlier servers only speak stdio — point Claude Desktop directly at the vaultbase binary instead.

License

MIT — © 2026 Vaultbase contributors

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors