Open-source, write-capable MCP server for Oracle Fusion HCM. Safe by default. Unofficial.
HCM For Oracle Fusion Cloud (Unofficial) MCP server exists for a simple reason — assistants are far more useful when they can act on HCM For Oracle Fusion Cloud (Unofficial) directly instead of describing what you should do. Open-source, write-capable MCP server for Oracle Fusion HCM. Safe by default. Unofficial.
An MCP server that lets AI models interact with Oracle Fusion Cloud HCM across its entire REST surface — workers, org structures, compensation, absence, payroll, recruiting, talent, learning and more — without hand-coding a tool per endpoint.
Once HCM For Oracle Fusion Cloud (Unofficial) is connected, these are the calls the assistant has available:
Group — ToolsDiagnostics — server_infoDiscovery — list_resources · describe_resource · get_capabilitiesRead — query_resource · get_recordWorkflows — find_worker · get_worker_profile · list_direct_reports · get_reporting_chain · lookup_org · get_current_compensation · list_absencesWrites — mutate_record · run_action (gated by features.writes_enabled, dry-run default, schema-validated)Configure — Required: server.base_url (or HCM_BASE_URL). Credentials should come from environment variables (HCM_USERNAME/HCM_PASSWORD, orBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 4 environment variables: HCM_BASE_URL, HCM_CLIENT_ID, HCM_CLIENT_SECRET, HCM_TOKEN_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. HCM For Oracle Fusion Cloud (Unofficial)'s toolset — Group, Diagnostics, Discovery and 4 more — is a fair guide to whether it matches your workflow. It is maintained by mohantyajitesh; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Group | Tools |
| Diagnostics | server_info |
| Discovery | list_resources · describe_resource · get_capabilities |
| Read | query_resource · get_record |
| Workflows | find_worker · get_worker_profile · list_direct_reports · get_reporting_chain · lookup_org · get_current_compensation · list_absences |
| Writes | mutate_record · run_action (gated by features.writes_enabled, dry-run default, schema-validated) |
| Configure | Required: server.base_url (or HCM_BASE_URL). Credentials should come from environment variables (HCM_USERNAME/HCM_PASSWORD, or HCM_CLIENT_ID/HCM_CLIENT_SECRET/HCM_TOKEN_URL), never the committed file. See [config.example |
{
"mcpServers": {
"fusion-hcm": {
"command": "uvx",
"args": ["fusion-hcm-mcp-server"],
"env": {
"HCM_BASE_URL": "your-value",
"HCM_CLIENT_ID": "your-value",
"HCM_CLIENT_SECRET": "your-value",
"HCM_TOKEN_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| HCM_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| HCM_CLIENT_ID | Configuration value read at startup. | Optional |
| HCM_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| HCM_TOKEN_URL | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.