Create a connection
Fill in the form
In New Connection, enter a Name, the Oracle URL (your pod base URL), a Username, and a Password.
The moment you save, ORCA starts background metadata discovery against the pod — you don’t trigger it manually.
Metadata discovery
A Discovery row of chips appears on the connection card, one per source. Each starts grey (never run), spins while it works (pending → running), and turns green (done) with an object count — or red (failed) if the pod refused. Re-trigger the whole sweep any time with the Re-run discovery button.
| Source | Discovers | Feeds |
|---|---|---|
rest | HCM + FSCM REST resource catalog | The “Discovered APIs” table and the chat/query tools |
hdl | HCM Data Loader business objects | HDL generation for HCM conversions |
fbdi | Finance / SCM / Projects import processes | The “FBDI Processes” table and FBDI loads |
table | Table / column comments (SQL only) | search_tables; skipped when SQL is off |
Two more chips (
fsm, soap) render but are placeholders today — they always record as skipped. For HCM work, rest and hdl are the ones that matter.What a connection powers
One connection powers ORCA chat, the conversion loads a cycle submits, and the MCP connector that lets Claude query the pod from outside the app. Flip the MCP toggle and ORCA surfaces a shared OAuth URL (recommended) plus a legacy token URL.Connect Claude to ORCA
Query your Oracle data from Claude Desktop or Claude Code over MCP.
Next steps
Governed REST vs SQL
How ORCA stays inside your Oracle security — and when SQL is allowed.