# Polymer MCP connector

The Polymer connector brings your jobs, candidates, applications, hiring stages and review notes into Claude, ChatGPT, Cursor 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.

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

## Facts

| | |
| --- | --- |
| Application | Polymer |
| Category | ATS |
| AI tools | 29 |
| Authentication | Connects with an API key |
| Needs your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | Yes |

## What you can ask once Polymer is connected

- 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.

## Connect Polymer in Elaichi

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

1. Open Connections, choose Add connection, and pick Polymer.
2. Optionally set Share with, then press Connect.
3. Paste a Polymer API key. One person generates a token in Polymer and pastes it once. Everyone else works through Share with, and never sees it.

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

## Connect Polymer to 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.

## Connect Polymer to 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 today. The plugin directory lives at chatgpt.com/plugins.

## Connect Polymer to 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.

## Connect Polymer 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

Only Read is granted by default, which is not enough to call a Polymer tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Polymer through Elaichi

### Catch up on a pipeline before standup

Recruiting. 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.

### Review a shortlist and leave feedback

Hiring managers. 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.

### Move applications after an interview loop

Recruiting. 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.

### Export resumes for a debrief

People ops. Ask for a resume export for a job and hand the file to interviewers before the debrief, without opening each application one by one.

### See what is open and who owns it

Leadership. 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.

### Add referrals and walk-ins to the right job

Operations. When a referral arrives by email, create the application against the correct job in Polymer so it enters the same pipeline as everyone else.

## Frequently asked questions

### 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, 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 my team share one Polymer connection?

Yes. One person connects Polymer with an API key and shares the connection with a team in Elaichi, and nobody else on the team ever sees or handles that key. Each recruiter or hiring manager still signs in as themselves, so the audit log names who moved an application or left a comment.

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

Yes. In Elaichi you can block individual actions on the Polymer connector, for example archiving applications, moving stages or deleting comments, while leaving reading in place. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.

### 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 and every other client in one step.

## All 29 Polymer tools

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

- **List all Polymer public jobs** (List). List public jobs for a polymer organization. Returns a collection of job items.
- **Get single Polymer public job by ID** (Get). Get a single public job by id from a polymer organization. Required: id.
- **List all Polymer organization** (List). Get the organization details in Polymer. Returns the organization object for the authenticated account.
- **List all Polymer organization users** (List). List active organization users in Polymer. Returns a collection of active user records from the organization.
- **Get single Polymer organization user by ID** (Get). Get a single organization user in Polymer by id. Required: id.
- **List all Polymer deactivated organization users** (List). List deactivated organization users in Polymer. Returns a collection of deactivated user records from the organization.
- **List all Polymer jobs** (List). List jobs in Polymer. Returns a collection of job objects from the items array.
- **Get single Polymer job by ID** (Get). Get a single job in Polymer by id. Returns the full job object. Required: id.
- **List all Polymer job hiring stages** (List). List hiring stages for a specific job in Polymer. Returns the hiring stages associated with the given job. Required: job_id.
- **Get single Polymer job resume export by ID** (Get). Get the resume export job associated with a specific job in polymer. Returns the resume export job record for the given job. Required: job_id.
- **Create a Polymer job resume export** (Create). Create a resume export job for a specific job in polymer. Returns the newly created resume export job record. Required: job_id.
- **List all Polymer candidates** (List). List candidates in Polymer. Returns a collection of candidate records.
- **Get single Polymer candidate by ID** (Get). Get a single candidate in Polymer by id. Returns the full candidate record. Required: id.
- **List all Polymer job applications** (List). List job applications in polymer. Returns a collection of job application records.
- **Get single Polymer job application by ID** (Get). Get a single job application by id in polymer. Returns the full job application object. Required: id.
- **Create a Polymer job application** (Create). Import a job application into polymer via the import endpoint. Returns the created job application record.
- **Create a Polymer job application apply** (Create). Submit a job application in Polymer via the apply endpoint. Returns the created application object.
- **Create a Polymer job application stage move** (Create). Move a job application to a new stage in polymer. Required: job_application_id.
- **Create a Polymer job application archive** (Create). Archive a job application in polymer. Required: job_application_id.
- **List all Polymer job application comments** (List). List all comments on a polymer job application. Returns a collection of comment objects associated with the specified application. Required: job_application_id.
- **Create a Polymer job application comment** (Create). Create a new comment on a polymer job application. Returns the created comment object. Required: job_application_id.
- **Update a Polymer job application comment by ID** (Update). Update an existing comment on a polymer job application by id. Returns the updated comment object. Required: job_application_id, id.
- **Delete a Polymer job application comment by ID** (Delete). Delete a comment from a polymer job application by id. Returns an empty response on success. Required: job_application_id, id.
- **List all Polymer job application reviews** (List). List all reviews for a polymer job application. Returns the collection of review records associated with the specified application. Required: job_application_id.
- **Create a Polymer job application review** (Create). Create a new review for a polymer job application. Returns the created review record. Required: job_application_id.
- **Update a Polymer job application review by ID** (Update). Update an existing review for a polymer job application. Returns the updated review record. Required: job_application_id and id.
- **Delete a Polymer job application review by ID** (Delete). Delete a review from a polymer job application by id. Returns an empty response on success. Required: job_application_id and id.
- **List all Polymer job application hiring stage events** (List). List hiring stage events for a specific job application in Polymer. Required: job_application_id.
- **List all Polymer job application messages** (List). List messages associated with a specific job application in Polymer. Required: job_application_id.