All servers / Developer / Sudocode MCP server
Sudocode MCP server
MCP server for sudocode, git-native context management for AI-assisted development
Tested by ConnectATDScore 84 out of 100. Tested 2026-11-18 on package version 0.2.0. Package: @sudocode-ai/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 14 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (8.0 seconds including download)
- Tools offered: 10
- Last published: 2026-03-18
- Weekly downloads (npm): 2,638
- License: Apache-2.0 · Direct dependencies: 4
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
readyno parametersShows you the current project state: what issues are ready to work on (no blockers), what's in progress, and what's blocked. Essential for understanding context before making any decisions about what to work on next.
list_issues5 of 5 parameters describedSearch and filter issues. Use this when you need to find specific issues by status, priority, keyword, or when exploring what work exists in the project.
show_issue1 of 1 parameter describedGet full details about a specific issue. Use this to understand what the issue implements (which specs), what blocks it (dependencies), its current status, and related work. Essential for understanding context before starting implementation.
upsert_issue8 of 8 parameters describedCreate or update an issue (agent's actionable work item). **Issues implement specs** - use 'link' with type='implements' to connect issue to spec. **Before closing:** provide feedback on the spec using 'add_feedback' if this issue implements a spec. If issue_id is provided, updates the issue; otherwise creates a new one. To close an issue, set status='closed'. To archive an issue, set archived=true.
list_specs2 of 2 parameters describedSearch and browse all specs in the project. Use this to find existing specifications by keyword, or to see what specs are available before creating new ones.
show_spec1 of 1 parameter describedGet full details about a specific spec including its content, relationships, and all anchored feedback. Use this to understand requirements before implementing.
upsert_spec6 of 6 parameters describedCreate or update a spec (user's requirements/intent/context document). If spec_id is provided, updates the spec; otherwise creates a new one with a hash-based ID.
link3 of 3 parameters describedCreate a relationship between specs and/or issues. Use this to establish the dependency graph and connect work to requirements. Most common: 'implements' (issue → spec) and 'blocks' (dependency ordering).
add_reference7 of 7 parameters describedInsert an Obsidian-style [[ID]] reference into spec or issue markdown content.
add_feedback6 of 6 parameters described**REQUIRED when closing issues that implement specs.** Document implementation results by providing feedback on a spec or issue.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.