Task execution MCP server - connects to specmanager.ai
npm install @specmanager/mcp-serverA Model Context Protocol (MCP) server that integrates with specmanager.ai for AI-powered task management and project execution.
- Node.js >= 18
- A specmanager.ai account
- An API key from your specmanager.ai dashboard
No installation required. Run directly with npx:
``bash`
npx @specmanager/mcp-server
`bash`
npm install -g @specmanager/mcp-server
Then run:
`bash`
specmanager-mcp
#### Stdio Mode
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| SPECMANAGER_API_KEY | Yes | - | Your API key from specmanager.ai |SPECMANAGER_PROJECT_ID
| | No | - | Default project ID (can be auto-detected from git) |
#### HTTP Mode
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| PORT | No | 3000 | HTTP server port |
In HTTP mode, API keys are provided per-request via headers (see HTTP Authentication).
1. Sign up or log in at specmanager.ai
2. Navigate to your account settings
3. Generate a new API key
4. Copy the key and set it as SPECMANAGER_API_KEY
For use with Claude Code or other MCP clients that communicate via stdio:
`bash`
export SPECMANAGER_API_KEY="your-api-key"
npx @specmanager/mcp-server
For hosted deployments or web-based integrations:
`bash`
npx @specmanager/mcp-server --http
Or with a custom port:
`bash`
npx @specmanager/mcp-server --http --port=8080
#### HTTP Authentication
In HTTP mode, no environment variable is needed for the API key. Instead, each request must include the API key via one of these headers:
``
Authorization: Bearer
or
``
X-API-Key:
This allows multi-tenant deployments where different users provide their own API keys.
#### HTTP Endpoints
| Method | Endpoint | Description |
|--------|----------|-------------|
| GET | /health | Health check |POST
| | /mcp | MCP message handler |GET
| | /mcp | SSE stream for session |DELETE
| | /mcp | Session cleanup |
`bash`
claude mcp add specmanager -e SPECMANAGER_API_KEY=your-api-key -- npx -y @specmanager/mcp-server
To add for your entire user (all projects):
`bash`
claude mcp add specmanager --scope user -e SPECMANAGER_API_KEY=your-api-key -- npx -y @specmanager/mcp-server
Alternatively, add to your MCP configuration file (.mcp.json):
`json`
{
"mcpServers": {
"specmanager": {
"command": "npx",
"args": ["-y", "@specmanager/mcp-server"],
"env": {
"SPECMANAGER_API_KEY": "your-api-key"
}
}
}
}
List your specmanager.ai projects. Supports auto-detection from git remote when workingDir is provided.
List specs for a project with task counts. Returns specs with pending/in-progress/done task counts. By default, only shows specs with pending or in-progress tasks. Use includeCompleted=true to also show fully completed specs.
List available tasks for execution. Filter by status: pending (default), in-progress, done, or all. Optionally filter by specId to only show tasks from a specific spec.
Retrieve detailed information about a specific task, including implementation steps, purpose, files to modify, and related spec context.
Mark a task as in-progress before beginning work. Required for proper state tracking.
Mark a task as completed with a summary of what was implemented and which files were modified.
Send real-time progress updates on in-progress tasks. Updates appear in the specmanager.ai dashboard and VSCode extension.
When working in a git repository linked to a specmanager.ai project, the server can automatically detect the project from your git remote URL. Simply provide the workingDir parameter to any tool that accepts it.
`bashClone the repository
git clone https://github.com/specmanager/mcp-server.git
cd mcp-server
MIT
- Documentation: specmanager.ai/docs
- Issues: GitHub Issues