Serveur MCP pour la génération d'artefacts agiles (backlogs, features, user stories) avec IA - compatible Windsurf, Claude et Cursor
Serveur MCP pour la génération d'artefacts agiles (backlogs, features, user stories) avec IA - compatible Windsurf, Claude et Cursor
Creating agile backlogs manually is time-consuming and error-prone:
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
{
"mcpServers": {
"agile-planner": {
"command": "node",
"args": [
"D:/path/to/agile-planner/server/index.js"
],
"env": {
"MCP_EXECUTION": "true",
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| MCP_EXECUTION | Declared in the maintainer’s client configuration. | Yes |
| OPENAI_API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Every Domotz endpoint, plus a local SQLite fleet mirror that answers cross-site questions.
MCP server for using Alchemy APIs
This project demonstrates a decoupled real-time agent architecture that connects LangGraph agents to remote tools served by custom MCP (Modular
Production-grade resilience middleware for MCP servers — timeout, retry, circuit breaker.