AgentVault
MCP server for AI-native credential management, enabling agents to securely store, retrieve, and manage API keys with encryption, spending budgets, and audit logging.
README
AgentVault
AI-native credential management for autonomous agents. Store API keys with column-level Fernet encryption, issue unique avk_ keys to registered agent identities, proxy decrypted values with TTL, enforce per-agent spending budgets, log every access, and expose everything as an MCP server.
- Live API: https://agentvault-api-production.up.railway.app
- Docs: https://agentvault-api-production.up.railway.app/docs
- Status: Production (Railway + Postgres + Stripe live)
Why
Autonomous agents need API keys to do anything useful — Stripe, OpenAI, SendGrid, your own internal services. Three bad options today:
- Hardcode in the agent prompt or config. Leaks in logs, can't rotate, no audit trail.
- Pass via env vars at spawn. No per-agent isolation, no budget controls, no revocation without redeploy.
- Roll your own vault. Real work — encryption at rest and in transit, audit logs, key rotation, budget tracking.
AgentVault is option 3 as a service. One avk_ key per agent. Permission patterns (["stripe_*", "openai_*"]). Daily/monthly spending caps. Full access log. MCP-native so agents can vault.get_credential("stripe_key") and get a TTL-bound decrypted value back.
Quickstart
Direct HTTP
import httpx
resp = httpx.post(
"https://agentvault-api-production.up.railway.app/api/v1/vault/get/stripe_key",
headers={"X-Agent-Key": "avk_..."},
params={"cost": 0.05},
)
stripe_key = resp.json()["value"]
MCP (Claude Desktop / Cursor / Cline)
{
"mcpServers": {
"agentvault": {
"command": "python",
"args": ["-m", "mcp_server"],
"env": {
"AGENTVAULT_API_URL": "https://agentvault-api-production.up.railway.app",
"AGENTVAULT_AGENT_KEY": "avk_..."
}
}
}
}
Then in Claude: vault.get_credential("stripe_key") returns the decrypted value.
How it works
- Column-level Fernet encryption — credentials are encrypted with
VAULT_ENCRYPTION_KEYbefore they hit the database. Stronger than at-rest disk encryption alone. avk_agent keys — SHA-256 hashed at rest, never stored plaintext. Recognizable prefix likesk_live_/whsec_.- Permission patterns —
["stripe_*", "openai_*"]scopes an agent without a full policy engine. fnmatch-based. - Budget enforcement — daily and monthly caps per agent.
/vault/get?cost=0.05records the spend; 429 once the cap is hit. - Audit log — every access (success or denied) goes into
credential_access_logswith IP, user-agent, error reason. - MCP server —
mcp_server/exposeslist_credentials,get_credential,vault_status,set_budget,view_audit_logas stdio MCP tools.
Pricing
| Tier | $/mo | Agents | Credentials | Audit | Rotation | Budgets | Team |
|---|---|---|---|---|---|---|---|
| Free | $0 | 3 | 10 | – | – | – | – |
| Pro | $49 | 25 | 100 | ✓ | ✓ | – | – |
| Business | $149 | ∞ | ∞ | ✓ | ✓ | ✓ | ✓ |
| Enterprise | $499 | ∞ | ∞ | ✓ | ✓ | ✓ | ✓ + SSO + compliance |
Self-host
git clone https://github.com/bch1212/agentvault
cd agentvault
pip install -r requirements.txt
cp .env.example .env # then fill in VAULT_ENCRYPTION_KEY and DATABASE_URL
python -m api.main
Run tests:
python -m pytest -v # 34 tests
Deploy to Railway:
bash deploy.sh
Architecture
api/
├── main.py # FastAPI + lifespan
├── database.py # Async SQLAlchemy (auto-rewrites postgresql:// → postgresql+asyncpg://)
├── services/
│ ├── encryption.py # Fernet encrypt/decrypt
│ ├── auth.py # avk_ key gen + SHA-256 hashing
│ ├── budget.py # Per-agent spend tracking
│ ├── audit.py # Access log
│ └── alerts.py # SendGrid alerts
├── middleware/ # X-Agent-Key + Bearer auth
└── routers/ # users, agents, credentials, vault, audit, budgets, billing
mcp_server/ # FastMCP stdio server
tests/ # 34 tests, SQLite in-memory
License
MIT.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.