Your configs deserve
ConfigPig is the managed registry that gives your team versioned config files, format conversion (JSON, YAML, TOML, INI, .env), safe deployments, and a REST API + MCP server — so your configs stop living in random files scattered across your codebase.
100% free. No credit card. No catch.
Works with every MCP client and REST API
Your configs are flying blind
When a config breaks in production, you find out from angry users — not from your tools. There's no version history, no rollback, no way to know which configs are stale or who changed what last Tuesday.
Scattered across files, repos, and environments. Nobody knows what's live in production.
One bad edit and the old config is gone. No diffs, no rollback, no audit trail.
Changing a config requires a code change, a PR, a build, and a deploy. For a settings file.
# Which version is this? Who changed it?
# Is this the same in staging?
# Nobody knows.
DB_CONFIG = {
"host": "db.internal.prod",
"port": 5432,
"pool_size": 20,
"timeout": 30,
"ssl": True,
}
# Hardcoded. No versioning. No rollback.
# Change this and hope for the best.
conn = connect(**DB_CONFIG)
How it works
From blank canvas to production-ready config in four steps.
Create
Write your config in JSON, YAML, TOML, INI, or .env format. Store it with metadata and tags.
Test
Compare versions side-by-side with unified diffs. Validate format before saving.
Deploy
Assign labels like production or staging to any version.
Roll back instantly if needed.
Integrate
Fetch configs via REST API or MCP. Request any output format — we convert automatically.
Everything your configs need
From a simple dashboard to a full REST API and MCP server.
Immutable Versioning
Every save creates a new version. Compare diffs, rollback instantly, and see exactly who changed what and when.
Flexible Labels
Point labels like production and staging at any version.
Create custom labels for any workflow. One config, many pointers.
Format Conversion
Store as YAML, fetch as JSON. Automatic conversion between JSON, YAML, TOML, INI, and .env formats.
Full REST API
Complete CRUD API with Swagger docs, team-scoped API keys, and fetch-with-conversion. One endpoint, always the right format.
MCP Server
Your AI tools manage configs directly. Claude, Cursor, Windsurf — any MCP client connects instantly. No plugins needed.
Workspace Export
Export your entire config workspace as portable JSON. Schedule regular backups.
You: Create a database config in YAML format.
Deploy to staging.
Claude: I'll create that config for you.
• create_config slug: "database-config" ✓
• create_version v1 with YAML content ✓
• fetch_config test fetch as JSON ✓
• promote_version v1 → staging ✓
Done. "database-config" is live on staging.
Want me to also fetch it as TOML for your
Go service?
Your AI tools manage your configs
Most config tools give you a dashboard and maybe an API. ConfigPig ships a full MCP server — so Claude, Cursor, and Windsurf can create, version, deploy, and convert your configs without leaving your editor.
Config CRUD, version management, label assignment, format conversion, and team admin.
OAuth 2.1 + PKCE for interactive clients. API key fallback for scripts and CI/CD.
Claude Desktop, Claude Code, Cursor, Windsurf — any MCP-compatible client connects instantly.
"Can't I just use Git / a database table?"
You could. Here's why teams don't.
Git isn't a config registry
Versions files, not runtime configs.
Git versions files. Configs need runtime fetching, label-based promotion, format conversion, and multi-environment support. A git commit can't do that.
A database table isn't a product
2–4 weeks of engineering, minimum.
You'd build versioning, rollback, label-based promotion, format conversion, an API, key management, and access controls. That's a product, not a table.
Build vs. buy
12 features you'd have to maintain.
Immutable versioning, label-based promotion, rollback, format conversion, format validation, API + auth, version diffing, multi-format export, duplicate detection, workspace export, usage analytics, MCP integration.
100% Free. Seriously.
No tiers. No trials. No credit card. Every feature, for every user, forever.
ConfigPig is free because config management shouldn't have a price tag. Small teams deserve good tooling without budgeting for yet another SaaS subscription.
- Unlimited configs
- Unlimited versions
- Unlimited labels
- Unlimited API calls
- Up to 10 team members
- All 5 config formats
- REST API + MCP server
- Format conversion + export
Frequently asked questions
How does versioning work?
Every time you save a config, a new immutable version is created automatically. You can compare any two versions with a unified diff, rollback to any previous version in one click, and see exactly who changed what and when. Versions are never overwritten.
What are labels?
Labels are flexible pointers like latest, staging, and
production that point to a specific config version —
so you can test v5 under staging while v3 is still live under production.
Custom labels are fully supported.
How does the MCP server work?
ConfigPig exposes a full MCP server that any compatible client (Claude Desktop, Claude Code, Cursor, Windsurf) can connect to. Your AI tools gain the ability to create, version, deploy, convert, and manage configs directly — no context-switching needed. Authentication uses OAuth 2.1 + PKCE.
What config formats are supported?
JSON, YAML, TOML, INI, and .env. Store in any format and fetch in any other — ConfigPig converts automatically. All formats are validated on save.
How does format conversion work?
All conversion goes through an intermediate dict: parse source → dict → serialize
to target format. Nested configs are flattened for .env (e.g., db.host →
DB_HOST). INI uses sections for top-level keys.
Is ConfigPig really free?
Yes. ConfigPig is 100% free for teams up to 10 people. Unlimited configs, unlimited versions, unlimited API calls, all five formats, the full REST API, MCP server, and format conversion. No credit card required, no trial, no catch.
Stop scattering configs. Start managing them.
100% free for teams up to 10. Your team will wonder how they shipped products without this.
Start (and Stay!) Free