dispersl-mcp
Related Servers
Alternatives to dispersl-mcp
No user-submitted related servers found.
Related Servers
- -licenseBqualityNot gradedmaintenanceEnables AI-driven orchestration of GitHub development workflows including automated issue analysis, code generation, code review, and PR creation through multiple specialized agents. Integrates with GitHub Actions to automate the complete development process from issue to pull request.7-
- AlicenseAqualityAmaintenanceOrchestrates multiple AI coding agents declaratively to automate software development workflows for engineering teams.1427,535 PyPI1,348Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to automate GitHub repository management, issue tracking, and commits using natural language.6 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to register, self-assign and coordinate tasks, track progress, review work, and manage GitHub Projects v2 with AI-powered PRD generation, sprint planning, issue triage, and PRD-to-issues pipelines backed entirely by GitHub-native storage.453 npmMIT
- AlicenseNot gradedqualityAmaintenanceExtends AI assistants with software development capabilities such as deep research, codebase analysis, requirements and user-story generation, project scaffolding, context curation, task management, and multi-step workflow execution.22 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI models like Claude or GPT to interact with a decentralized git network, supporting repository initialization, DID generation, agent spawning, and pull requests.-
TDQS
Scored across 28 tools
Most tools target distinct resources and actions, especially task/step CRUD, stats, and specialized agents. Minor ambiguity exists between the plan agent and specialized agents, and history/current getters require attention to descriptions.
The set uses consistent snake_case and mostly follows a verb_noun pattern. Minor deviations like new_key vs create_task, fetch_api_root, and the dispersl_* agent prefixes are readable but not perfectly uniform.
28 tools is heavy for a single MCP server, spanning tasks, steps, stats, agents, sessions, MCP configuration, models, and API keys. While many are distinct, the surface is large enough that consolidation or clearer grouping would improve usability.
Core task, step, agent, and key operations are present, but lifecycle coverage has notable gaps. There is no create_step, no delete/revoke for tasks, steps, or keys, no list MCP servers, and no session termination.