> ## Documentation Index
> Fetch the complete documentation index at: https://docs.btsscorp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect to Claude

> Query your Oracle Fusion data from Claude over MCP — governed, within your own Oracle security

ORCA lets you work with your Oracle Fusion (SaaS) data in plain language — every request is **governed** and runs **within your own Oracle security**. Whatever your role, ORCA puts our consultants' expertise on tap: the same checks, lookups, and playbooks a seasoned Oracle practitioner would run — a question away, no ticket, no wait.

The same governed agent — **same skills, same consent rules** — is reachable from **Claude Desktop** or **Claude Code** over MCP (Model Context Protocol). Connect it to Claude once and just ask.

## Prerequisites

<Steps>
  <Step title="An Oracle connection with MCP enabled">
    In **Settings → Oracle Connections**, flip the **MCP** toggle on the connection you want to expose.
  </Step>

  <Step title="Your MCP URL">
    ORCA shows your MCP URL in the app (it looks like `https://<your-orca-host>/api/mcp`). There's **no token in the URL** — you authenticate by signing in to ORCA.
  </Step>
</Steps>

## Claude Desktop

<Steps>
  <Step title="Open Claude settings">
    In Claude Desktop, open **Settings**.

    <Frame>
      <img src="https://mintcdn.com/btsscorp/N8LxhuhJM-s9OUIJ/images/mcp-guide/01-customize.png?fit=max&auto=format&n=N8LxhuhJM-s9OUIJ&q=85&s=4326e48fb6e78054d23c35caf9b6bc38" alt="Claude Desktop settings" width="802" height="372" data-path="images/mcp-guide/01-customize.png" />
    </Frame>
  </Step>

  <Step title="Go to Connectors">
    Select the **Connectors** section.

    <Frame>
      <img src="https://mintcdn.com/btsscorp/N8LxhuhJM-s9OUIJ/images/mcp-guide/02-connectors.png?fit=max&auto=format&n=N8LxhuhJM-s9OUIJ&q=85&s=28f234a9c3e1b1d8710c73553ad5de72" alt="Connectors section in Claude settings" width="482" height="280" data-path="images/mcp-guide/02-connectors.png" />
    </Frame>
  </Step>

  <Step title="Add a custom connector">
    Click **Add custom connector**.

    <Frame>
      <img src="https://mintcdn.com/btsscorp/N8LxhuhJM-s9OUIJ/images/mcp-guide/03-add-custom.png?fit=max&auto=format&n=N8LxhuhJM-s9OUIJ&q=85&s=e05b4d288addab1308e259a96ac3b1dc" alt="Add custom connector dialog" width="1400" height="224" data-path="images/mcp-guide/03-add-custom.png" />
    </Frame>
  </Step>

  <Step title="Name it and paste the URL, then Add & connect">
    Give it any name you like — **ORCA** works well (the name is just a local label). Paste your MCP URL, click **Add**, then **Connect**.

    <Frame>
      <img src="https://mintcdn.com/btsscorp/N8LxhuhJM-s9OUIJ/images/mcp-guide/05-add-and-connect.png?fit=max&auto=format&n=N8LxhuhJM-s9OUIJ&q=85&s=400c4d37be01e9a31930e8eea38ef0da" alt="Naming the connector and pasting the MCP URL" width="1154" height="1040" data-path="images/mcp-guide/05-add-and-connect.png" />
    </Frame>
  </Step>

  <Step title="Sign in to ORCA & approve a connection">
    Claude opens your browser. Sign in to ORCA, then pick the Oracle connection to grant and click **Approve**. Your Oracle credentials never leave ORCA — Claude only receives a short-lived, scoped token.

    <Frame>
      <img src="https://mintcdn.com/btsscorp/N8LxhuhJM-s9OUIJ/images/mcp-guide/06-login.png?fit=max&auto=format&n=N8LxhuhJM-s9OUIJ&q=85&s=080d21814d2d74ee55529b439ce04603" alt="Signing in to ORCA and approving a connection" width="776" height="508" data-path="images/mcp-guide/06-login.png" />
    </Frame>
  </Step>

  <Step title="Allow the tools">
    Approve the tool permissions (**Always allow for all tools** is fine). Done — ask away in any chat.

    <Frame>
      <img src="https://mintcdn.com/btsscorp/N8LxhuhJM-s9OUIJ/images/mcp-guide/07-allow-tools.png?fit=max&auto=format&n=N8LxhuhJM-s9OUIJ&q=85&s=0636e84591d14aa7ea8e4835f8b9f911" alt="Allowing the ORCA tools in Claude" width="1486" height="1102" data-path="images/mcp-guide/07-allow-tools.png" />
    </Frame>
  </Step>
</Steps>

## Claude Code (CLI)

Same flow — add the server once, then Claude Code opens your browser for the identical sign-in and consent. Run `/mcp` to trigger or inspect auth.

```bash theme={null}
claude mcp add --transport http orca <YOUR_MCP_URL>
```

## How access stays governed

* You sign in to ORCA and approve which Oracle connection Claude may use.
* Claude receives a short-lived, scoped token — your Oracle credentials never leave ORCA.
* Every request runs within your own Oracle security, exactly as it does inside the app. Governed **REST** is the default path; **SQL**, if enabled on the connection, still asks for consent and labels its answers.

## Skills that keep getting better

The connector ships with **skills** — pre-built expert playbooks with pre-validated Oracle calls that a seasoned consultant would run. Claude reaches for the right one automatically when your question matches its shape.

<CardGroup cols={1}>
  <Card title="Fusion Security Posture" icon="user-shield">
    Role assignments, data access, security profiles, and AOR for a user.
  </Card>

  <Card title="Worker Scheduling" icon="calendar-days">
    What shift someone works, schedules, rosters, and who's on a given day.
  </Card>

  <Card title="Workforce Counts" icon="users">
    Headcount and worker-type breakdowns.
  </Card>
</CardGroup>

<Info>
  We ship **new skills continually** — and they're delivered to your connector automatically. Your ORCA connector gets smarter over time with nothing to install or configure on your side.
</Info>

## Build dashboards, not just answers

Because ORCA answers over MCP, any **MCP client** — an AI assistant that speaks the protocol, such as Claude Desktop or Claude Code — can do more than return a single answer. Ask it to chart the results, assemble a report, or stand up a **live dashboard** over your governed Oracle data, and it queries ORCA for the numbers and builds the view for you. The data stays within your own Oracle security the whole time.

<CardGroup cols={1}>
  <Card title="Turn a question into a dashboard" icon="chart-column">
    * "Build me a workforce dashboard: headcount by department and location, with month-over-month trend."
    * "Chart active workers by location, then lay it out as a report I can share."
    * "Track FBDI import processes for General Ledger and show their status at a glance."
  </Card>
</CardGroup>

## What you can ask

Plain-language questions across users, roles, security, HCM data, and analytics — a few to get started:

<CardGroup cols={3}>
  <Card title="Business users">
    * "Investigate the gender distribution across the company and chart it."
    * "Show me headcount by department, and flag any that grew more than 10% this year."
    * "How many active workers do we have by location? Put it in a bar chart."
  </Card>

  <Card title="Implementers & consultants">
    * "Audit the data-access permissions and security profiles for a given user."
    * "Which roles grant access to payroll data, and how does row-level access resolve?"
    * "List the FBDI import processes available for General Ledger."
  </Card>

  <Card title="Support agents">
    * "Does user JSMITH exist, and what roles are assigned to them?"
    * "Why can this user see that employee's record — walk me through it."
    * "What shift is a given worker scheduled for this week?"
  </Card>
</CardGroup>