envmanifest v0.1 The config contract layer for AI-assisted software delivery.

Declare your app's config once. Reconcile it across code, .env files, CI, and deployed providers. Free CLI for local checks. MCP server for coding agents. Verifiable attestations of what was actually deployed.

Install

npm install -g envmanifest

30-second quickstart

cd your-project
envmanifest init        # scan code, draft manifest.yml
envmanifest doctor      # plain-English status
envmanifest check       # CI-shaped reconcile

Use the schema in your editor

Pin this at the top of your manifest.yml — VS Code's YAML extension and JetBrains JSON Schema support both pick it up:

# yaml-language-server: $schema=https://env.ghostlogic.tech/schemas/v0/manifest.schema.json

version: 0
project: my-app
environments: [local, production]
resources: []

For coding agents (MCP)

Local MCP server exposes the manifest to Claude Code / Cursor / any MCP-aware agent — names + metadata only, never values. Default-deny on mutating tools.

npm install -g @envmanifest/mcp-local
claude mcp add envmanifest --scope user -- envmanifest-mcp

For CI (GitHub Action)

- uses: adam-scott-thomas/envmanifest/actions/check@v0.1.1
  with:
    environment: production
    format: sarif

Endpoints on this domain

• GET /schemas/v0/manifest.schema.json — JSON Schema for v0 manifests
• GET /.well-known/seal-public-key — placeholder for the L1+ signing key (Phase 2)
• GET /health — uptime probe

Source & license

• github.com/adam-scott-thomas/envmanifest
• MIT for OSS components (CLI, runtime, MCP local, schema). Cloud adapters BSL 1.1 → Apache 2.0 after 2 years (Phase 2).
• Roadmap · Issues

Schema is currently v0, experimental. Locks at v1 after real-world contact with major frameworks and providers (target: 6 months or 100 active users).