# Cornerstone OnDemand MCP connector

Connect Cornerstone OnDemand to Elaichi once and Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can look up users, answer employee approvals, maintain org units and check bulk imports, each person under their own access.

Source: https://elaichi.ai/connectors/cornerstoneondemand/

## Facts

| | |
| --- | --- |
| Application | Cornerstone OnDemand |
| Category | HRIS |
| AI tools | 409 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Cornerstone OnDemand is connected

- Which training approvals are waiting on me right now?
- Find the org unit Priya Shah sits in
- Did last night's bulk import of new hires have any errors?

## Connect Cornerstone OnDemand in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Cornerstone OnDemand.
2. Optionally set Share with, then press Connect.
3. Paste your Cornerstone OnDemand app credentials. Cornerstone OnDemand authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Cornerstone OnDemand tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Cornerstone OnDemand MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Cornerstone OnDemand MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Cornerstone OnDemand MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Cornerstone OnDemand MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Cornerstone OnDemand MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Cornerstone OnDemand to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Cornerstone OnDemand tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Cornerstone OnDemand through Elaichi

### Find an employee record in seconds

HR Operations. Ask for a person by name and get their Cornerstone OnDemand user record and the org unit they sit in, without clicking through the admin screens.

### Clear the approvals waiting on you

Managers. See every employee approval sitting in your Cornerstone OnDemand queue and respond to each one from the chat you already have open.

### Keep the org structure current after a reorg

People Operations. Create, rename or retire custom organizational units in Cornerstone OnDemand as teams move, and check the legacy org units they replace.

### Check a bulk import before anyone complains

IT. Pull the error and warning reports for last night's Cornerstone OnDemand import and find out which rows failed and why.

### Load a batch of new hires

Onboarding. Upload a bulk file of new starters to Cornerstone OnDemand, start the job, and follow it through to completion without leaving the conversation.

### Reset a password without a ticket

IT. Update a user's Cornerstone OnDemand password on request, with the change recorded against the person who asked for it.

## Elaichi vs Zapier MCP vs Composio for Cornerstone OnDemand

All three can connect Cornerstone OnDemand to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Cornerstone OnDemand tools | Allow or restrict single Cornerstone OnDemand tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Cornerstone OnDemand call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Cornerstone OnDemand to Claude?

Connect Cornerstone OnDemand in Elaichi by entering the app credentials your Cornerstone OnDemand administrator provides. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and Cornerstone OnDemand is ready to use.

### Does Cornerstone OnDemand work with ChatGPT and Cursor as well as Claude?

Yes. Once Cornerstone OnDemand is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Cornerstone OnDemand once and every client picks it up.

### What can an AI agent actually do with my Cornerstone OnDemand data?

An agent connected to Cornerstone OnDemand can search for users, list the employee approvals waiting on you and respond to them, look up org units, and create or update custom organizational units. It can also upload bulk imports, start and track bulk jobs, and read the error and warning reports those jobs produce. Short, specific asks such as "show my pending approvals" work better than long paragraphs.

### Does connecting Cornerstone OnDemand give the AI access to everything in my portal?

No. Every call to Cornerstone OnDemand runs as the person who signed in, so an agent sees only the users, approvals and org units that person could already see in Cornerstone OnDemand itself. Elaichi can narrow that access further with roles and restrictions, and it never widens it.

### Can my team share one Cornerstone OnDemand connection?

Yes. One administrator connects Cornerstone OnDemand in Elaichi and shares the connection with a team, and nobody else ever handles the app credentials. Each person still signs in to Elaichi as themselves, so the audit log names who looked up a user or responded to an approval.

### Can I stop an agent from deleting or changing things in Cornerstone OnDemand?

Yes. Restrictions in Elaichi apply per action, so you can allow searching Cornerstone OnDemand users while restricting deleting org units or updating passwords, on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Cornerstone OnDemand connection when someone leaves?

Offboarding a person in Elaichi ends their access to Cornerstone OnDemand at once, in every client they used. A shared Cornerstone OnDemand connection keeps working for everyone else on the team. If you ever want to remove Cornerstone OnDemand entirely, disconnecting it once in Elaichi removes it from every client.

### Does the Cornerstone OnDemand MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Cornerstone OnDemand is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Cornerstone OnDemand?

Yes. Both let Claude, ChatGPT or Cursor use Cornerstone OnDemand. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Cornerstone OnDemand call.

### How is Elaichi different from Composio for Cornerstone OnDemand?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Cornerstone OnDemand: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 409 Cornerstone OnDemand tools

Every tool below is callable through https://api.elaichi.ai/mcp once Cornerstone OnDemand is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Cornerstone OnDemand bulk get specification** (Get). Get the OpenApi v3 Specification for Bulk API to see portal-specific request objects for creating Jobs and requesting Schema. Bulk API (GET /services/api/x/bulk-api/v1/specification). OAuth scope: bulkapispecification:read.
- **Cornerstone OnDemand bulk get schema** (Get). Schema that defines what kind of data can be loaded. Bulk API (POST /services/api/x/bulk-api/v1/schemas). OAuth scope: bulkapischema:read.
- **Cornerstone OnDemand bulk get permissions** (Get). Get a list of permissions assigned to users required to execute specified load types. Bulk API (GET /services/api/x/bulk-api/v1/permissions).
- **List all Cornerstone OnDemand bulk jobs** (List). Search for a Bulk API Jobs in a given date range. Bulk API (GET /services/api/x/bulk-api/v1/jobs). OAuth scope: bulkapijob:read. Required: job_create_from_date, job_create_to_date.
- **Create a Cornerstone OnDemand bulk job** (Create). Create a Bulk API job. Bulk API (POST /services/api/x/bulk-api/v1/jobs). OAuth scope: bulkapijob:create. Required: imports.
- **Get single Cornerstone OnDemand bulk job by ID** (Get). Get the Status for each of the imports in the job. Bulk API (GET /services/api/x/bulk-api/v1/jobs/{jobId}). The id is the job id. OAuth scope: bulkapijob:read. Required: id.
- **Cornerstone OnDemand bulk imports get report** (Get). Get a CSV report that contains the records that were not loaded, or were loaded with warnings. Bulk API (GET /services/api/x/bulk-api/v1/imports/{importId}/report). OAuth scope: bulkapiimport:read. Required: import_id.
- **Cornerstone OnDemand bulk imports get error report** (Get). Get a CSV report that contains the records that were not loaded. Bulk API (GET /services/api/x/bulk-api/v1/imports/{importId}/report/errors). OAuth scope: bulkapiimport:read. Required: import_id.
- **Cornerstone OnDemand bulk imports get warning report** (Get). Get a CSV report that contains the records that were loaded with warnings. Bulk API (GET /services/api/x/bulk-api/v1/imports/{importId}/report/warnings). OAuth scope: bulkapiimport:read. Required: import_id.
- **Cornerstone OnDemand bulk imports upload** (Upload). Send data to an Import to begin processing. Bulk API (POST /services/api/x/bulk-api/v1/imports/{importId}). OAuth scope: bulkapiimport:load. Required: import_id.
- **List all Cornerstone OnDemand bulk keys** (List). Get a list of active Encryption Keys. Bulk API (GET /services/api/x/bulk-api/v1/keys).
- **Create a Cornerstone OnDemand bulk key** (Create). Create an Encryption Key to use when sending sensitive data. Bulk API (POST /services/api/x/bulk-api/v1/keys). Required: name.
- **Get single Cornerstone OnDemand bulk key by ID** (Get). Returns public key for a given key id. Bulk API (GET /services/api/x/bulk-api/v1/keys/{keyId}). The id is the key id. Required: id.
- **List all Cornerstone OnDemand user search** (List). Global Search. Use this API to search for people, training, and certifications in Cornerstone. - The API considers the LO Availability of the user associated with the OAuth 2.0 application. Core and HR API (GET /services/api/Core/GlobalSearch). OAuth scope: globalsearch:read. Required: SearchText.
- **List all Cornerstone OnDemand employee approvals** (List). Use this endpoint to fetch all pending approval items for the supported approval types for a given user. Note that the user included in the request must have the required permissions to fetch approval data using this API. Core and HR API (GET /services/api/Employee/{userName}/approvals). OAuth scope: approval:read. Required: user_name.
- **Cornerstone OnDemand employee approvals respond** (Action). Use this endpoint to approve or deny a pending approval item. Core and HR API (POST /services/api/Employee/{userName}/approvals). OAuth scope: approval:create. Required: user_name.
- **List all Cornerstone OnDemand legacy org units** (List). Use this endpoint to retrieve OU details. Core and HR API (GET /services/api/OrgUnits/OU). OAuth scope: ou:read. Required: truto_organizational_units.
- **Update a Cornerstone OnDemand user password by ID** (Update). Password Management. Use this endpoint to update the password for a user. Core and HR API (PUT /services/api/x/authentication/v1/users/{userId}/password). The id is the user id. Required: id.
- **List all Cornerstone OnDemand custom ou types** (List). List the custom OU types. Use this endpoint to discover which custom OU types the portal has configured. Each entry carries an ouTypeId, and that value is the {ouTypeId} path segment every other custom OU endpoint needs. Core and HR API (GET /services/api/x/chr-jobmgmt-app/v1/custom-ou-types). OAuth scope: ou:read.
- **List all Cornerstone OnDemand custom ous** (List). List an OU type's custom OUs. Use this endpoint to fetch custom OUs in bulk. Core and HR API (GET /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous). OAuth scope: ou:read. Required: ou_type_id.
- **Create a Cornerstone OnDemand custom ous** (Create). Create a custom OU. Use this endpoint to add a custom OU to the OU type named in the path. Core and HR API (POST /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous). OAuth scope: ou:create. Required: ou_type_id, active, dateEffective, defaultCultureCode, globalCode, titles.
- **Delete a Cornerstone OnDemand custom ous by ID** (Delete). Archive a custom OU. Use this endpoint to archive a custom OU. Core and HR API (DELETE /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous/{customOuId}). The id is the custom ou id. OAuth scope: ou:delete. Required: id, ou_type_id.
- **Get single Cornerstone OnDemand custom ous by ID** (Get). Get a single custom OU. Use this endpoint to fetch one custom OU by its identifier, within its OU type. Core and HR API (GET /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous/{customOuId}). The id is the custom ou id. OAuth scope: ou:read. Required: id, ou_type_id.
- **Update a Cornerstone OnDemand custom ous by ID** (Update). Update a custom OU. Use this endpoint to change a custom OU's content with a JSON Merge Patch (application/merge-patch+json). Core and HR API (PATCH /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous/{customOuId}). The id is the custom ou id. OAuth scope: ou:update. Required: id, ou_type_id.
- **Cornerstone OnDemand custom ous list children** (List). List a custom OU's children. Use this endpoint to fetch the custom OUs whose current parent is the supplied one. Core and HR API (GET /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous/{customOuId}/children). OAuth scope: ou:read. Required: ou_type_id, custom_ou_id.
- **List all Cornerstone OnDemand custom ou parents** (List). List a custom OU's parent assignments. Core and HR API (GET /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous/{customOuId}/parents). OAuth scope: ou:read. Required: ou_type_id, custom_ou_id.
- **Create a Cornerstone OnDemand custom ou parent** (Create). Add a parent assignment to a custom OU. Core and HR API (POST /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous/{customOuId}/parents). OAuth scope: ou:create. Required: ou_type_id, custom_ou_id, dateEffective, parentCustomOuId.
- **Delete a Cornerstone OnDemand custom ou parent by ID** (Delete). Remove a custom OU's parent assignment. Use this endpoint to delete one item from a custom OU's parent timeline. Core and HR API (DELETE /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous/{customOuId}/parents/{assignmentId}). The id is the assignment id. OAuth scope: ou:delete. Required: id, ou_type_id, custom_ou_id.
- **Update a Cornerstone OnDemand custom ou parent by ID** (Update). Update a custom OU's parent assignment. Core and HR API (PATCH /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous/{customOuId}/parents/{assignmentId}). The id is the assignment id. OAuth scope: ou:update. Required: id, ou_type_id, custom_ou_id.
- **List all Cornerstone OnDemand custom ou statuses** (List). List a custom OU's status assignments. Use this endpoint to read a custom OU's status timeline, that is the record of when it has been active and when inactive. Core and HR API (GET /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous/{customOuId}/statuses). OAuth scope: ou:read. Required: ou_type_id, custom_ou_id.
- **Create a Cornerstone OnDemand custom ou status** (Create). Add a status assignment to a custom OU. Core and HR API (POST /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous/{customOuId}/statuses). OAuth scope: ou:create. Required: ou_type_id, custom_ou_id, active, dateEffective.
- **Delete a Cornerstone OnDemand custom ou status by ID** (Delete). Remove a custom OU's status assignment. Use this endpoint to delete one item from a custom OU's status timeline. Core and HR API (DELETE /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous/{customOuId}/statuses/{assignmentId}). The id is the assignment id. OAuth scope: ou:delete. Required: id, ou_type_id, custom_ou_id.
- **Update a Cornerstone OnDemand custom ou status by ID** (Update). Update a custom OU's status assignment. Core and HR API (PATCH /services/api/x/chr-jobmgmt-app/v1/custom-ou-types/{ouTypeId}/ous/{customOuId}/statuses/{assignmentId}). The id is the assignment id. OAuth scope: ou:update. Required: id, ou_type_id, custom_ou_id.
- **List all Cornerstone OnDemand job functions** (List). List job functions. Use this endpoint to fetch job functions in bulk. Core and HR API (GET /services/api/x/chr-jobmgmt-app/v1/job-functions). OAuth scope: function:read.
- **Create a Cornerstone OnDemand job function** (Create). Create a job function. Use this endpoint to add a job function to the Structure taxonomy. Core and HR API (POST /services/api/x/chr-jobmgmt-app/v1/job-functions). OAuth scope: function:create. Required: active, dateEffective, defaultCultureCode, globalCode, titles.
- **Delete a Cornerstone OnDemand job function by ID** (Delete). Archive a job function. Use this endpoint to archive a job function. Core and HR API (DELETE /services/api/x/chr-jobmgmt-app/v1/job-functions/{jobFunctionId}). The id is the job function id. OAuth scope: function:delete. Required: id.
- **Get single Cornerstone OnDemand job function by ID** (Get). Get a single job function. Use this endpoint to fetch one job function by its identifier. Core and HR API (GET /services/api/x/chr-jobmgmt-app/v1/job-functions/{jobFunctionId}). The id is the job function id. OAuth scope: function:read. Required: id.
- **Update a Cornerstone OnDemand job function by ID** (Update). Update a job function. Use this endpoint to change a job function's content with a JSON Merge Patch (application/merge-patch+json). Core and HR API (PATCH /services/api/x/chr-jobmgmt-app/v1/job-functions/{jobFunctionId}). The id is the job function id. OAuth scope: function:update. Required: id.
- **Cornerstone OnDemand job functions list children** (List). List a job function's children. Use this endpoint to fetch the job functions whose current parent is the supplied one. Core and HR API (GET /services/api/x/chr-jobmgmt-app/v1/job-functions/{jobFunctionId}/children). OAuth scope: function:read. Required: job_function_id.
- **List all Cornerstone OnDemand job function parents** (List). List a job function's parent assignments. Use this endpoint to read a job function's parent timeline, which records where it has sat in the hierarchy over time. Core and HR API (GET /services/api/x/chr-jobmgmt-app/v1/job-functions/{jobFunctionId}/parents). OAuth scope: function:read. Required: job_function_id.
- **Create a Cornerstone OnDemand job function parent** (Create). Add a parent assignment to a job function. Core and HR API (POST /services/api/x/chr-jobmgmt-app/v1/job-functions/{jobFunctionId}/parents). OAuth scope: function:create. Required: job_function_id, dateEffective, parentJobFunctionId.
- **Delete a Cornerstone OnDemand job function parent by ID** (Delete). Remove a job function's parent assignment. Core and HR API (DELETE /services/api/x/chr-jobmgmt-app/v1/job-functions/{jobFunctionId}/parents/{assignmentId}). The id is the assignment id. OAuth scope: function:delete. Required: id, job_function_id.
- **Update a Cornerstone OnDemand job function parent by ID** (Update). Update a job function's parent assignment. Core and HR API (PATCH /services/api/x/chr-jobmgmt-app/v1/job-functions/{jobFunctionId}/parents/{assignmentId}). The id is the assignment id. OAuth scope: function:update. Required: id, job_function_id.
- **List all Cornerstone OnDemand job function statuses** (List). List a job function's status assignments. Use this endpoint to read a job function's status timeline, which records when it has been active and when inactive. Core and HR API (GET /services/api/x/chr-jobmgmt-app/v1/job-functions/{jobFunctionId}/statuses). OAuth scope: function:read. Required: job_function_id.
- **Create a Cornerstone OnDemand job function status** (Create). Add a status assignment to a job function. Core and HR API (POST /services/api/x/chr-jobmgmt-app/v1/job-functions/{jobFunctionId}/statuses). OAuth scope: function:create. Required: job_function_id, active, dateEffective.
- **Delete a Cornerstone OnDemand job function status by ID** (Delete). Remove a job function's status assignment. Core and HR API (DELETE /services/api/x/chr-jobmgmt-app/v1/job-functions/{jobFunctionId}/statuses/{assignmentId}). The id is the assignment id. OAuth scope: function:delete. Required: id, job_function_id.
- **Update a Cornerstone OnDemand job function status by ID** (Update). Update a job function's status assignment. Core and HR API (PATCH /services/api/x/chr-jobmgmt-app/v1/job-functions/{jobFunctionId}/statuses/{assignmentId}). The id is the assignment id. OAuth scope: function:update. Required: id, job_function_id.
- **List all Cornerstone OnDemand job levels** (List). List job levels. Use this endpoint to fetch job levels in bulk. Every query parameter is optional; with none supplied the endpoint returns all job levels the caller may see, a page at a time, under the standard {results, paging} envelope. Core and HR API (GET /services/api/x/chr-jobmgmt-app/v1/job-levels). OAuth scope: level:read.
- **Create a Cornerstone OnDemand job level** (Create). Create a job level. Use this endpoint to add a job level to the Structure taxonomy. Core and HR API (POST /services/api/x/chr-jobmgmt-app/v1/job-levels). OAuth scope: level:create. Required: active, dateEffective, defaultCultureCode, globalCode, titles.
- **Delete a Cornerstone OnDemand job level by ID** (Delete). Archive a job level. Use this endpoint to archive a job level. Core and HR API (DELETE /services/api/x/chr-jobmgmt-app/v1/job-levels/{jobLevelId}). The id is the job level id. OAuth scope: level:delete. Required: id.
- ...and 359 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
