Polymer MCP connector
The Polymer connector brings your jobs, candidates, applications, hiring stages and review notes into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so recruiters can ask about a pipeline, move applications forward and leave comments while every action is logged under their own name.
- Connects with an API key
- Free 14-day trial
- No credit card
Show open Polymer jobs and their hiring stages.
Working in Polymer with Elaichi
-
List all Polymer public jobs
-
Get single Polymer public job by ID
-
List all Polymer organization
How to connect Polymer to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Polymer 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.
Polymer 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.
Polymer 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.
Polymer 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.
Polymer 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 Polymer 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 Polymer through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Polymer is logged.
-
Recruiting
Catch up on a pipeline before standup
Ask which applications are sitting in each hiring stage for an open role, who applied this week, and which candidates have been waiting longest without a comment.
-
Hiring managers
Review a shortlist and leave feedback
Pull up a candidate, read the application and the reviews already on it, then add a comment with your take so the recruiter sees it in Polymer.
-
Recruiting
Move applications after an interview loop
Once the panel has decided, move each application to the next stage or archive the ones that are out, and note the reason in a comment in the same breath.
-
People ops
Export resumes for a debrief
Ask for a resume export for a job and hand the file to interviewers before the debrief, without opening each application one by one.
-
Leadership
See what is open and who owns it
Get a plain list of open jobs across the organization, how many applications each has, and which Polymer users are on the team versus deactivated.
-
Operations
Add referrals and walk-ins to the right job
When a referral arrives by email, create the application against the correct job in Polymer so it enters the same pipeline as everyone else.
Try asking
- “Show open Polymer jobs and their hiring stages.”
- “How many candidates applied to the Senior Engineer job?”
- “List Polymer job applications received in the last week.”
What connecting Polymer gets you
6 screens from Elaichi, each doing one job for your Polymer account.
Ask Elaichi to work across your apps.
Show open Polymer jobs and their hiring stages.
How many candidates applied to the Senior Engineer job?
List Polymer job applications received in the last week.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about candidates, get answers back.
Plain language questions answered from live Polymer jobs, candidates and applications.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot read Polymer.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
29 Polymer tools ready without custom code.
Jobs, hiring stages, candidates, applications and organization users, every method cataloged.
Toolboxes
Every team gets its own Polymer toolbox.
Recruiting, hiring managers and people ops each work from a scoped toolbox.
Shared connections
Share Polymer access, never the credential.
See who connected each account and how many teams and members use it.
Audit log
Every Polymer call is on the record.
When, who, what happened, type and resource, in an 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. Automations, collections and live dashboards come with the Black plan.
Polymer digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch jobs
Polymer
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
Polymer
Queued
Automations
A schedule fires, a digest gets approved.
Polymer applications are fetched, grouped, drafted by an agent, approved, then posted back.
Polymer health
Refreshed 4 minutes ago · every 15 minutes · from the jobs collection
Jobs
1,284 ↓ 12%
Candidates
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Jobs created
Last 14 days
By team
Share of activity
Recruiting EMEA 34%
Engineering hiring 27%
People ops 21%
Campus hiring 18%
Collections and dashboards
Hiring numbers arrive before anyone asks.
Four metrics, 14 days of records created and a team breakdown, computed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Polymer
All three can connect Polymer 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 Polymer tools | Allow or restrict single Polymer 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 Polymer 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.
Polymer tools for your AI agents
29 tools are ready to call through Elaichi's MCP endpoint the moment you connect Polymer, 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 Polymer to Claude?
First, add Polymer in Elaichi and paste in a Polymer API key when asked, there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Claude can start reading your Polymer jobs and applications.
Does Polymer work with ChatGPT and Cursor as well as Claude?
Yes. Once Polymer 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 Polymer once and every client you use picks it up.
What can an AI agent actually do with my Polymer data?
An agent connected to Polymer can list your open and public jobs, look up candidates and their applications, read the hiring stages for a role and the reviews and comments on each application. It can also create an application, move an application to another stage, archive it, add or edit a comment, and request a resume export for a job. It cannot create or edit jobs or change your Polymer users.
Does connecting Polymer give the AI access to every job and candidate?
No. Every request to Polymer runs as the person who signed in, so the agent sees the jobs, candidates and applications that person's Polymer access already allows. Elaichi can narrow that further with restrictions, and it can never widen what someone has in Polymer.
Can I stop an agent from deleting or changing things in Polymer?
Yes. In Elaichi you can restrict individual actions on the Polymer connector, for example archiving applications, moving stages or deleting comments, while leaving reading in place. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a Polymer connection when someone leaves?
When you offboard a person in Elaichi, their access to Polymer through every client ends at once. A shared Polymer connection keeps working for everyone else on the team. If you disconnect Polymer in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.
Does the Polymer MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Polymer 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 Polymer?
Yes. Both let Claude, ChatGPT or Cursor use Polymer. 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 Polymer call.
How is Elaichi different from Composio for Polymer?
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 Polymer: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Polymer 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