OpenSpec MCP Server
A Model Context Protocol (MCP) server for OpenSpec - bringing spec-driven development to AI assistants like Cursor, Claude Desktop, and more.
What is OpenSpec MCP?
OpenSpec MCP Server exposes OpenSpec's powerful spec-driven development workflow through the standardized MCP protocol. This allows AI assistants to:
- Create and manage change proposals
- Read and update specification documents
- Track task progress
- Validate spec formats
- Archive completed changes
Installation
Using uvx (Recommended)
No installation needed! Just configure your AI tool to use:
uvx openspec-mcp
Using pip
pip install openspec-mcp
Configuration
Cursor
Add to .kiro/settings/mcp.json or ~/.kiro/settings/mcp.json:
{
"mcpServers": {
"openspec": {
"command": "uvx",
"args": ["openspec-mcp"],
"env": {
"OPENSPEC_DEBUG": "false"
},
"disabled": false,
"autoApprove": [
"list_changes",
"list_specs",
"show_change",
"read_spec",
"read_tasks"
]
}
}
}
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"openspec": {
"command": "uvx",
"args": ["openspec-mcp"],
"env": {
"OPENSPEC_DEBUG": "false"
}
}
}
}
Available Tools
Project Management
init_openspec- Initialize OpenSpec project structurelist_changes- List all active changes with progresslist_specs- List all specification documents
Change Management
create_proposal- Create a new change proposalshow_change- Show detailed information about a changearchive_change- Archive a completed change
Specification Management
read_spec- Read a specification documentread_tasks- Read tasks for a changeupdate_task_status- Update task completion status
Validation
validate_change- Validate change document format
Usage Examples
In Cursor
User: Please create a change proposal for adding two-factor authentication
AI: I'll use OpenSpec MCP to create this change proposal.
[Calls create_proposal tool]
Change proposal created: openspec/changes/add-two-factor-auth
Let me help you fill in the details...
Testing with MCP Inspector
npx @modelcontextprotocol/inspector uvx openspec-mcp
Environment Variables
OPENSPEC_WORKING_DIR- Working directory (default: current directory)OPENSPEC_DEBUG- Enable debug logging (default: false)OPENSPEC_LOG_LEVEL- Log level: DEBUG, INFO, WARNING, ERROR (default: INFO)OPENSPEC_STRICT- Enable strict validation mode (default: true)
Development
# Clone the repository
git clone https://github.com/Fission-AI/OpenSpec
cd OpenSpec/openspec-mcp
# Install development dependencies
pip install -e ".[dev]"
# Run tests
pytest
# Run with coverage
pytest --cov=openspec_mcp --cov-report=html
# Format code
black src tests
ruff check src tests
# Type checking
mypy src
License
MIT License - see LICENSE file for details
Links
Metadata
Release files for openspec-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| openspec_mcp-0.2.0.tar.gz | 60.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openspec_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 88.1 kB
Release files / openspec_mcp-0.2.0.tar.gz
| Download URL | openspec_mcp-0.2.0.tar.gz |
|---|---|
| Size | 60.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f0963580bba72b0d30d452222461f88e88728966d48b364e63e0a48bfb2cb3f
|
|
BLAKE2b-256 checksum How to use checksums |
3d7ce9791ffe9d42293ea8db461f3ee1881b8249889f0552a993183ee16f7847
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.2
|
Release files / openspec_mcp-0.2.0-py3-none-any.whl
| Download URL | openspec_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 27.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ead5efa8074536f3054c716ad1ea0318ae9977758840f7921681b77e0cd78760
|
|
BLAKE2b-256 checksum How to use checksums |
8939ee42b168869ccb5bd8da8452a2695128cf77f3c4acc9c63c00b3d387dd81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.2
|
Security for openspec-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.