Securely manage encrypted secrets for Claude Code through MCP with file injection, access rules, audit logs, and session controls.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent โ or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag โ we're steadily working through the catalog.
๐ก Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Securecode MCP.
onboardGuided setup: signup, import, API key, config, SDK
get-secretGet a secret (injected to file by default, `reveal: true` to show to AI)
list-secretsList all secrets with tags and expiry status
create-secretCreate a new secret
update-secretUpdate value, description, or tags
delete-secretDelete a secret
MCP Server for SecureCodeHQ. Lets Claude Code access your secrets securely without ever seeing them.
Then tell Claude Code:
The onboard tool walks you through account creation, secret import, and configuration. Takes about 2 minutes.
Your secrets (API keys, tokens, passwords) are encrypted with AES-256 and stored in SecureCode. Claude Code accesses them via MCP, but the actual values never appear in the chat.
When Claude reads a secret, the value is written to a local file on your machine. The AI gets the file path but never sees the raw value. This is inject mode, the default.
| Tool | What it does |
|---|---|
onboard | Guided setup: signup, import, API key, config, SDK |
get-secret | Get a secret (injected to file by default, reveal: true to show to AI) |
list-secrets | List all secrets with tags and expiry status |
create-secret | Create a new secret |
update-secret | Update value, description, or tags |
delete-secret | Delete a secret |
renew-secret | Renew expired secrets or change TTL |
import-env | Import .env via secure web window (values never pass through AI) |
export-env | Export secrets as .env or CSV |
get-status | Check plan, usage, and MCP server version |
wake-session | Unlock session with optional scope and auto-sleep timer |
sleep-session | Lock session and clean injected files |
session-status | Check session state and time remaining |
byebye | Lock session + clean all secrets from disk |
get-active-rules | List active MCP access rules (read-only) |
security-check | Post-setup security hardening checks |
help | Docs: tools, SDK, sessions, rules, troubleshooting |
Control how AI agents access your secrets with tag-based policies. Created from the dashboard, enforced server-side.
| Action | Effect |
|---|---|
| Block Always | Secret only accessible from the dashboard |
| Require Confirmation | Agent must acknowledge before accessing |
| Require Session | Requires active session (wake-session) |
| Block Models | Only allows specific AI models |
| Notify | Sends email on access (non-blocking) |
Sessions auto-sleep after configurable inactivity (default: 2 hours).
reveal: true returns value to AI (audited)The companion SDK lets your app load secrets at runtime:
MIT
Factual signals from GitHub, npm, and our automated checks โ not a rating.
No reviews yet โ be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/juanisidoro-securecode-mcp)<a href="https://allmcps.com/mcp/juanisidoro-securecode-mcp"><img src="https://allmcps.com/api/badge/juanisidoro-securecode-mcp?style=directory" alt="Securecode MCP on AllMCPs" /></a>