SecureCode is a secrets management MCP server for securely storing, managing, and accessing sensitive data (API keys, tokens, passwords) without exposing raw values in AI conversations. Secrets are encrypted with AES-256-GCM and stored in SecureCodeHQ's cloud.

Secret Management

• Get (get-secret): Retrieves a secret by injecting its value into a local file by default (AI never sees it), or use reveal: true for audited direct access

• List (list-secrets): View all secrets with tags and expiration status — values never returned

• Create (create-secret): Store new secrets with optional tags, description, domain, and TTL

• Update (update-secret): Modify an existing secret's value, description, tags, or domain

• Renew (renew-secret): Reactivate expired secrets or change their TTL

• Delete (delete-secret): Soft-delete a secret (recoverable)

Import & Export

• Import (import-env): Securely import from .env files via a web interface (values bypass the AI)

• Export (export-env): Export secrets as a .env file or CSV

Session Management

• Wake (wake-session): Unlock secret access, optionally scoped to tags with an auto-sleep timer

• Sleep (sleep-session): Immediately lock the session

• Status (session-status): Check active state, scope restrictions, and time remaining

• Byebye (byebye): Lock session and clean all injected secret files from disk

Access Control & Security

• Active rules (get-active-rules): View tag-based MCP access rules (block, require confirmation, require session, block models, notify) — managed from the dashboard

• Security check (security-check): Analyze the project for security issues and get hardening recommendations

• All access is logged with AI model, IP, machine identity, and timestamp; secrets never pass through third parties (local stdio transport)

Onboarding, Account & Help

• Onboard (onboard): Guided setup for signup, .env import, API key creation, and MCP/SDK configuration

• Status (get-status): Check plan, usage limits, secret count, and server version

• Help (help): Access documentation on tools, SDK, sessions, rules, and troubleshooting

• Companion SDK (@securecode/sdk): Load secrets at runtime in your applications

Allows for the secure import and export of environment variables via .env files, enabling users to migrate existing secrets into the secure vault and manage them within development environments.