HCM MCP Server for Oracle Fusion Cloud (unofficial)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HCM_BASE_URL | Yes | Base URL of the Oracle Fusion HCM pod (e.g., https://your-pod.fa.ocs.oraclecloud.com) | |
| HCM_PASSWORD | No | Password for Basic Authentication | |
| HCM_USERNAME | No | Username for Basic Authentication | |
| HCM_CLIENT_ID | No | Client ID for OAuth2 authentication | |
| HCM_TOKEN_URL | No | Token URL for OAuth2 authentication | |
| HCM_TRANSPORT | No | Transport type (e.g., stdio, http); default is stdio | stdio |
| HCM_CLIENT_SECRET | No | Client Secret for OAuth2 authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Report non-sensitive server configuration and enabled module flags. Safe to call without a live pod connection — useful for verifying a deployment's configuration before exercising the HCM API. |
| list_resourcesA | Search the catalog of common Oracle Fusion HCM REST resources. Works offline from a bundled seed list. Filter by |
| describe_resourceA | Return a resource's live schema: attributes, child collections, actions. Hits Oracle's |
| get_capabilitiesA | Report which HCM modules are live on this pod. For each module: its mode (on/off/auto) and discovered status
(enabled/disabled/provisioned/not_provisioned/no_access/unreachable).
Modules set to |
| query_resourceA | Query any Oracle Fusion HCM resource (the generic read workhorse).
|
| get_recordA | Fetch a single record by its key, optionally expanding child collections.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct responsibility: schema exploration (describe_resource), module status (get_capabilities), single record retrieval (get_record), resource catalog (list_resources), generic query (query_resource), and server configuration (server_info). No two tools overlap in purpose.
All tool names follow a consistent verb_noun pattern with snake_case: describe_resource, get_capabilities, get_record, list_resources, query_resource, server_info. The pattern is uniform and predictable.
With 6 tools, the set is concise yet covers the core needs for an HCM API exploration server: metadata discovery, querying, and configuration info. No tool is superfluous, and the count feels well-scoped for the domain.
The tool surface is complete for read and exploration tasks, providing schema discovery, resource catalog, and data retrieval. However, it lacks mutation operations (create/update/delete), which may be required for full HCM workflows, hence a minor gap.