OpenSpec
The leading spec-driven development workflow for AI agents. Implements the /opsx:propose → /opsx:apply → /opsx:archive cycle that scaffolds proposals, specs, design docs, and task checklists, then applies them and archives once shipped.
“OpenSpec is the spec-driven development workflow that AI coding agents have been waiting for. The pitch is straightforward: you tell the agent to propose a change (`/opsx:propose add-dark-mode`), and OpenSpec scaffolds a structured artifact bundle: proposal, specs, design, tasks. The agent then applies the tasks one at a time (`/opsx:apply`), and once done, archives the change with the specs updated for the next feature. The 43k stars are the loudest signal in this entire directory and they earn it. The architecture decision worth understanding: OpenSpec is built brownfield-first, scaling from a single developer to enterprise teams while preserving the team's existing workflow. Run it on a Greenfield repo and you get spec-driven development from day one; run it on an existing codebase and the proposals respect what already exists.”
INSTALL THIS SERVER
{
"mcpServers": {
"openspec": {
"command": "npx",
"args": [
"-y",
"@fission-ai/openspec@latest",
"mcp"
]
}
}
}
{
"mcpServers": {
"openspec": {
"command": "npx",
"args": [
"-y",
"@fission-ai/openspec@latest",
"mcp"
]
}
}
}
{
"mcpServers": {
"openspec": {
"command": "npx",
"args": [
"-y",
"@fission-ai/openspec@latest",
"mcp"
]
}
}
}
{
"mcpServers": {
"openspec": {
"command": "npx",
"args": [
"-y",
"@fission-ai/openspec@latest",
"mcp"
]
}
}
}
{
"mcpServers": {
"openspec": {
"command": "npx",
"args": [
"-y",
"@fission-ai/openspec@latest",
"mcp"
]
}
}
}
7 SELECTED TOOLS
OUR ASSESSMENT
The leading spec-driven development workflow for AI agents. Implements the `/opsx:propose → /opsx:apply → /opsx:archive` cycle that scaffolds proposals, specs, design docs, and task checklists, then applies them and archives once shipped. 43k GitHub stars; MIT-licensed; npm-distributed as `@fission-ai/openspec`. Built brownfield-first; scales from personal projects to enterprise.
- 43k GitHub stars and active maintenance signal real workflow adoption among teams using AI coding agents.
- Brownfield-first architecture; proposals respect existing code while shaping incremental change.
- Structured artifact output (proposal, specs, design, tasks) gives the agent a checklist to drive against, with clear hand-off points for human review.
- Zero-config quick start: `npm install -g @fission-ai/openspec@latest` then `openspec init`.
- Workflow conventions are opinionated; teams with established spec patterns may find friction adapting.
- New `/opsx:` workflow is the recommended path; older OpenSpec workflows exist but receive less ongoing development.
- Requires Node.js 20.19.0+; older runtimes fail at install.
OpenSpec runs locally and operates on the operator's filesystem. The agent reads and writes files under `openspec/` in the project directory plus generated artifacts under the project tree. Secrets and credentials stay outside OpenSpec's scope; spec-driven workflows execute the same code the agent was already authorized to write, so the existing project-level access controls apply. Production deployment of OpenSpec-generated changes uses the team's standard CI and code-review gates.
Teams adopting AI coding assistants who want repeatable, spec-driven feature workflows over prompt-and-pray. Works equally well on greenfield and existing codebases.
TECHNICAL DETAILS
RECORDED ADOPTION METRICS
Saved directory snapshots. Record last checked MAY 3, 2026. The review date above does not refresh these figures.
// Recorded note43.6k stars place this as the most-starred entry in our directory. Star traction reflects strong adoption among teams running structured agent-driven development workflows.
// Recorded noteTop-ranked dev-tools MCP by every stat we track. The brownfield-first architectural choice is the reason it scales beyond demo workflows.
SOURCES & RECORDED CHECKS
These are the directory listings and check details held in this record. Client compatibility, directory listings and installation testing are separate signals. Recorded client names describe the scope of a check; they do not establish a security assessment or a recurring test schedule.
The same server, 5 different lenses. We reconcile these signals into our editorial score, which is why our number sometimes diverges from a directory-aggregate star count.
| Source | Their rating | Their star count | Their downloads | Last synced |
|---|---|---|---|---|
| AutomationSwitch This page | 4.5editorial | 44,941 | — | MAY 3, 2026 |
| PulseMCP | — unrated | unavailable | unavailable | APR 28, 2026 |
| MCPMarket | — unrated | unavailable | unavailable | APR 28, 2026 |
| Official MCP Registry | — unrated | unavailable | unavailable | APR 28, 2026 |
| Awesome MCP Servers | — unrated | unavailable | unavailable | APR 28, 2026 |
| Smithery | — unrated | unavailable | unavailable | APR 28, 2026 |
// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.
OTHER DEV TOOLS MCP SERVERS
GitHub
GitHub’s official MCP server for repository, issue and pull-request context, with hosted and locally run deployment options.
Playwright
Official Microsoft Playwright MCP server. Browser automation tools (navigate, click, fill, screenshot, evaluate JS, network capture) backed by Playwright. 31,942 stars, 35 commits/30d, Apache-2.0.
FastMCP (Python)
The fast, Pythonic way to build MCP servers and clients. Maintained by PrefectHQ. 25,133 GitHub stars and 92 commits on main in the last 30 days. The dominant Python MCP framework.
Repomix
Pack the entire repository into a single AI-friendly file. Optimised context for feeding codebases to Claude, ChatGPT, Gemini, and others. 24,515 GitHub stars and 100 commits on main in the last 30 days.
Serena
Powerful MCP toolkit for coding. Provides semantic retrieval and editing capabilities, positioned as the IDE for the agent. 23,971 GitHub stars and 100 commits on main in the last 30 days.
MCP Python SDK
The official Python SDK for Model Context Protocol servers and clients. Maintained by the Model Context Protocol project. 22,984 GitHub stars and 5 commits on main in the last 30 days.
DISCUSS YOUR
MCP REQUIREMENTS.
Evaluating a server, scoping an internal deployment, or working out whether MCP is the right fit at all. Start the conversation and we will point you at the right piece of the ecosystem.