Claude Integration

From MintHCM Wiki

Info
Title Claude Integration
Claude Integration

Short Description

Connect Claude to your MintHCM instance via the Model Context Protocol (MCP) to query and update HR data in plain language.



Screens

Description

MintHCM connects to Claude through the Model Context Protocol (MCP), an open standard created by Anthropic. Once connected, you can ask Claude about your HR data in plain language, without opening MintHCM, building a report or writing a query.

MintHCM is open source (AGPL-3.0) and self-hosted. The MCP server runs on your own instance and Claude connects to it directly.

What you can do

Ask Claude things like:

  • "How many candidates do we have at the entry interview stage?"
  • "List employees whose contracts end in the next 90 days."
  • "Which applications came in last month, and what stage is each one at?"
  • "Run our headcount report and summarise what changed since last quarter."
  • "Total the hours logged on this project in September."
  • "Create a candidate record for Anna Kowalska, applied for the Java Developer role."
  • "Link this candidate to the Java Developer recruitment."
  • "Schedule a meeting with this candidate on Monday at 10:00."

Claude answers from live data in your own MintHCM instance: no exports, no report builder, no switching tabs.

What Claude can read and change

Claude works with the modules and fields configured in your instance and respects the permissions of the account you sign in with.

Claude can read:

  • Find and list records in any module, with filters (status, date range, assigned user and other fields)
  • Count records matching a condition
  • Sum numeric fields, such as hours or amounts, across filtered records
  • Show how records are linked to each other
  • Run your existing MintHCM reports and return the results
  • Look up which fields a module has

Claude can change, always with your confirmation first:

  • Create new records, such as a candidate, an employee or a meeting
  • Update fields on an existing record
  • Delete a record
  • Link two records together, or remove a link between them

Read-only questions run straight away. Anything that creates, changes or deletes data requires your approval in the conversation before it happens.

Before you start

  • MintHCM version 4.3.3 or later. The MCP server is part of the core since 4.2.0, but OAuth for remote connectors is available from 4.3.3.
  • The MCP server is not zero-config. The administrator needs to:
    1. Make sure the web server rules for the /mcp/ path and the OAuth endpoints are in place (the .htaccess rules introduced in 4.3.3; check the 4.3.3 release notes after updating). Apache needs mod_rewrite and AllowOverride All (or at least FileInfo).
    2. Give the relevant role permission to use the MCP tools.
  • A MintHCM user account. Claude only sees what that account is allowed to see.
  • A paid Claude plan (Pro, Max, Team or Enterprise).

Don't have MintHCM yet? Book a demo or download it from GitHub.

Connect

  1. Open Claude and go to Settings > Connectors.
  2. Find MintHCM in the directory and click Connect.
  3. Enter the address of your MintHCM MCP server, for example https://your-company.example.com/mcp/. Keep the trailing slash.
  4. Sign in with your MintHCM account on the page that opens and click Authorize.

You'll know it worked when Claude lists MintHCM among your connected tools.

Self-hosting without the directory

If you run MintHCM on a private network or prefer to configure the connection manually, you can add the server yourself. For example, in Claude Code: 

claude mcp add --transport http mint-mcp https://your-company.example.com/mcp/

Start claude, sign in and click Authorize in the browser tab that opens, then type /mcp to check that mint-mcp shows as connected.

[Video to be added]

Troubleshooting

The connection fails, or you see "Dynamic Client Registration not supported" or an HTTP 404 error

  • Check that AllowOverride All (or FileInfo) is set for the mcp/ directory in your Apache configuration. Without it, .htaccess is ignored.
  • Test the discovery address, for example curl -i https://your-company.example.com/mcp/.well-known/oauth-authorization-server. It should return 200 OK with JSON. A 404 means the rewrite rule isn't matching.
  • Check mcp/mintmcp.log on your instance for OAuth errors.

The connection hangs while waiting for a response Finish the sign-in in the browser. If no tab opened, remove the connection and add it again.

The server address returns a redirect, then a 404 or 405 error Make sure the address ends with a slash: /mcp/.

Claude says it can't find a record that exists in MintHCM Check the permissions of the MintHCM account you signed in with. Claude can only reach records that account can open.

Privacy and data

Claude connects directly to your MintHCM instance. Requests do not pass through eVolpe or MintHCM servers, and eVolpe does not store or track them.

Records that Claude reads become part of your conversation with Claude and are handled under the terms of your Claude plan. Access is limited to what your MintHCM account is allowed to see.

On your instance, the MCP server keeps a log of OAuth events (mcp/mintmcp.log: client registered, token issued, errors) without secrets. The log stays on your own server.

See our privacy policy for details.

Support


Scope

Mentioned in articles

Retrieved from "https://wiki.minthcm.org/index.php?title=Integration:Claude_Integration&oldid=6359"