
HCM MCP Server for Oracle Fusion Cloud (unofficial)
io.github.mohantyajiteshPublished by GitHub account mohantyajiteshv0.1.1Updated Oct 30, 2026
Open-source, write-capable MCP server for Oracle Fusion HCM. Safe by default. Unofficial.
Overview
Unofficial local MCP server that connects an assistant to Oracle Fusion Cloud HCM, with write-capable access that is safe by default.
- What you can do
- Connect an assistant to an Oracle Fusion Cloud HCM pod using a configured base URL and integration user.
- Work with HCM data through the server's tools, which the manifest does not enumerate.
- Perform write operations, which the description says are possible, with safe-by-default behavior.
- Adjust modules, feature flags, OAuth2 settings and limits through an optional config file or environment variables.
- When to use it
- Use it when an assistant needs to read or change Oracle Fusion HCM data in a specific pod, and you can supply an integration user and pod URL. It is unofficial, so verify behavior against your own environment before relying on it.
- Requirements
- Runs locally over stdio, launched with uvx from the PyPI package fusion-hcm-mcp-server. Requires HCM_BASE_URL (the Fusion pod base URL) and HCM_USERNAME (an integration user, ideally with least-privilege read-only HCM roles). The HCM_PASSWORD secret is needed unless stored in the OS credential store under service 'fusion-hcm-mcp-server'. An optional CONFIG_FILE points to a config.toml for modules, feature flags, OAuth2 and limits; environment variables override file values.
Installation
In SourceWeft
- Open HCM MCP Server for Oracle Fusion Cloud (unofficial) in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.