Degreed MCP connector
The Degreed connector brings learners, completions, skills, pathways, certificates and badges into Claude, ChatGPT, Cursor and Microsoft Copilot through one governed Elaichi endpoint, so each person asks questions inside their own Degreed access.
- App credentials
- Free 14-day trial
- No credit card
Which of my team's required learnings are still incomplete this quarter?
Working in Degreed with Elaichi
-
List all Degreed users
-
Get single Degreed user by ID
-
List all Degreed user todays learnings
How to connect Degreed to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Degreed MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Degreed MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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.
Degreed MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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.
Degreed MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Degreed MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Degreed to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Degreed through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Degreed is logged.
-
Learning and development
See who finished the required learning
Ask which people on a pathway still have required learnings open and who completed them this month. Chase the gaps before the deadline instead of exporting a report.
-
Managers
Prepare for a development conversation
Pull a team member's completions, skill ratings, badges and accomplishments into one view before a one to one. Walk in knowing what they have been learning.
-
HR
Keep learner records current after changes
When someone changes role or manager, update their Degreed user record and check their group memberships in one ask. New joiners can be created the same way.
-
Talent
Find people with a skill you need
Ask who has rated themselves on a skill and what their skill plans look like. Match internal opportunities to the people already building toward them.
-
Compliance
Check certificates before an audit
List the certificates held across a group and spot who is missing one. Answer an auditor's question with live Degreed records rather than a stale spreadsheet.
-
IT
Tidy up accounts during offboarding
Look up a leaver's Degreed user record and remove it as part of the checklist. Nobody has to sign into the admin area to do it.
Try asking
- “Which of my team's required learnings are still incomplete this quarter?”
- “Show skill ratings for everyone in the Sales Enablement group.”
- “Summarize this week's completions and badges across the engineering pathways.”
What connecting Degreed gets you
6 screens from Elaichi, each doing one job for your Degreed account.
Ask Elaichi to work across your apps.
Which of my team's required learnings are still incomplete this quarter?
Show skill ratings for everyone in the Sales Enablement group.
Summarize this week's completions and badges across the engineering pathways.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about learning progress in plain language.
Get answers about completions, skills and pathways from live Degreed records.
Copy the endpoint
AI apps
Use Degreed from any MCP client.
One governed endpoint for Claude, ChatGPT and Cursor, with no SDK or shared API key.
Tool catalog
283 Degreed tools, no code to write.
Users, completions, skills, pathways and badges, covered without an engineer building anything.
Toolboxes
Every team gets its own Degreed toolbox.
Scope what Learning, HR and managers can reach in Degreed, one toolbox per team.
Shared connections
Share a Degreed connection, never a credential.
One admin connects Degreed and teammates work through it without seeing the app credentials.
Audit log
Know who looked up which learner, when.
Every Degreed call lands in an append-only log with who, what and which resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Degreed digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Degreed
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Degreed
Queued
Workflows
A schedule starts the work, people approve it.
Completions are fetched, grouped, drafted into a digest, approved, then posted back to Degreed.
Degreed health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Completions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Learning 34%
HR 27%
Managers 21%
Talent 18%
Collections and dashboards
Degreed health numbers, refreshed without asking.
Four metrics, 14 days of new completions and a team breakdown, computed with no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Degreed
All three can connect Degreed 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Degreed tools | Allow or restrict single Degreed 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 Degreed 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Degreed tools for your AI agents
283 tools are ready to call through Elaichi's MCP endpoint the moment you connect Degreed, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Degreed to Claude?
Connect Degreed in Elaichi first by entering the app credentials your Degreed admin already holds, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and Degreed is ready to ask questions of.
Does Degreed work with ChatGPT and Cursor as well as Claude?
Yes. Once Degreed is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Degreed once and every client picks it up.
What can an AI agent actually do with my Degreed data?
It can look up learners and list their completions, required learnings, pathways, skill ratings, skill plans, certificates, badges, accomplishments, groups and opportunities. It can also create, update or remove a Degreed user record when your role allows it. Short concrete asks, such as who on the support team has not finished their required learning, work better than long paragraphs.
Does connecting Degreed give the AI everything in my organization's Degreed?
No. Every call runs inside the Degreed access of the person who signed in, so the agent sees the learners, groups and pathways that person is allowed to see. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Degreed already grants.
Can I stop an agent from deleting or changing things in Degreed?
Yes. Restrictions in Elaichi apply per action, for example removing a Degreed user or updating a learner record, and can be set 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 Degreed connection when someone leaves?
Offboarding that person in Elaichi ends their access to Degreed through every client at once. A Degreed connection they shared keeps working for everyone else on the team. If you ever want Degreed gone entirely, disconnecting it once in Elaichi removes it from every client.
Does the Degreed MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Degreed 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 Degreed?
Yes. Both let Claude, ChatGPT or Cursor use Degreed. 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 Degreed call.
How is Elaichi different from Composio for Degreed?
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 Degreed: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Degreed in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot