Connects AI clients to a remote Vaultbase backend via a stdio-to-HTTP bridge for managing records, collections, and SQL.
Also known as vaultbase-sh/mcp, mcp, @vaultbase/mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.2
- Last commit
- Nov 11, 2026
- License
- MIT
What is Vaultbase MCP?
Vaultbase connects AI clients to a remote Vaultbase backend via a stdio-to-HTTP bridge for managing records, collections, and SQL.
Summary generated from the project's README
About Vaultbase MCP server
Managing remote database records and collections through AI clients like Claude Desktop or Cursor is what this bridge enables. It acts as a communication layer that connects local MCP clients to a remote Vaultbase backend by translating stdio signals into HTTP and SSE transport. This setup is ideal for teams that want to access a centralized deployment without installing the full Vaultbase binary on every individual developer machine.
To use the bridge, you must provide a VAULTBASE_URL and a VAULTBASE_MCP_TOKEN via environment variables. The package is written in TypeScript and runs on Node 18 or higher using npx. Because the bridge only frames messages without rewriting them, all core functionality including tools, resources, prompts, and audit logging remains managed directly by the remote Vaultbase server.
What you can do with it
- 1Access remote data via AI editorsConnect an AI-powered code editor to a centralized Vaultbase deployment using the stdio-to-HTTP bridge.
- 2Centralize database access for teamsAvoid installing the Vaultbase binary on every developer machine by connecting to a remote server.
Written from the project's README. Every use case is checked against a quote from it.
How to install Vaultbase MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Vaultbase MCP in Claude Code
$ claude mcp add --env 'VAULTBASE_MCP_TOKEN=<YOUR_VAULTBASE_MCP_TOKEN>' --env 'VAULTBASE_URL=<VAULTBASE_URL>' mcp -- npx -y @vaultbase/mcpInstall Vaultbase MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@vaultbase/mcp"
],
"env": {
"VAULTBASE_MCP_TOKEN": "<YOUR_VAULTBASE_MCP_TOKEN>",
"VAULTBASE_URL": "<VAULTBASE_URL>"
}
}
}
}Install Vaultbase MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vaultbase/mcp"
],
"env": {
"VAULTBASE_MCP_TOKEN": "<YOUR_VAULTBASE_MCP_TOKEN>",
"VAULTBASE_URL": "<VAULTBASE_URL>"
}
}
}
}Install Vaultbase MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@vaultbase/mcp"],"env":{"VAULTBASE_MCP_TOKEN":"<YOUR_VAULTBASE_MCP_TOKEN>","VAULTBASE_URL":"<VAULTBASE_URL>"}}'Install Vaultbase MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@vaultbase/mcp"
],
"env": {
"VAULTBASE_MCP_TOKEN": "<YOUR_VAULTBASE_MCP_TOKEN>",
"VAULTBASE_URL": "<VAULTBASE_URL>"
}
}
}
}Install Vaultbase MCP in Codex
$ codex mcp add mcp --env 'VAULTBASE_MCP_TOKEN=<YOUR_VAULTBASE_MCP_TOKEN>' --env 'VAULTBASE_URL=<VAULTBASE_URL>' -- npx -y @vaultbase/mcpInstall Vaultbase MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@vaultbase/mcp"] [mcp_servers.mcp.env] VAULTBASE_MCP_TOKEN = "<YOUR_VAULTBASE_MCP_TOKEN>" VAULTBASE_URL = "<VAULTBASE_URL>"
Install Vaultbase MCP in Gemini CLI
$ gemini mcp add -s user -e 'VAULTBASE_MCP_TOKEN=<YOUR_VAULTBASE_MCP_TOKEN>' -e 'VAULTBASE_URL=<VAULTBASE_URL>' mcp npx -- -y @vaultbase/mcpInstall Vaultbase MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@vaultbase/mcp"
],
"env": {
"VAULTBASE_MCP_TOKEN": "<YOUR_VAULTBASE_MCP_TOKEN>",
"VAULTBASE_URL": "<VAULTBASE_URL>"
}
}
}
}Configuration
VAULTBASE_MCP_TOKENRequiredSecretA Vaultbase API token with an mcp scope (mcp:read is enough to read data)
VAULTBASE_URLRequiredAddress of your Vaultbase server, for example https://api.example.com
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablevaultbase-sh/mcp is public and reachablegithub.com/vaultbase-sh/mcp ↗Pass
- Package names this repository as its source@vaultbase/mcp names vaultbase-sh/mcp as sourcenpmjs.com/package/@vaultbase/mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-11github.com/vaultbase-sh/mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @vaultbase/mcpPass
- No critical advisory in the package or its dependenciesthe package checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubStdio↔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
Vaultbase MCP questions
How do I add Vaultbase MCP to Claude Code?
Run claude mcp add --env 'VAULTBASE_MCP_TOKEN=<YOUR_VAULTBASE_MCP_TOKEN>' --env 'VAULTBASE_URL=<VAULTBASE_URL>' mcp -- npx -y @vaultbase/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Vaultbase MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What are the system requirements for the bridge?
The package is written in pure TypeScript and requires Node.js version 18 or higher.
Does the bridge modify MCP messages?
No, the bridge only frames messages for the transport layer; all MCP semantics like tools and resources are handled by the Vaultbase server.