Secenv Mcp

io.github.chirag127Published by GitHub account chirag127v1.1.4Updated Oct 24, 2026

Centralized secrets manager MCP server. Generate .env files, rotate keys, sync to GitHub Actions.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that acts as a centralized secrets manager, letting an assistant generate .env files, rotate keys and sync secrets to GitHub Actions.

What you can do
Generate .env files from a centralized secrets store for projects the assistant works on. Rotate keys held in that store. Sync secrets to GitHub Actions. The server is described as a centralized secrets manager, so these operations are organized around one vault rather than per-project files.
When to use it
Useful when you keep secrets in a private Git-hosted vault and want an assistant to produce .env files, rotate keys or push secrets into GitHub Actions without handling them by hand.
Requirements
Runs as a local process on the user's machine (desktop only, stdio transport, distributed as an mcpb package). Requires the SECENV_REPO_URL environment variable, the Git URL of your private secrets vault, which is required on first run. No authentication is declared.
Before you install
The server handles real secrets: it reads from a private vault and writes .env files and GitHub Actions secrets, so a mistake can expose or overwrite credentials. It requires the SECENV_REPO_URL variable pointing at your private vault. Rotating keys and syncing secrets change live credentials and CI configuration; review actions before approving them.

Installation

In SourceWeft

  1. Open Secenv Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.4LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.