Tandem
Related Servers
Alternatives to Tandem
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables coding agents to turn Jira Cloud tickets into ready-to-build briefs, verify local branches against acceptance criteria, and prepare QA handoffs, with optional previewed and audited write-back.1081 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables end-to-end automation of developer workflows from Jira issue tracking to GitHub pull requests through natural language, allowing developers to search issues, create branches, commit changes, and manage PRs directly from their IDE.2MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to automate Jira and GitHub/GitLab workflows. It handles issues, branches, pull requests, and deployments with project-aware context and safety checks.3282 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables automation of workflows across GitHub, Notion, and Google Calendar with AI-powered task execution, personalized agent memory, and Slack integration for seamless team coordination and project management.MIT
- AlicenseAqualityBmaintenanceEnables an AI agent to retrieve assigned tickets and their context, assign and mark tickets in progress, create pull requests that close tickets, and move tickets through review and done states while leaving Git actions to the agent and merges to humans.5MIT
- -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-
TDQS
Scored across 10 tools
The orchestration tools (start, ship, status, standup, release_notes, health) each target a distinct workflow, and the primitive getters (github_pr, jira_issue, notion_page, github_checks) are clearly narrower. The main overlap is between github_pr (which already returns CI check runs) and github_checks, and between tandem_status and tandem_standup, but the descriptions make the scope difference (single issue vs. multi-issue summary, PR vs. arbitrary branch/SHA) reasonably clear.
There is a readable two-tier convention: 'tandem_'+verb for orchestration and provider_noun for raw getters. However, the patterns don't align — tandem_start/tandem_ship are bare verbs with no object, while github_pr/jira_issue/notion_page are object-only with no verb, so the set mixes verb-style and noun-style names. It's still predictable enough to parse at a glance.
Ten tools is well within the sweet spot, and each one earns its place: six orchestration/workflow tools plus four thin primitive getters that the orchestrators build on. Nothing feels redundant or padded.
The core lifecycle is covered end to end: start a bundle, ship it, inspect unified status, roll up a standup, draft release notes, and health-check integrations. Minor gaps remain — there's no way to link up an already-existing branch/doc to an issue without running tandem_start, no arbitrary comment/update tool, and no unfiltered issue listing — but agents can work around these.