VaultMCP

Works with any MCP client — Claude Desktop, VS Code, Cursor, Windsurf, Zed, and more.

One vault. One MCP URL. Every IDE talks to VaultMCP — not to your raw AWS or GitHub keys.

git clone https://github.com/Axiler-Lab/vaultmcp.git cd vaultmcp cp .env.example .env

docker compose up -d postgres redis pnpm install pnpm --filter @vaultmcp/shared build pnpm db:generate # first time / after schema changes pnpm db:migrate pnpm dev:api # :3001 pnpm dev:web # :5173

One public entrypoint onport 80. API and web are not published directly.

Same config shape forCursor,Claude Desktop,VS Code,Windsurf,Zed, and other MCP clients. Use OAuth (browser login) or a personal access token from the dashboardConnecttab. Never put provider secrets in client config.

{ "mcpServers": { "vaultmcp": { "url": "https://vaultmcp.dev/mcp" } } }

{ "mcpServers": { "vaultmcp": { "url": "https://vaultmcp.dev/mcp", "headers": { "Authorization": "Bearer vmcp_…" } } } }

Self-host: replace withhttps://YOUR_HOST/mcp. Local API:http://localhost:3001/mcp.

Cursor:~/.cursor/mcp.jsonor.cursor/mcp.json. Other clients use their own MCP config path.

After auth:list_workspaces→use_workspace→ call namespaced tools (github__…,aws__…).

npx @vaultmcp-axiler/cli@latest login --token vmcp_… --url https://YOUR_HOST npx @vaultmcp-axiler/cli@latest run -w your-slug -- npm run dev

Create a PAT with theRuntime env (CLI)preset (envscope only). MCP tokens and env tokens are not interchangeable. Preferrunoverenvso secrets stay in the child process.

Secretvaluesare encrypted at rest withAES-256-GCMusing envelope encryption:

- Each workspace has its own data encryption key (DEK)
- DEKs are wrapped byVAULT_MASTER_KEY(kept out of the database)
- GCM AAD binds ciphertext to theworkspaceId, so blobs cannot be swapped across workspaces
- Decryption happens only server-side — for MCP upstream injection, or opt-in CLI export
- Secretnamesand other metadata arenotencrypted (so the UI can list and authorize without decrypting)

TreatVAULT_MASTER_KEYas a root credential. Rotate provider secrets in the UI without changing IDE config.

Also: list APIs and audit logs never return plaintext values; viewers cannot invoke secret-backed tools or export runtime env.

apps/api Gateway, OAuth, REST, upstream proxy apps/web Control plane UI packages/shared Crypto helpers + shared schemas packages/cli Local env injection CLI deploy/ Reverse proxy config docs/ Deploy, CLI, and crypto guides examples/ Upstream walkthroughs

VaultMCP is often run as a network service.AGPL-3.0-onlymeans if you modify it and offer that service over a network, you must share the corresponding source. That keeps hosted forks honest while still allowing self-hosting and contribution.

VaultMCP is an open-source project fromAxiler Labs. We’d love help from the community — issues and pull requests are very welcome, especially around security, reliability, docs, and MCP compatibility.

By contributing, you agree your work is licensed underAGPL-3.0-only, same as the rest of the repo. Never commit secrets; use.env.examplefor variable names only.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Create crafted UI components inspired by the best 21st.dev design engineers.

Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server

An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .

MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent

ALAPI MCP Tools,Call hundreds of API interfaces via MCP

AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform

MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.

APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.