Skip to content

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.

  • App credentials
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Summarize the latest engagement survey responses by department.

Working in Culture Amp with Elaichi

  • List all Culture Amp employees
  • Get single Culture Amp employee by ID
  • List all Culture Amp employee demographics
Ask anything…
Governance / Audit log Last 24 hours
Culture Amp List all Culture Amp employee demographics Emily Carter · ChatGPT · 9:41 AM Done
Culture Amp Get single Culture Amp employee by ID Emily Carter · ChatGPT · 9:41 AM Done
Culture Amp List all Culture Amp employees Emily Carter · ChatGPT · 9:41 AM Done
Culture Amp List all Culture Amp employee manager reviews Megan Brooks · Claude · 9:38 AM Done
Culture Amp List all Culture Amp performance cycles Ryan Hayes · Cursor · 9:35 AM Done

How to connect Culture Amp to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Culture Amp MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

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

Culture Amp MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

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

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Culture Amp MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 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 Culture Amp to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Culture Amp through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Culture Amp is logged.

  • People

    Read the engagement survey before the all-hands

    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.

  • People analytics

    Compare factor scores across departments

    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.

  • Managers

    Check which manager reviews are still open

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

  • Leadership

    Get a plain summary of a pulse survey

    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.

  • Inclusion

    See how responses split by demographic group

    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.

  • Internal communications

    Turn survey sections into a results brief

    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.

Try asking

  • “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.”

See all 19 Culture Amp tools →

What connecting Culture Amp gets you

6 screens from Elaichi, each doing one job for your Culture Amp account.

Elaichi Agent

Ask Elaichi to work across your apps.

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.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about engagement, get answers from live surveys.

Three prompts to start, each pulling Culture Amp survey responses and factors as they stand today.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Culture Amp in every client, one endpoint.

Claude, ChatGPT and Cursor reach Culture Amp through https://api.elaichi.ai/mcp with no SDK and no shared key.

ElaichiTools
Tool Action Description
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.

Tool catalog

19 Culture Amp tools, no code to write.

Employees, demographics, surveys, responses, factors, performance cycles and manager reviews, ready the moment you connect.

ElaichiToolboxes
Name Source template Tools Created

People toolbox

Culture Amp · surveys and employees

Culture Amp starter 18 Mar 4, 2026

People analytics toolbox

Culture Amp · responses and factors

— 9 Mar 2, 2026

Managers toolbox

Culture Amp · performance cycles and reviews

— 24 Feb 27, 2026

Leadership toolbox

Culture Amp · survey summaries

Culture Amp starter 6 Feb 19, 2026

Inclusion toolbox

Culture Amp · demographics and responses

— 31 Jan 30, 2026

Internal communications toolbox

Culture Amp · survey sections and questions

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Culture Amp toolbox.

People analytics sees responses and demographics, managers see their cycle reviews, each scoped by role.

ElaichiConnections
Connection Scope Status Access
CU

Culture Amp (People team)

Connected by Emily Carter

Personal • Active 1 team · 6 members
CU

Culture Amp (Analytics)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
CU

Culture Amp (Managers)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
CU

Culture Amp (Leadership)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
CU

Culture Amp (Inclusion)

Connected by Ryan Hayes

Personal • Active Not shared
CU

Culture Amp (Internal comms)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share one Culture Amp connection, keep the credential.

One person connects Culture Amp, shares it with teams, nobody else ever sees the credentials.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Culture Amp Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Culture Amp Employees Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Culture Amp Employees List Toolbox

Audit log

Know who read which survey response, and when.

Every Culture Amp call is logged with the person, the action, the type and the 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.

Culture Amp digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch employees

    Culture Amp

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Culture Amp

    Queued

Workflows

The schedule drafts the survey digest, not you.

Responses are fetched, grouped by factor, drafted into a digest, approved by a person, then posted.

Culture Amp health

Refreshed 4 minutes ago · every 15 minutes · from the employees collection

Live

Employees

1,284 ↓ 12%

Surveys

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Employees created

Last 14 days

By team

Share of activity

People team 34%

Analytics 27%

Managers 21%

Leadership 18%

Collections and dashboards

Culture Amp health numbers, computed without a model.

Four metrics, fourteen days of survey responses, a breakdown by team, refreshed on a schedule.

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Culture Amp, by what to check
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 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Culture Amp tools for your AI agents

19 tools are ready to call through Elaichi's MCP endpoint the moment you connect Culture Amp, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

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.

Put Culture Amp 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