sops-mcp

Purpose: Securing and managing secrets using SOPS encryption with a Model Context Protocol server.

Inferred · not functionally tested

Audience: devops and security engineers

Inferred · not functionally tested

Functions: data_extraction, workflow_automation

Inferred · not functionally tested

Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Apache-2.0 · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

sops-mcp sits in PulseGate's Password & secrets management category. Inferred · not functionally tested: It focuses on securing and managing secrets using SOPS encryption with a Model Context Protocol server. Inferred · not functionally tested: sops-mcp is an open-source project aimed at devops and security engineers. Basis unknown · not verified: sops-mcp is open source under the Apache-2.0 license. Basis unknown · not verified: sops-mcp is available on the command line, and it can be self-hosted.

Behind sops-mcp is privacyplaybook, and it first shipped in 2026. The project is developed in the open on GitHub with 54 commits in the last 90 days. Inferred · not functionally tested: Among its 5 catalogued features are SOPS encryption, secret management, and MCP server. Basis unknown · not verified: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.