How Wix scaled AI-native work to 5,000 employees with Willow
Read More
Enterprise Connectors
Culture Amp logo. Culture Amp MCP server connector.

Culture Amp MCP Server

Culture Amp is an employee experience platform for engagement surveys, performance reviews, and people analytics. This connector exposes read-only access to employees, demographics, performance cycles, and manager reviews.

ToolsTools
9
Last updatedLast Updated
✓Enterprise-grade security
✓SSO & authentication ready
✓Full governance & audit logs

What is the Culture Amp MCP Server?

The Culture Amp MCP server gives AI agents structured, permission-aware access to Culture Amp through the Model Context Protocol. With 9 pre-built actions, agents can read, create, and update Culture Amp data on behalf of authorized users.

Willow ships the Culture Amp MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Culture Amp is being used by every AI agent in your stack.

Tools

List Employees

List all employees in the Culture Amp account. Optionally filter to a single employee by `email` or `employee_identifier` (the org's own ID; takes precedence over email). Use `cursor` to walk through pages from a previous response's `pagination.afterKey`.

Get Employee

Retrieve a single employee by their Culture Amp identifier (UUID). Returns core profile fields, dates, and links to related demographics and manager-review collections.

List Employee Demographics

List demographic name/value assignments for a specific employee (e.g. department, location, role level). Useful for slicing performance or engagement data by attributes that aren't on the employee record itself.

List Performance Cycles

List performance cycles in the account. Use `state` to limit to `active`, `closed`, or `ready` cycles, `after_date` (RFC 3339, e.g. `2024-01-01T00:00:00Z`) to fetch only cycles processed after a date, and `cursor` for pagination.

Get Performance Cycle

Retrieve a single performance cycle by its Culture Amp ID. Returns the cycle name, state, and processing timestamps.

List Manager Reviews

List all manager reviews in the account, across cycles and employees. Use `after_date` (RFC 3339) to incrementally sync changes and `cursor` for pagination. Reviews with `dirty` status are excluded by the API.

Get Manager Review

Retrieve the full details of a manager review by ID, including the rating, open-text answers, multiple-choice answers, and acknowledgement status.

List Manager Reviews by Employee

List manager reviews for a specific employee across all performance cycles. Use this when you already know the employee's Culture Amp ID and want their review history.

List Manager Reviews by Performance Cycle

List all manager reviews that belong to a specific performance cycle. Useful for cycle-level reporting (completion rates, rating distributions) once you have the cycle ID from List Performance Cycles.

Customize tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

ReviewEdit descriptions
ConfigureChange arguments
ApproveSelect tools
Create NewAdd tool

Set Up Your Culture Amp MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "willow-cultureamp": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/cultureamp"
    }
  }
}

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "willow-cultureamp": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/cultureamp"
    }
  }
}

Claude Code

CLI
claude mcp add willow-cultureamp --transport http https://<org>.mcp-s.com/mcp/mcp/cultureamp

n8n

HTTP Request Node
{
  "url": "https://<org>.mcp-s.com/mcp/mcp/cultureamp",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Culture Amp

Willow adds the layer Culture Amp and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Culture Amp MCP Server FAQ

What is the Culture Amp MCP server?

The Culture Amp MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Culture Amp data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Culture Amp MCP server different from the official one?

The official Culture Amp MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Culture Amp MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Culture Amp MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Culture Amp, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Culture Amp actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Culture Amp MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Culture Amp MCP locally, you'll see it.

What does the Culture Amp MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Culture Amp MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.

Compare Willow MCP Gateway

See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.

Your agents are already in the wild.

Give them a Basecamp. Go from AI chaos to AI work, in minutes.