butchr
Watches Jira tickets assigned to the account, detects active (In Progress/In Review) tickets, and notifies agents of ticket, comment, and link changes.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@butchrlist my active Jira tickets and their agent status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
butchr
The software factory, rewritten. A single local daemon that:
Watches your Jira — the tickets assigned to the account that owns the API token, and the items they link to.
Runs an agent per active ticket — when a ticket is In Progress or In Review, it spins up a herdr agent (via
@brooswit/herdr-sdk).Pushes updates to those agents — over MCP (
@brooswit/thatch): agents connect to the daemon identifying which issue they work on, and the daemon channels ticket/comment/link changes to the right one.Shows a live view — a webapp listing the active agents; click one and butchr opens a terminal window running
herdr agent attachon it, so you drop straight into that agent's shell. No browser extension, no embedded terminal — terminals are real herdr terminals.
Change detection is @brooswit/sundry's watch over a Jira JQL feed. Blocking agent prompts are handled through herdr's own blocked detection + send_keys (herdr owns the terminal; butchr reads and answers).
Architecture
one Elysia process
├── /mcp agents connect here (thatch), identifying via x-issue header
├── /agents,/health read-only live view
└── loops (landing incrementally)
├── jira-watch sundry.watch over `assignee = currentUser() AND updated >= cursor`
├── reconcile desired (In Progress/In Review) ↔ herdr agents: spawn / stop
└── notify ticket/comment/link change → thatch channel → the agent on that issuesrc/: config · atlassian (Jira client) · daemon (the app + notify) · web (live view). More loops land as their own modules.
Related MCP server: Jira MCP Server
Install & run
On each machine:
npm i -g @brooswit/butchr # or pin a version
cp .env.example .env # fill in ATLASSIAN_SITE / EMAIL / TOKEN_FILE
butchr # reads .env / the environmentFrom source (development):
bun run startDevelopment
bun run check # generate + typecheck + tests + coverage ≥90% (what CI runs)Every src/ change needs a CHANGELOG.md entry and a version bump (CI enforces it).
Predecessor (300 releases of history) preserved at brooswit/butchr-legacy.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with Jira to fetch issues by key and perform JQL searches. It provides a foundation for integrating multiple work systems, with planned support for Slack and GitHub.671MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive, production-ready MCP server for seamless Jira Cloud integration, enabling AI agents and custom applications to manage boards, issues, users, projects, and workflows via natural language commands.3,8454MIT
- FlicenseNot gradedqualityDmaintenanceManages Atlassian Jira Cloud projects, issues, sprints, boards, worklogs, comments, and workflow transitions from MCP-compatible clients.
- AlicenseAqualityFmaintenanceA local MCP server for Jira Cloud-driven development. Connects MCP clients to Jira for searching issues, reading tasks, parsing attachments, and mapping projects to local repos.1065MIT
Related MCP Connectors
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
Agent-native collaboration network: orchestrate a team of long-running agents from any MCP client.
Workflow diagnostics, capability routing, and x402 settlement for MCP-compatible agents.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/brooswit/butchr'
If you have feedback or need assistance with the MCP directory API, please join our Discord server