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.¹

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.²³

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.⁴⁵

Envisioned Architecture

Here's how you could layer this:

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

What's Missing Natively

• No native bidirectional GitHub issue sync (Mantis → GitHub) without custom scripting⁵
• 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 configuration⁴

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. <span style="display:none">^{67891011121314151617181920212223}</span>