Skip to main content
Glama
SecureCode

SecureCode

by juanisidoro

@securecode/mcp-server

MCP Server for SecureCodeHQ. Lets Claude Code access your secrets securely without ever seeing them.

SecureCode MCP server

Quick Start

claude mcp add securecode -- npx -y @securecode/mcp-server

Then tell Claude Code:

Set up SecureCode in this project

The onboard tool walks you through account creation, secret import, and configuration. Takes about 2 minutes.

Related MCP server: aarifmms/keyblind

What It Does

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.

Tools

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

MCP Access Rules

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)

Session Lock

You: "Wake my session for acme staging"
Claude: Session unlocked. Only acme/staging secrets accessible.

You: "byebye"
Claude: Session locked & secrets cleaned from disk.

Sessions auto-sleep after configurable inactivity (default: 2 hours).

How It Works

  • Secret values are written to a local file, the AI never sees them (inject mode)

  • Explicit reveal: true returns value to AI (audited)

  • Injected files are removed on sleep, byebye, or process exit

  • Multiple Claude Code instances don't collide (hash based on API key + PID)

  • Encrypted with AES-256-GCM using envelope encryption (Cloud KMS)

  • Every access is logged with AI model, IP, machine identity, and timestamp

  • Runs locally via stdio transport, secrets never pass through third parties

  • Device approval required on first use from each machine

SDK

The companion SDK lets your app load secrets at runtime:

npm install @securecode/sdk
import { loadEnv } from '@securecode/sdk';
await loadEnv(); // all secrets loaded into process.env

SDK on npm

Requirements

  • Node.js >= 18

  • A SecureCodeHQ account (free tier: 50 secrets, 10K accesses/month)

License

MIT

Available Tools

17 tools
byebyeA

End your work session. Locks the session, cleans up all injected secrets from disk, and says goodbye. Use this when you finish working for the day.

Inputs: no named parameters.

create-secretB

Create a new secret. Secrets with the same name can coexist if they have different env tags.

Inputs: name (required), value (required), description, tags, +2 more.

delete-secretA

Delete a secret (soft delete, can be recovered)

Inputs: name (required), tags.

export-envC

Export all secrets as .env or CSV format. Returns the full content with decrypted values.

Inputs: format, tags.

get-active-rulesA

List active MCP access rules. Read-only — rules can only be created or modified from the dashboard. Use this to understand why access to a secret was blocked.

Inputs: no named parameters.

get-secretA

Get a secret by name. By default, injects the value into a local file so it never appears in the AI conversation. Use reveal:true to see the raw value (audited as conscious action). Use cleanup:true to remove all injected secrets from disk.

Inputs: name, tags, reveal, cleanup.

get-statusA

Get your SecureCodeHQ account status: plan, usage limits, secrets count, and MCP server version. Useful to check remaining capacity and verify the server is up to date.

Inputs: no named parameters.

helpB

Get SecureCode documentation: available tools, usage patterns, SDK setup, and common workflows. Use this to understand how to help the user with SecureCode.

Inputs: topic.

import-envA

Import secrets from .env files into SecureCode. For security, .env import must be done through the web interface — the AI agent never sees secret values during import. This tool provides the link to the import page.

Inputs: no named parameters.

list-secretsA

List all available secrets with their tags and expiration status. Returns names and metadata, never values.

Inputs: tags.

onboardA

Start or continue the SecureCode onboarding. Guides the user through signup, .env import, API key creation, MCP configuration, and optional SDK setup — all from Claude Code. Call this tool multiple times to progress through the steps.

Inputs: action, configPath, selectedProject, selectedEnv.

renew-secretA

Renew an expired secret or change its TTL. Use this to reactivate expired secrets or extend expiration.

Inputs: name (required), ttlHours, tags.

security-checkA

Analyze the project for security issues after SecureCode setup. Returns a list of actions the agent MUST execute to protect secrets. Call this after SDK installation.

Inputs: no named parameters.

session-statusA

Check the current session status: active or sleeping, scope restrictions, and time remaining before auto-sleep.

Inputs: no named parameters.

sleep-sessionA

Lock the session immediately. All secret access will be blocked until you wake it again. Use this when you finish working.

Inputs: no named parameters.

update-secretC

Update an existing secret's value, description, tags, or domain. Only provided fields are changed.

Inputs: name (required), value, description, tags, +2 more.

wake-sessionB

Wake (unlock) the session to start accessing secrets. Optionally restrict access to specific tag scope and set auto-sleep timer.

Inputs: scope, autoSleepMinutes.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have distinct purposes, but some potential confusion exists between 'byebye' and 'sleep-session' (both end sessions) and 'get-secret' and 'list-secrets' (both retrieve secret info). Descriptions help clarify differences, but overlap in session management and secret retrieval could cause misselection.

    Naming Consistency4/5

    Tools follow a consistent verb-noun pattern (e.g., create-secret, delete-secret, update-secret) with clear, descriptive names. Minor deviations include 'byebye' (informal) and 'onboard' (single word), but overall naming is predictable and readable.

    Tool Count4/5

    17 tools is slightly high but reasonable for a secrets management domain, covering operations like CRUD for secrets, session control, onboarding, and security checks. It feels comprehensive without being overly bloated, though some tools like 'help' and 'get-status' might be borderline essential.

    Completeness5/5

    The toolset provides complete coverage for secrets management: full CRUD (create, get, list, update, delete, renew), session lifecycle (sleep, wake, status), onboarding, import/export, security analysis, and documentation. No obvious gaps exist for the stated purpose, enabling agents to handle end-to-end workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Local AES-256-GCM encrypted vault for AI agents. Resolve {{PLACEHOLDER}} secrets in prompts at runtime — LLMs never see real API keys. Argon2id key derivation, zero cloud.
      2
      70 npm
      7
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Encrypted secrets vault that blinds AI agents to API keys. Stores secrets in AES-256-GCM encrypted SQLite vault, resolves them at runtime via MCP values never appear in LLM conversation transcripts. Sandbox .env files with deterministic fakes.
      27
      133 npm
      3
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Encrypted token store for Claude Code sessions, providing MCP tools for secure secret management with macOS Keychain integration, per-project allowlists, and native dialog input.
      6
      56 npm
      6
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to securely manage API keys and secrets via the MCP protocol, with encrypted storage at rest and a simple CLI and Python SDK.
      1
      MIT