Agent-first secrets vault. Store, rotate, and share credentials from chat. 16 tools.
Connect Secretcarousel to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Agent-first secrets vault. Store, rotate, and share credentials from chat. 16 tools. The secretcarousel mcp server is what makes that connection.
Your agent touches credentials all day — a database URL here, an API key there — and the moment its context resets, those secrets end up pasted into a .env file in Slack, echoed into a log, or left in the transcript. You become the vault. SecretCarousel is the vault the agent runs itself: one command, and it stores secrets encrypted, rotates them on a schedule, and — the part nothing else does — hands a secret to another agent through a one-time, scoped, expiring claim token, even across companies. No plain-text value ever crosses the boundary.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: SC_API_KEY, DATABASE_URL, SIGNING_KEY, YOUR_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by jyswee; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Secretcarousel's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"secretcarousel": {
"command": "npx",
"args": ["-y", "secretcarousel"],
"env": {
"SC_API_KEY": "your-value",
"DATABASE_URL": "your-value",
"SIGNING_KEY": "your-value",
"YOUR_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| SC_API_KEY | Credential the server authenticates with. | Yes |
| DATABASE_URL | Endpoint or connection string the server talks to. | Yes |
| SIGNING_KEY | Credential the server authenticates with. | Yes |
| YOUR_KEY | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.