The tool set is small because it is shaped around one routine: read CurrMonth, run the aggregation, wait for the job, validate the numbers with an export, move the variable to the next month, read it back to confirm. Mock mode matters more than it sounds — it lets you rehearse that whole chain and see the shape of every response before anyone has to approve a connection to a production planning environment.
A client for the Oracle EPM Cloud REST APIs. Seven tools cover the calls a planning administrator makes by hand through Postman or EPM Automate, and a mock mode answers all of them from sample data before any credentials exist.
- get_api_version tests connectivity and reports the API versions the environment exposes, against GET /HyperionPlanning/rest/.
- list_applications returns the EPM applications in the environment.
- get_substitution_variables reads the current month, year and scenario variables that drive everything else.
- update_substitution_variable writes one back — the step that rolls a period forward.
- run_business_rule submits a calc script or business rule as a job.
- check_job_status polls the returned job id for completion or error.
- export_data_slice pulls data out of the cube by dimension members.
Node.js 18+, or the packaged .mcpb extension for Claude Desktop, which installs without editing a config file. Mock mode is the default and needs no Oracle credentials. Live mode takes EPM_MODE, EPM_BASE_URL, EPM_USERNAME, EPM_PASSWORD and EPM_APP_NAME as environment variables. The REST APIs use Basic Authentication and the username must be written as identitydomain.username — the wrong form is what produces a 401. An account with multi-factor authentication cannot use Basic Auth at all, and OAuth 2.0 is not in this version.