Best for
- Developers already using Varlock to manage .env files who want their AI assistant to reference official documentation
- Teams needing details on @env-spec syntax, CLI commands, or plugin configuration
V
Varlock Docs MCP Server
Official
Official documentation MCP server for Varlock, available over HTTP/SSE
GitHub source repository ↗
38FMRS · D
This is Varlock's own officially hosted documentation-retrieval MCP server, offered over HTTP and SSE remote endpoints, suited for developers who want an AI assistant to accurately answer questions about Varlock usage — but the README provides no specific tool list or config example, and it does not touch local files or secrets.
Varlock is an "AI-safe" .env file manager: it uses a .env.schema as the single source of truth, giving variables types, validation, multi-environment loading, and secure secret retrieval via plugins (1Password, Infisical, AWS, Azure, GCP, HCP Vault, and more), alongside proactive leak scanning (varlock scan) and runtime log redaction. The repository's README lists, under "MCP Servers," two officially hosted documentation MCP servers maintained by dmno-dev (Varlock's own developers): Varlock Docs (HTTP) at https://docs.mcp.varlock.dev/mcp, and Varlock Docs (SSE) at https://docs.mcp.varlock.dev/sse. These let MCP-capable AI clients retrieve Varlock's documentation to answer questions about .env.schema syntax, CLI commands, and plugin configuration more accurately. The README does not enumerate specific tools exposed by the server or provide a client config JSON example; full setup instructions are linked to https://varlock.dev/guides/mcp/docs-mcp/, which is not included in the provided source material.
Tools
The tool list has not been reviewed yet.
Setup
The README only provides the two deployed MCP endpoint URLs (HTTP: https://docs.mcp.varlock.dev/mcp, SSE: https://docs.mcp.varlock.dev/sse) and points to https://varlock.dev/guides/mcp/docs-mcp/ for the full installation guide; that guide's content is not part of the supplied source material, so no reliable step-by-step instructions can be given here. Generally, clients that support remote MCP servers need the corresponding URL and transport (streamable-http or sse) added to their MCP configuration.
Fit and risk
Not for
- Users who want to read or modify local .env file contents directly via MCP (not covered by this server — use the varlock CLI itself)
- Scenarios requiring access to secret values or runtime environment variables (this server is documentation-only and does not handle secret data)
Required permissions
- As a remote, read-only documentation service, clients typically only need outbound HTTPS network access to reach the endpoint
- No local filesystem or environment variable access is required (none is mentioned in the README)
Risks and side effects
- This is a remote service hosted at docs.mcp.varlock.dev, so its availability and data freshness depend on dmno-dev's operation rather than being locally controlled
- The README does not state whether authentication or rate limiting is in place; review terms and privacy practices before connecting
- If documentation lags behind code changes, the AI assistant could give outdated guidance
Troubleshooting
- Confirm the client supports the chosen transport (the HTTP endpoint corresponds to streamable-http, the other to sse)
- Check network connectivity to https://docs.mcp.varlock.dev
- If the connection fails, consult the official setup guide at https://varlock.dev/guides/mcp/docs-mcp/ for the current configuration format
Use cases
Letting an AI coding assistant consult Varlock's official docs when answering questions, instead of relying on potentially stale training data
Retrieving @env-spec syntax and decorator documentation in real time while writing or debugging .env.schema files
Supporting developers integrating Varlock plugins (1Password, Infisical, AWS Secrets, etc.) with documentation lookups
Supported clients
Supported clients have not been confirmed yet.