Namely MCP connector
Connecting Namely to Elaichi lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent look up and update employee profiles, teams, groups, folders and company events, with each person signed in as themselves and every call logged.
- OAuth or API key
- Free 14-day trial
- No credit card
List everyone on the Engineering team with their start dates
Working in Namely with Elaichi
-
List all Namely companies info
-
List all Namely profiles
-
Get single Namely profile by ID
How to connect Namely to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Namely 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.
Namely 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.
Namely 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.
Namely 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.
Namely 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 Namely 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 Namely through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Namely is logged.
-
HR
Find who sits on which team today
Ask for everyone on a team or in a group and get the current roster from Namely, with the profile details you need before a review or a reorg.
-
People Ops
Set up a new hire's profile
Create the Namely profile for a new starter from the offer details you already have, then confirm it looks right before their first day.
-
Managers
Catch a profile up after a change
After a promotion, a title change or a move to a new manager, update the person's Namely profile in one ask instead of clicking through the form.
-
IT
Pull a roster for an access review
List every active profile in Namely, grouped by team or department, so you can check it against the systems people still have access to.
-
Office
Put the all-hands on the company calendar
Create a Namely event for the all-hands, the holiday party or the fire drill, and pull up what is already scheduled before picking a date.
-
Internal comms
Keep the policy folder tidy
See which documents live in each Namely folder, add a folder for a new policy set, and remove resources that are out of date.
Try asking
- “List everyone on the Engineering team with their start dates”
- “Create a profile for Priya Shah starting Monday in Marketing”
- “Add a company event for the all-hands next Thursday at 10”
What connecting Namely gets you
6 screens from Elaichi, each doing one job for your Namely account.
Ask Elaichi to work across your apps.
List everyone on the Engineering team with their start dates
Create a profile for Priya Shah starting Monday in Marketing
Add a company event for the all-hands next Thursday at 10
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about any Namely profile in plain language.
Type a question, get an answer from live Namely profiles, teams and events.
Copy the endpoint
AI apps
Namely works in Claude, ChatGPT and Cursor.
One governed endpoint, signed in over OAuth, no SDK and no shared API key.
Tool catalog
54 Namely tools ready without writing code.
Profiles, groups, teams, folders, resources and events, covered with no custom code to maintain.
Toolboxes
Each team gets its own Namely toolbox.
HR, IT and managers each see the Namely tools scoped to their work.
Shared connections
Share a Namely connection, never a credential.
One person connects Namely, teammates work through it, and nobody else handles a key.
Audit log
Every Namely change is logged by name.
See who updated which profile, created which event, and when, in one append-only log.
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.
Namely digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch profiles
Namely
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
Namely
Queued
Workflows
A schedule drafts the Namely digest for you.
New profiles are fetched, grouped and drafted into a digest, approved, then posted to Namely.
Namely health
Refreshed 4 minutes ago · every 15 minutes · from the profiles collection
Profiles
1,284 ↓ 12%
Groups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Profiles created
Last 14 days
By team
Share of activity
HR US 34%
HR EMEA 27%
People Ops 21%
IT 18%
Collections and dashboards
Namely headcount numbers arrive without being asked.
Four metrics, profiles created over 14 days, a team breakdown, computed with no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Namely
All three can connect Namely 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 Namely tools | Allow or restrict single Namely 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 Namely 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.
Namely tools for your AI agents
54 tools are ready to call through Elaichi's MCP endpoint the moment you connect Namely, 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 Namely to Claude?
Connect Namely in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Namely asks for an OAuth application registered inside your own Namely account, so an admin brings a client ID and secret once, or you can connect with a Namely API key instead. After that, each person signs in to Namely as themselves and nobody else handles a credential.
Does Namely work with ChatGPT and Cursor as well as Claude?
Yes. Once Namely 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 Namely once and every client picks it up.
What can an AI agent actually do with my Namely data?
With Namely connected, an agent can look up an employee's profile, list who is on a team or in a group, create or update a profile, browse folders and the documents in them, and add or remove company events. Short, concrete asks such as "list everyone on the Support team" work better than long paragraphs.
Does connecting Namely give the AI access to everyone's records?
No. Every call to Namely runs as the person who signed in, so an agent sees only the profiles, groups, folders and events that person can already see in Namely. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Namely already allows.
Can I stop an agent from deleting or changing things in Namely?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting folders or events, or updating profiles, for a role or for one person while leaving lookups open. A restricted Namely 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 Namely connection when someone leaves?
Offboarding a person in Elaichi ends their access to Namely through every client at once. A Namely connection shared with a team keeps working for everyone else. If you want it gone entirely, disconnecting Namely once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Namely MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Namely 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 Namely?
Yes. Both let Claude, ChatGPT or Cursor use Namely. 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 Namely call.
How is Elaichi different from Composio for Namely?
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 Namely: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Namely 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