MintHCM: a self-hosted HCM platform built for AI agents
Open-source HCM system for managing HR processes with AI agents. Full data ownership, MCP/A2A-native, no vendor lock-in.
At a glance
- What is it?
- MintHCM is an AGPL-3.0 human capital management system that runs on PHP 8.2, MySQL 8.0 and Apache2, and ships an MCP server so agents can work against HR data you host yourself. The trade-off is that you operate a SuiteCRM-derived stack, not a SaaS product.
- Who is it for?
- Adopt MintHCM if you run HR processes that need deep customization, want the data inside your own network, and have PHP developers who can read a SuiteCRM-derived codebase. Do not adopt it if you want a hosted product with a support contract and no server to patch, or if nobody on the team can maintain a LAMP stack.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 9 days ago.
- What is it written in?
- Mainly PHP, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 30, 2026, and from our analysis. They are not legal advice.
Editorial analysis
The gap MintHCM aims at: HR data you host, with agents that can reach it
Most HR software forces a choice. SaaS suites give you a working product and take custody of employee records. Open-source HR tools give you the code but leave agent integration as your own project. MintHCM positions itself against both, describing traditional SaaS HR as having no data sovereignty and no deep customization, and other open-source HR tools as having full control but no native AI agent ecosystem. The claim is that MintHCM is agent-ready by design rather than AI features bolted on, with MCP, WebMCP and A2A named in the README as part of the architecture. The audience the README names is specific: enterprises with complex HR processes, organizations adopting AI in operations, companies that require full control over data and infrastructure, and system integrators. That last group matters. This is a platform you customize at framework level, not a product you configure through a settings screen, and the repository is honest that it builds on SugarCRM Community Edition and SuiteCRM, which is why the project says MintHCM is CRM reinvented. If you have never administered either of those, the shape of the codebase will be unfamiliar.
How the pieces fit: PHP application, MCP server, Vue front end
The top-level repository layout tells you most of the architecture. index.php is the entry point of the PHP application. install/ and upgrade/ hold the installer and the upgrade path. api/ is the integration surface, and the README points to a separate guide because the API is only similar to SuiteCRM's, with differences the project documents explicitly. mcp/ is the MCP server that exposes HR data and processes to MCP-compatible agents, and the README also names A2A for agent-to-agent workflows and A2UI/AGUi for human-to-agent interfaces. vue/ and kanban/ hold front-end code, and legacy/ carries the inherited SugarCRM and SuiteCRM material. MintCLI sits at the top level as a command-line tool. The data model is described as flexible, and the README lists the functional surface: recruitment and candidate management, onboarding and offboarding, employee profiles and employment history, competences and evaluations, time and attendance, leave management, performance and development, organizational structure, job descriptions, resources booking, and reporting. Model choice is left to you. The README states MintHCM is LLM-agnostic and names OpenAI, Anthropic, Mistral, local Llama and regional sovereign LLMs as options, with no forced dependency on a single AI vendor.
Installing MintHCM and connecting a first agent
The README does not inline installation steps. It points to the installation guide at minthcm.org/support/minthcm-installation-guide/, and the stated requirements are a Linux or Windows machine running Apache2, PHP 8.2 and MySQL 8.0. A docker/ directory exists in the repository and the README carries a Docker Hub badge for minthcm/minthcm, so a container path is published, but the README itself does not give the docker run invocation. Treat the guide as the source of truth for the exact commands. What you can check before starting is that your environment matches the three requirements above: PHP 8.2, MySQL 8.0, and Apache2 on Linux or Windows.
The second thing to read before writing integration code is the API guide at minthcm.org/support/how-to-use-mint-api/. The README is explicit that MintHCM is based on SuiteCRM and the API is very similar, but that there are important differences covered in that guide. If you have existing SuiteCRM client code, do not assume it works unchanged.
The repository itself shows where each piece lives. The top-level entries include api/, mcp/, docker/, install/, upgrade/, vue/, kanban/, legacy/, MintCLI and index.php. Listing them tells you what ships for integration and for agent access:
ls api/
ls mcp/From there, the README's stated path is to connect HR data and processes to any MCP-compatible agent through the MCP server, with A2A available for multi-agent workflows. The README also notes a built-in AI agent that is ready to use out of the box, and states that custom agents can be built on HR data and processes.
Where MintHCM is the wrong tool
The requirement list is the first limitation, and it is not negotiable in the README's wording. Apache2, PHP 8.2 and MySQL 8.0 are named as the stack. If your organization standardized on nginx, PostgreSQL, or a PHP version other than 8.2, you are adapting the deployment rather than following it. The second limitation is the inherited codebase. MintHCM is built on SugarCRM Community Edition and SuiteCRM, and the repository keeps a legacy/ directory for that material. Deep customization means working inside that structure, which is a different skill from configuring an HR product. The README's own framing supports this: framework-level customization with full code and data-model control, not just configuration. The third limitation is operational. Nothing in the README describes a hosted option, a support contract, or a managed upgrade service. Upgrade paths exist in the repository as an upgrade/ directory and releases are tagged, with 4.3.2.2 published on 2026-08-20, but applying them is your responsibility. If you want HR software where someone else patches the server, this is the wrong category of tool. Finally, the README does not document rollback after an upgrade, and it does not describe a migration path off MintHCM. Both are worth confirming with the project before you commit production employee records.
MintHCM against SuiteCRM, which it is built on
The most useful comparison is not against a SaaS suite, because the difference there is obvious. It is against SuiteCRM, the project MintHCM derives from. SuiteCRM is a CRM: accounts, contacts, opportunities, campaigns. Its data model is organized around customers and revenue. MintHCM reuses that foundation and rebuilds the domain around employment: recruitment and candidates, onboarding and offboarding, employee profiles and employment history, competences and evaluations, time and attendance, leave management, performance and development, organizational structure, job descriptions, resources booking. The README describes this as reintroducing some features, redesigning others, and providing a new system. The second difference is the agent layer. SuiteCRM does not ship an MCP server, and MintHCM's README presents MCP, WebMCP, A2A and A2UI/AGUi as part of the architecture rather than as integrations you build. If your team already runs SuiteCRM and wants HR functions, MintHCM is the closer starting point than extending the CRM. If your team runs SuiteCRM for sales and is evaluating MintHCM for HR, expect two systems with shared ancestry and a shared upgrade discipline, not one system with an extra module.
Licence, upgrade cost and what AGPL-3.0 means here
MintHCM is licensed AGPL-3.0. The README contrasts this with alternatives by stating there are no gated features, no enterprise-only fork, and no phone-home telemetry. That is a meaningful commitment for an HR system, because it means the same code you can read is the code you run. The AGPL is a copyleft licence with a network clause, and the practical consequence for a self-hosted deployment is that modifications you make available to users over a network carry source-disclosure obligations. This is not legal advice; if you plan to modify MintHCM and expose it to employees or customers, have counsel read the licence rather than relying on a summary. On upgrade cost, the repository gives you upgrade/ and versioned releases, and the project publishes release notes per tag. The README does not describe an automated upgrade service, a long-term support branch, or a rollback procedure. Budget for a maintenance window and a test environment each time you move between releases. The translation workflow is separate: the README points to a Crowdin project for downloading and contributing language packages, so localization work happens outside the main repository.
Editorial conclusion
Adopt MintHCM if you run HR processes that need deep customization, want the data inside your own network, and have PHP developers who can read a SuiteCRM-derived codebase. Do not adopt it if you want a hosted product with a support contract and no server to patch, or if nobody on the team can maintain a LAMP stack. Before committing, verify the installation guide against your target PHP and MySQL versions, confirm the docker/ directory matches the deployment model you plan to run, and read the API differences guide because the README states the MintHCM API is only similar to SuiteCRM's, not identical.
Frequently asked questions
How do I install MintHCM?
The README does not inline the steps; it points to the installation guide at minthcm.org/support/minthcm-installation-guide/. The stated requirements are Linux or Windows running Apache2, PHP 8.2 and MySQL 8.0, and the repository also contains a docker/ directory with a published Docker Hub image.
Is the MintHCM API the same as the SuiteCRM API?
The README states that MintHCM is based on SuiteCRM so the API is very similar, but that there are important differences covered in a separate guide at minthcm.org/support/how-to-use-mint-api/. Existing SuiteCRM client code should be checked against that guide rather than assumed to work.
Does MintHCM work with any LLM provider?
The README describes MintHCM as LLM-agnostic and names OpenAI, Anthropic, Mistral, local Llama and regional sovereign LLMs as options, stating there is no forced dependency on a single AI vendor. Agent access to HR data and processes is presented through the MCP server in the mcp/ directory.
What are the MintHCM system requirements?
The README lists a Linux or Windows machine running Apache2, PHP 8.2 and MySQL 8.0. Those are stated as the requirements, not as minimums.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/minthcm-minthcm)