Expand MCP tools: git ops, tags, workspaces, pull requests #3328
harryy2510
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey team! 👋
I've been using the MCP server heavily with Claude Code and kept running into the same friction. Agents can manage issues fine, but the moment they need to check git status, push code, or open a PR, they have to drop out of the vibe-kanban context entirely.
So I went ahead and implemented a set of new MCP tools to close that gap. Would love to get your thoughts on the approach and whether this is something you'd want upstream.
What's in the implementation
10 new MCP tools that give external agents (Claude Code, Cursor, etc.) broader control over the full dev loop:
get_workspacelist_project_statuseslist_branchesgit_statusgit_pushcreate_pull_requeststop_executioncreate_tag/update_tag/delete_tagAlso improved
update_issuewith richer field support (assignee, priority, tags, status).Fork
The full implementation is on my fork:
feat/mcp-updateson harryy2510/vibe-kanban14 files changed, ~2100 lines added. All new tool routers wired, docs updated, orchestrator mode tests passing.
If this looks useful, feel free to pull from the fork or let me know and I can work with whatever process works best for you!
All reactions