Secret Store

sh.secretstorePublished by secretstore.shOfficial publisherv1.0.0Updated Nov 14, 2026

Vault for .env files and credentials with scoped, audited MCP access for coding agents.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A hosted vault for .env files and credentials that gives coding agents scoped, audited access to secrets over MCP.

What you can do
  • Store and manage .env files and credentials in a central vault.
  • Give coding agents scoped access to the secrets they need.
  • Keep an audit trail of access to stored credentials.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
When coding agents need environment variables or credentials without pasting secrets into prompts or committing .env files, and you want scoped permissions and an audit record of that access.
Requirements
A remote MCP endpoint at secretstore.sh reached over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared.
Before you install
The service holds credentials and .env secrets, so a compromise or overly broad scope exposes them. Access is granted to agents, which may read secrets on your behalf; review the scopes you grant and rely on the audit trail. No tool list is published, so verify what the server can read or change before connecting.

Installation

In SourceWeft

  1. Open Secret Store in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/sh.secretstore%2Fsecret-store/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "secret-store": {
      "type": "http",
      "url": "https://secretstore.sh/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 14, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.