# Entalpa > Entalpa is a spec-driven development platform for AI coding agents: a persistent, MCP-native specification layer (stakeholders → business needs → user stories → requirements → design specs) with atomic locking and open questions surfaced before the build, for people building with Claude Code, Cursor and Codex. It turns an ambiguous product idea into structured, traceable requirements and serves them to the agent over MCP, so the agent builds what was meant without breaking what exists. Key facts: - Category: spec-driven development (SDD). Unlike file-based SDD workflows (GitHub Spec Kit, OpenSpec, Kiro's per-feature specs), the spec is a store, not a markdown file: it persists across sessions, and a locked requirement is excluded from what the model is allowed to regenerate. - Problem it solves: architectural drift in AI-assisted ("vibe") coding. Agents guess implicit business logic, break existing features, rewrite the spec they were given, and burn tokens re-deriving context every session, because no durable, governed spec exists upstream of the code. - Approach: a living, traceable specification the agent has to follow, served over MCP. End-to-end traceability from stakeholder intent to design. Entalpa does not replace coding agents; it stabilizes them. It composes with Spec Kit, OpenSpec and CLAUDE.md rather than replacing them. - Audience: solo founders and small teams building real products with AI agents; product people who need a spec their engineers' agents will actually read. - Access: web app with a free tier at https://app.entalpa.com (no credit card required); reading and writing a project over MCP never spends credits; no lock-in, agent-agnostic (any MCP client). Export to ReqIF. ## Pages - [Home](https://entalpa.com/en): what Entalpa does, the failure modes of AI coding agents it fixes, supported agents, FAQ - [For product teams](https://entalpa.com/en/for-product-teams): the same platform pitched to product managers and founders - [How it works](https://entalpa.com/en/how-it-works): the specification pipeline (stakeholders, business needs, user stories, requirements, design specs) and how agents consume it over MCP - [Connect your agent](https://entalpa.com/en/connect): the Entalpa MCP server, with a setup page for each client (Claude Code, Cursor, Codex, Windsurf, VS Code + Copilot, Gemini CLI, Claude Desktop, Cline, Roo Code, Zed, Antigravity, Kiro, Warp, OpenCode, Amp, Continue) - [Spec-driven development tools compared](https://entalpa.com/en/vs): one table across Spec Kit, Kiro, OpenSpec, BMAD, Tessl and Entalpa, then an honest page on each, including CLAUDE.md, Context7, memory MCP servers, ChatPRD, Jama and DOORS, each saying where the other tool wins - [Guides](https://entalpa.com/en/guides): long-form pieces built from what developers said about their own projects and from incidents in ours. What spec-driven development is and what happened to it, spec-driven development with Claude Code, the vibe-coding wall, what your agent breaks, reviewing the spec not the diff, why agents guess requirements, and a PRD template written for coding agents - [Agent failure modes, measured](https://entalpa.com/en/fix): one page per failure mode, each with a measurement we ran on a real repository and the method printed on the page - [App](https://app.entalpa.com): the Entalpa web app; sign up and start free, no credit card required ## Contact - Email: contact@entalpa.com - App: https://app.entalpa.com - Company: Entalpa ## Optional - [Pricing](https://entalpa.com/en/pricing) - [Privacy policy](https://entalpa.com/en/privacy-policy) - [Terms of service](https://entalpa.com/en/terms-of-service)