Culture Amp MCP. Manage employee data and track engagement surveys.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Culture Amp. Connect your AI agent to Culture Amp to manage employee records, track engagement surveys, and map organizational structure.
It lets you pull employee profiles, monitor survey participation rates, and list company groups using natural language queries. Ideal for HR Ops and People Analysts who need a single data point of truth for workforce health.
What your AI agents can do
Create employee record
Adds a new employee to the Culture Amp platform, resolving their ID and verification status.
Get employee details
Retrieves the full profile attributes for a specific employee.
Get survey details
Gets the configuration and status for a specific survey, including participant counts.
Get full details for a specific employee using their profile attributes.
Find employee records using a name or email keyword search.
Get a list of all employees, retrieving basic properties like ID, email, and status.
Check the configuration and status of any specific engagement survey.
List all groups and teams defined in the platform to understand the company layout.
List available demographic fields and analytics datasets to define reporting parameters.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Culture Amp MCP Server: 10 Tools for HR Data Management
Use these tools to manage employee records, track survey analytics, and map organizational structure through your AI agent.
019d757fcreate employee record
Adds a new employee to the Culture Amp platform, resolving their ID and verification status.
019d757fget employee details
Retrieves the full profile attributes for a specific employee.
019d757fget survey details
Gets the configuration and status for a specific survey, including participant counts.
019d757flist analytics datasets
Lists all available datasets you can use for reporting and analytics.
019d757flist cultureamp accounts
Lists all accounts associated with your organization's scope.
019d757flist demographic fields
Lists the demographic fields available to use when segmenting reports.
019d757flist employees
Provides a list of all employees, including their ID, email, and current status.
019d757flist engagement surveys
Lists all available engagement and experience surveys, noting their status (active/closed).
019d757flist organizational groups
Lists all teams and groups defined in Culture Amp, including their hierarchy.
019d757fsearch employees by name
Finds employee profiles by entering a name or email keyword.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Culture Amp, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Connect your AI agent to Culture Amp. You can pull employee profiles, track survey participation, and map out the company's structure with simple natural language queries. You'll get a single data source for workforce health, perfect for HR Ops and People Analysts.
To get employee details, you can use get_employee_details to pull the full profile attributes for any specific employee. If you just need to know who's on the payroll, list_employees gives you a list of everyone, pulling basic info like their ID, email, and status. Want to find someone by name or email? Use search_employees_by_name for that.
For managing employee records, you've got create_employee_record, which adds a new employee to the Culture Amp platform and resolves their ID and verification status.
When it comes to surveys, list_engagement_surveys shows you all the available engagement and experience surveys, noting if they're active or closed. You can check the setup and status of any single survey using get_survey_details, which also reports participant counts.
Mapping the company structure is simple. list_organizational_groups lists every team and group defined in Culture Amp, showing the whole hierarchy. If you need to build reports or segments, list_analytics_datasets shows you all the available datasets for reporting, and list_demographic_fields lists the demographic fields you can use when segmenting reports.
How Culture Amp MCP Works
- 1 Connect the Culture Amp integration to your AI agent and authorize it using your Culture Amp API Key.
- 2 Prompt your agent with a request, like 'List all employees in the Marketing department,' specifying the goal.
- 3 The agent executes the necessary tools (e.g.,
list_employeesorsearch_employees_by_name) and returns the structured data for you to analyze.
The bottom line is that your AI agent runs the complex HR queries against Culture Amp's data sources, giving you structured answers instead of forcing you to navigate multiple web pages.
Who Is Culture Amp MCP For?
People Operations specialists and HR Analysts. This connection is for the Ops Engineer who is tired of manually cross-referencing data from separate systems—the employee directory, the survey tool, and the org chart. If your job requires knowing 'who knows what' about your workforce, this is for you.
Runs audits on employee records; monitors survey participation rates across departments.
Pulls data to segment reports, linking demographic fields to engagement scores for deep insights.
Retrieves specific data for their immediate teams to track engagement trends and identify local gaps.
What Changes When You Connect
- Get a full view of employee profiles using
get_employee_details. Instead of clicking through a dozen tabs to see a person’s history, your agent pulls all core attributes in one go. This is crucial for auditing. - Understand your team structure immediately. Use
list_organizational_groupsto get a definitive list of all defined teams and departments. You don't have to guess the company's layout. - Track survey health without manual reports.
list_engagement_surveystells you which surveys are running, if they're active, and how many people have responded. You get real-time status updates. - Segment your data accurately.
list_demographic_fieldsshows you exactly what data points (like department or tenure) you can use to slice up your reports, preventing inaccurate analysis. - Handle employee additions easily. Use
create_employee_recordto onboard a new employee directly through the agent, mutating the core employee directory state. - Quickly locate staff.
search_employees_by_namelets you bypass the main employee list and jump straight to a profile using just a name or email keyword.
Real-World Use Cases
Auditing a department's compliance status
The HR Ops Specialist needs to know if everyone in the Finance group has completed the mandatory compliance survey. They ask their agent to use list_employees combined with list_organizational_groups to scope the group, then use get_survey_details to check participation against the list. This confirms compliance status faster than any spreadsheet.
Investigating low engagement in a team
A Team Lead notices low scores in one group. They ask their agent to run list_organizational_groups to confirm the target group ID, then use list_engagement_surveys to get the right survey ID. Finally, they use get_employee_details for key members to see if there are underlying profile issues or gaps.
Onboarding a new hire and checking their role
A manager needs to add a new worker and confirm their place in the company. They use create_employee_record to add the worker, and then follow up with search_employees_by_name and get_employee_details to verify the profile was built correctly and assigned the right attributes.
Preparing for a Quarterly Business Review (QBR)
The People Analyst needs a full picture of workforce trends. They first call list_analytics_datasets to see what metrics are available, then use list_demographic_fields to define the segmentation criteria, allowing them to build a complex report structure that was previously impossible.
The Tradeoffs
Treating the API like a search engine
Trying to run a single query that magically pulls employee data, survey results, and group memberships all at once. This fails because the system requires specific tool calls for each data type.
→
First, use list_employees to get the primary list of IDs. Then, run targeted calls: use get_employee_details for individual profiles and list_organizational_groups to map the structure. Never assume one tool covers everything.
Forgetting the data dependencies
Attempting to check a survey's participation rate without first using list_engagement_surveys to confirm the survey ID and its active status. The call will fail or return junk data.
→
Always check the survey lifecycle first. Use list_engagement_surveys to get the correct ID, and then pass that ID to get_survey_details before asking for participation metrics.
Over-relying on manual data dumps
Manually exporting CSVs from the website to piece together a view of engagement and organizational roles. This is slow, error-prone, and doesn't update when the source changes.
→
Let your agent do the heavy lifting. Use list_employees for the list, and then use list_organizational_groups to map the relationships. The agent stitches the data together programmatically.
When It Fits, When It Doesn't
Use this server if your job requires connecting three distinct data points: People (employee profiles/IDs), Place (organizational groups/teams), and Performance (survey/engagement scores). It’s essential if you need to know, 'How does the engagement score of the Engineering team compare to the Sales team?'
Don't use this if you just need a single, isolated report (e.g., 'What is the total number of employees?'). For that, a simple counting tool suffices. If your need is only to check basic payroll data, look for a dedicated payroll API instead. This tool is for complex, relational HR analysis.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Culture Amp. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually auditing employee data takes hours of clicking through disconnected dashboards.
Right now, auditing a single department's status means logging into the directory, pulling a list of IDs. Then you switch to the survey platform to check who responded, and finally jump to the org chart to confirm group membership. It’s a three-system handoff, filled with copy-pasting and cross-referencing.
With this MCP server, you ask your agent to 'Audit the Engineering team's status.' The agent runs the necessary tools (`list_employees`, `list_organizational_groups`, etc.) and returns a unified data packet. You get the full picture, not just links to where the data lives.
Culture Amp MCP Server: Get a unified view of workforce health.
You no longer need to run separate queries for 'Who works here?' and 'How do they feel?' The agent combines the outputs of `list_employees` and `list_engagement_surveys` into one actionable result. The process is direct.
This changes the game from reactive reporting to proactive analysis. You move past just *seeing* data; you start *acting* on connected insights.
Common Questions About Culture Amp MCP
How do I use the `list_employees` tool with Culture Amp? +
The list_employees tool provides a basic list of all employees, giving you their ID, email, and status. This is the starting point for finding the basic roster of staff.
Can I check the status of an engagement survey using `get_survey_details`? +
Yes, get_survey_details gives you the configuration, status, and participant count for a specific survey. It tells you if the survey is active or closed.
What is the difference between `list_employees` and `search_employees_by_name`? +
Use list_employees to get a full list of everyone. Use search_employees_by_name when you know a name or email keyword and want to jump directly to a specific profile.
Do I need to use `list_organizational_groups` before I can list employees? +
No. You can use list_employees directly to get the roster. However, running list_organizational_groups first helps you define the boundaries and context for your employee queries.
How do I use `create_employee_record` if I only have a user ID? +
You pass the ID and necessary verification status parameters. This tool adds a new employee to the platform, resolving their unique ID and checking their current verification status.
What happens if I run `get_employee_details` for an employee who doesn't exist? +
The tool returns a specific error code and a clear message. This tells you exactly which employee profile couldn't be found, allowing you to correct your input.
Should I use `list_demographic_fields` before running analytics? +
Yes, it's best practice to run this first. It gives you a list of all available demographic fields and identifiers, ensuring your reporting segments use the correct names.
How can I find employees in a specific team using `search_employees_by_name`? +
You need to combine the search with the group name. Use the group name as a filter parameter alongside the name or email keyword to narrow down the results.
How do I get a Culture Amp API Key? +
Log in to Culture Amp as an administrator, navigate to Settings > Data Integrations, and you will find the API section to generate a new key.
Can I see individual survey responses? +
To protect employee anonymity, the API generally provides aggregated survey data and participation status, rather than individual identifiable responses.
Does the integration support demographic segmentation? +
Yes, you can use the list_demographic_fields tool to view how your data is segmented, allowing the agent to provide more targeted insights.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
OneSignal
Send push notifications, emails, and in-app messages to millions of users with segmentation and A/B testing built in.
EventMobi
Deliver immersive event experiences with virtual and hybrid event tools, networking features, and live engagement analytics.
Wrike
Manage tasks, projects, and folders on Wrike — the most versatile work management platform for teams.
You might also like
AQICN
Access real-time Air Quality Index (AQI) data, pollutant levels, and weather conditions from over 30,000 stations worldwide.
Enverus Energy Intelligence
Equip your AI agent to access global energy data, track drilling rigs, and monitor well production via the Enverus API.
BILL Spend & Expense
Manage corporate spend via BILL — list budgets, cards, and transactions directly from any AI agent.