# Culture Amp MCP connector

The Culture Amp connector brings your surveys, responses, employee records, performance cycles and manager reviews to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so anyone can ask about engagement results inside their own Culture Amp access.

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

## Facts

| | |
| --- | --- |
| Application | Culture Amp |
| Category | Survey |
| AI tools | 19 |
| 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 Culture Amp is connected

- Summarize the latest engagement survey responses by department.
- Which survey factors scored lowest in the last pulse survey?
- List manager reviews still outstanding in the current performance cycle.

## Connect Culture Amp in Elaichi

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

1. Open Connections, choose Add connection, and pick Culture Amp.
2. Optionally set Share with, then press Connect.
3. Paste your Culture Amp app credentials. Culture Amp 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 Culture Amp tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Culture Amp 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.

## Culture Amp 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`.

## Culture Amp 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.

## Culture Amp 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.

## Culture Amp 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 Culture Amp 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 Culture Amp 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 Culture Amp through Elaichi

### Read the engagement survey before the all-hands

People. Ask for the headline results of the latest Culture Amp engagement survey, section by section, and have the talking points ready before leadership walks into the room.

### Compare factor scores across departments

People analytics. Pull survey factors and responses from Culture Amp and line up how engineering, sales and support scored on the same factor, without exporting a spreadsheet first.

### Check which manager reviews are still open

Managers. Ask which manager reviews in the current Culture Amp performance cycle have been completed and which are still outstanding, then chase the right people.

### Get a plain summary of a pulse survey

Leadership. Get a short, plain-language summary of a Culture Amp pulse survey, with the questions that moved most since the last one, in time for the exec meeting.

### See how responses split by demographic group

Inclusion. Look at Culture Amp survey responses alongside employee demographics to see where experience differs by tenure, location or level, and where to focus the next listening session.

### Turn survey sections into a results brief

Internal communications. Pull the questions, sections and factor scores from a closed Culture Amp survey and draft the results update that goes out to the whole company.

## Elaichi vs Zapier MCP vs Composio for Culture Amp

All three can connect Culture Amp 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 Culture Amp tools | Allow or restrict single Culture Amp 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 Culture Amp 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 Culture Amp to Claude?

Connect Culture Amp in Elaichi first, then paste https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. Culture Amp's own step is entering the app credentials your Culture Amp account issues, and that is the whole sign-in. There is no OAuth application to register and no client ID or secret to generate. The endpoint is the same address for every customer.

### Does Culture Amp work with ChatGPT and Cursor as well as Claude?

Yes. Once Culture Amp 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 Culture Amp once and every client picks it up.

### What can an AI agent actually do with my Culture Amp data?

It can read your Culture Amp employees and their demographics, your surveys with their questions, sections, factors and responses, and your performance cycles and manager reviews. That means you can ask things like which factor scored lowest in the last engagement survey, how a department compares to the company, or which manager reviews are still open this cycle. Short, concrete asks work better than long sentences.

### Does connecting Culture Amp let the AI see every survey response and demographic?

No. Every call to Culture Amp runs inside the access of the person who signed in, so an agent sees only the surveys, responses and employee records that person can already see in Culture Amp. Elaichi can narrow that further with roles and restrictions, and it never widens it.

### Can my team share one Culture Amp connection?

Yes. One person connects Culture Amp in Elaichi and shares the connection with a team, and nobody else ever handles the Culture Amp app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Culture Amp call.

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

The Culture Amp connector reads employees, surveys, responses, performance cycles and manager reviews; it does not change or delete anything in Culture Amp. If you want to narrow reading further, restrictions apply per action, on a role or on one person, for example restricting access to demographics or individual survey responses. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Culture Amp connection when someone leaves?

Offboarding a person in Elaichi ends their access to Culture Amp through every client at once. A Culture Amp connection they shared keeps working for everyone else on the team. If you ever want to remove Culture Amp altogether, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

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

Yes. Culture Amp 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 Culture Amp?

Yes. Both let Claude, ChatGPT or Cursor use Culture Amp. 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 Culture Amp call.

### How is Elaichi different from Composio for Culture Amp?

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 Culture Amp: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 19 Culture Amp tools

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

- **List all Culture Amp employees** (List). List all employees in the Culture Amp account. Returns: id, employeeIdentifier, email, name, preferredName, birthDate, startDate, endDate, links, processedAt. When both email and employee_identifier query filters are provided, employee_identifier takes precedence.
- **Get single Culture Amp employee by ID** (Get). Get a single Culture Amp employee by id. Returns: id, employeeIdentifier, email, name, preferredName, birthDate, startDate, endDate, links, processedAt. Required: id.
- **List all Culture Amp employee demographics** (List). List the demographic assignments for a Culture Amp employee. Returns: name, value. Required: employee_id.
- **List all Culture Amp employee manager reviews** (List). List manager reviews for a given employee in Culture Amp. Returns: performanceCycleId, managerReviewId, employeeId, managerId, performanceRating, openTextQuestions, multipleChoiceQuestions, multipleChoiceMultiSelectQuestions, reviewAcknowledged, status, links, completedAt, createdAt, updatedAt, processedAt. Required: employee_id.
- **List all Culture Amp performance cycles** (List). List Culture Amp performance cycles in the account. Returns: id, name, state, createdAt, updatedAt, processedAt.
- **Get single Culture Amp performance cycle by ID** (Get). Get a Culture Amp performance cycle by id. Returns: id, name, state, createdAt, updatedAt, processedAt. Required: id.
- **List all Culture Amp performance cycle manager reviews** (List). List CultureAmp manager reviews for a given performance cycle. Returns: performanceCycleId, managerReviewId, employeeId, managerId, performanceRating, openTextQuestions, multipleChoiceQuestions, multipleChoiceMultiSelectQuestions, reviewAcknowledged, status, links, completedAt, createdAt, updatedAt, processedAt. Required: performance_cycle_id.
- **List all Culture Amp manager reviews** (List). List all manager reviews in the CultureAmp account. Returns: performanceCycleId, managerReviewId, employeeId, managerId, performanceRating, openTextQuestions, multipleChoiceQuestions, multipleChoiceMultiSelectQuestions, reviewAcknowledged, status, links, completedAt, createdAt, updatedAt, processedAt.
- **Get single Culture Amp manager review by ID** (Get). Get a single CultureAmp manager review by id. Returns the full review including employeeId, managerId, performanceCycleId, performanceRating, status, reviewAcknowledged, and its question responses. Required: id.
- **List all Culture Amp surveys** (List). List all surveys in the Culture Amp account. Returns: id, name, status, rdeEnabled, owner, workflow, launchedAt, closedAt, createdAt, updatedAt, processedAt, communicatedClosedAt, surveyDueDays, kioskModeEnabled, excludeParticipantsAfter. Deprecated — no longer available for new setup; use the Culture Amp Reporting API for RDE-enabled survey data.
- **Get single Culture Amp survey by ID** (Get). Get a single Culture Amp survey by id. Returns: id, name, status, rdeEnabled, owner, workflow, launchedAt, closedAt, createdAt, updatedAt, processedAt, communicatedClosedAt, surveyDueDays, kioskModeEnabled, excludeParticipantsAfter. Deprecated — no longer available for new setup; use the Culture Amp Reporting API instead. Required: id.
- **List all Culture Amp survey questions** (List). List all questions from a Culture Amp survey. Returns: id, code, questionType, label, description, ratingScale, selectOptions, otherOption, status, sectionId, factorIds, createdAt, updatedAt, processedAt. Deprecated — this API is no longer available for new setup; use the Culture Amp Reporting API instead. Required: survey_id.
- **Get single Culture Amp survey question by ID** (Get). Get the details of a single question from a Culture Amp survey. Returns: id, code, questionType, label, description, ratingScale, selectOptions, otherOption, status, sectionId, factorIds, createdAt, updatedAt, processedAt. Deprecated — this API is no longer available for new setup; use the Culture Amp Reporting API instead. Required: id, survey_id.
- **List all Culture Amp survey responses** (List). List all responses for an individual Culture Amp survey. Returns: id, employeeId, answers, rdeEnabled, captureLocale, surveySubmittedBy, startedAt, submittedAt, expiredAt, createdAt, updatedAt, processedAt. Deprecated — no longer available for new setup; use the Reporting API instead. Required: survey_id.
- **Get single Culture Amp survey response by ID** (Get). Get the details of a single response from a Culture Amp survey. Returns: id, employeeId, answers, rdeEnabled, captureLocale, surveySubmittedBy, startedAt, submittedAt, expiredAt, createdAt, updatedAt, processedAt. Deprecated — no longer available for new setup; use the Reporting API instead. Required: id, survey_id.
- **List all Culture Amp survey factors** (List). List all factors from a CultureAMP survey. Returns: id, name, type, code, indexFactor, customFactor, shortDescription, longDescription, status, order, createdAt, updatedAt. Deprecated: this API is no longer available for new setups; use the CultureAMP Reporting API instead. Required: survey_id.
- **Get single Culture Amp survey factor by ID** (Get). Get a single factor from a CultureAMP survey by id. Returns: id, name, type, code, indexFactor, customFactor, shortDescription, longDescription, status, order, createdAt, updatedAt. Deprecated: this API is no longer available for new setups; use the CultureAMP Reporting API instead. Required: id, survey_id.
- **List all Culture Amp survey sections** (List). List all sections of a Culture Amp survey. Returns: id, name, type, code, shortDescription, longDescription, status, order, createdAt, updatedAt. Deprecated: this API is no longer available for setup; use the Reporting API instead. Required: survey_id.
- **Get single Culture Amp survey section by ID** (Get). Get a single section of a Culture Amp survey by id. Returns: id, name, type, code, shortDescription, longDescription, status, order, createdAt, updatedAt. Deprecated: this API is no longer available for setup; use the Reporting API instead. Required: id, survey_id.
