🌀
← Back to Articles & Artefacts
artefactseast

Expand the work potentially MantisBT (Mantis Bug Tracker) could be envisionned also as this will link the github issue to the service

IAIP Research
alt2github-orchestrate-multiple-agent-communication-thru-git

Expand the work potentially MantisBT (Mantis Bug Tracker) could be envisionned also as this will link the github issue to the service#

This is actually a very solid fit for your architecture. Here's the expanded picture.

MantisBT as an Agentic Workflow Hub#

MantisBT is self-hosted, open source, and PHP-based — meaning you own the full stack. Its REST API is enabled by default and ships with a Swagger sandbox at /api/rest/swagger/, making it immediately discoverable by agents without custom documentation. The key insight is that MantisBT wasn't designed for agentic use, but its structure maps well onto it.1

The MCP Layer — Already Exists#

This is the most immediately useful finding: a MantisBT MCP server already exists. Built with TypeScript, FastMCP, Axios, and Zod, it exposes MantisBT's REST API as type-safe MCP tools — meaning your agents can already call it through the standard MCP protocol to manage issues, projects, users, and notes. You can find it at mcpmarket.com/server/mantisbt and market-mcp.com/mcp/mantisbt.23

This directly answers your original need: an agent-readable system where agents can retrieve and update structured workflow state.

GitHub ↔ MantisBT Sync#

The Source Control Integration plugin + GitHub Integration plugin link commit messages to MantisBT issues bi-directionally. A commit message like "Fixed #42" auto-resolves the MantisBT issue and tags it with the changeset, branch, and author. The current limitation is that this is one-directional by default — GitHub commits update Mantis, but Mantis issues don't automatically open GitHub issues. A custom field acting as a gh_issue_id link is the common workaround.45

Envisioned Architecture#

Here's how you could layer this:

LayerToolRole
Issue registryMantisBTGround truth for tasks, workflows, states
Agent accessMantisBT MCP ServerAgents read/write issues via MCP protocol
Code linkageSource Control + GitHub pluginCommits reference MantisBT IDs, auto-close
OrchestratorLangGraph supervisorRoutes tasks, checks issue state, updates notes
Design conversationYour LLM (with MCP)Discusses workflow design, writes issues on your behalf
Workflow sequencesMantisBT custom fields + relationshipsEncode dependency chains between issues

MantisBT's issue relationships (parent/child, duplicate, related) become your workflow dependency graph, readable by agents through the REST API or MCP layer.12

What's Missing Natively#

  • No native bidirectional GitHub issue sync (Mantis → GitHub) without custom scripting5
  • No built-in workflow sequence runner — you'd use MantisBT as state store, with LangGraph doing the sequencing logic
  • The GitHub plugin was originally documented for devZing-hosted instances; self-hosted setup requires manual webhook configuration4

Suggested Deep Search Queries#

  1. "MantisBT MCP server FastMCP agent workflow state management — extending tools for workflow dependency traversal and sequence execution" — targets making the existing MCP server more than CRUD, giving agents the ability to walk dependency chains.
  2. "MantisBT GitHub bidirectional issue sync webhook 2024 2025 — open source plugin or script to mirror issue creation both ways" — targets the missing sync direction.
  3. "Self-hosted issue tracker as agent memory and workflow state store — MantisBT vs Plane vs Linear API agentic orchestration comparison" — useful if you want to evaluate whether MantisBT is the right choice vs newer trackers like Plane that were designed API-first. 67891011121314151617181920212223
⁂

Footnotes#

  1. https://mantisbt.org/docs/master/en-US/Developers_Guide/html/restapi.html ↩ ↩2

  2. https://mcpmarket.com/server/mantisbt ↩ ↩2

  3. https://market-mcp.com/mcp/mantisbt ↩

  4. https://docs.devzing.com/mantisbt-github-integration/ ↩ ↩2

  5. https://mantisbt.org/forums/viewtopic.php?t=24803 ↩ ↩2

  6. https://ieeexplore.ieee.org/document/11024348/ ↩

  7. https://ieeexplore.ieee.org/document/10685639/ ↩

  8. https://arxiv.org/abs/2601.12735 ↩

  9. https://www.semanticscholar.org/paper/7d634878c09e1ea3423ff7c62221160865600175 ↩

  10. https://github.com/franck-gaspoz/MantisBTRestAPIClient ↩

  11. https://documenter.getpostman.com/view/29959/mantis-bug-tracker-rest-api/7Lt6zkP ↩

  12. https://www.postman.com/avionics-participant-52825978/work/collection/frimrum/mantis-bug-tracker-rest-api ↩

  13. https://netflix.github.io/mantis/reference/api/ ↩

  14. https://aws.plainenglish.io/how-mcp-orchestrates-multi-agent-ai-for-saas-workflows-1aaba7aa8f0b ↩

  15. https://mantisbt.org/forums/viewtopic.php?t=24747 ↩

  16. https://support.monday.com/hc/en-us/articles/4413247738770-The-GitHub-Integration ↩

  17. https://aaif.io/blog/from-workflow-orchestration-to-agentic-orchestration/ ↩

  18. https://support.mantishub.com/api/rest_api ↩

  19. https://community.atlassian.com/forums/Jira-questions/Jira-github-integration-after-spring-2025-updates/qaq-p/3021875 ↩

  20. https://arxiv.org/abs/2512.08706 ↩

  21. https://ieeexplore.ieee.org/document/11029879/ ↩

  22. https://ieeexplore.ieee.org/document/11082076/ ↩

  23. https://arxiv.org/abs/2501.16945 ↩