If you've ever waited three days for a headcount report, exported a CSV at 9pm to answer one question, or asked engineering to build you "just a small dashboard," this post is for you.
The off-the-shelf tools sold to People teams, finance leaders, and managers of all kinds weren’t built for the way any specific company actually works. Every team's questions are different. Every workflow is different. So you either compromise on what you're trying to do, or you wait weeks for engineering to build something custom. Most of the time, the moment you needed the answer has already passed.
We are opening Remote's global infrastructure so that any company, tool, or AI agent can build on it. Our public API and SDK were already in place, with a CLI coming soon.
Remote MCP, the focus of this post, is the latest piece. It's our connection between Remote and any MCP-compatible AI tool. Sign in once through your browser, and your agent (Claude, ChatGPT — whatever is your AI of choice) has live, secure access to the workforce data you've already trusted us with. No API keys to generate, no exports, no custom integrations to maintain.
The nine examples below are real MCP workflows our own executives ran this week. Every one of them is a question someone on this team has had to answer manually before. Here's what those workflows look like now.
1. Flag comp gaps below the country midpoint
Barbara Matthews, Chief People Officer
Every People leader has wanted the kind of view that catches the people quietly at risk: long tenure, no recent adjustment, and sitting under the country midpoint for their role. It's the kind of high-value analysis that gets deprioritized when the People team is already stretched.
Barbara asked Remote MCP to run it (shown here on a demo org):
"Pull comp data for this department. Flag anyone without a salary adjustment in 18+ months. Surface where they're sitting below the country midpoint for the role."
The result: 15 employees, with 5 flagged as urgent on both counts, a few more flagged on salary alone, and 6 fully clear. A full afternoon of work, returned as a clean chart before the next meeting.
2. Pull a board-ready headcount report
Michiel Boere, Chief Financial Officer
Headcount reports are deceptively hard. By department, by location, by employment type, against plan, against last quarter, against budget. The shape of the report changes every time someone asks for it, and assembling it usually means a finance analyst rebuilding a spreadsheet from scratch.
Michiel asked Remote MCP to assemble one (shown here on a demo org):
"Pull a headcount report broken down by department, location, and employment type. Compare against plan and against last quarter."
The result: the full report, formatted with the comparisons already done. A finance project that used to take half a day, ready to share before the meeting.
3. Track probation periods across countries
Marcelo Lebre, Co-founder and President
Probation periods are the kind of thing that quietly slip when they live in a spreadsheet. Every country has different rules. Every employee has a different start date. Missing a probation deadline can mean missing the window to act.
Marcelo asked Remote MCP to surface the picture across countries (shown here on a demo org):
"Show all employees in probation across countries. Flag anyone ending in the next 30 days. Highlight where action is needed."
The result: 9 employees ending probation in the next 30 days, 4 needing action, and 1 termination flagged, returned employee-by-employee with a checklist for each.
4. Model a structural workforce change
Job van der Voort, CEO
Some of the hardest questions a leadership team faces involve modelling a change before deciding whether to make it. What if we restructured part of the team across more time zones? What would it cost? Where could we onboard fastest? What would compliance look like? Each of those questions used to live in a different system, owned by a different team.
As a thought exercise, Job asked Remote MCP to model a hypothetical scenario — a follow-the-sun support model with a portion of hiring shifted geographically (shown here on sandbox data):
"Show our current support team costs by geography. Project savings if we shift 40% of hiring to a different region. Estimate payroll overhead impact. Identify the countries where we can onboard fastest. Draft a hiring plan for moving support to a follow-the-sun model."
The result, in seconds: recommendations, projections, and visualizations covering all four questions at once — the kind of cross-functional modelling that used to require finance, legal, HR, and operations working in parallel.
5. Break down total employment cost by country
Michelle Adams, Chief Business Officer
Total cost of employment by country is one of the most common questions a CBO or CFO gets, and one of the hardest to answer cleanly. Salary, employer taxes, Remote fees, FX — it all has to roll up by country, and historically that's a finance project that takes days for a number that's already slightly stale by the time it lands.
Michelle asked Remote MCP to do it (shown here on a demo org):
"Break down total employment cost by country: salary, employer taxes, Remote fees, everything."
The result: total annual spend, average cost per employee, the most and least expensive markets, and a per-country bar chart, all back before her next call started.
6. Reconcile budgeted headcount against actuals
Paula Dieli, VP of EOR Operations
Every FP&A or Ops leader has had this conversation: it's the day before the board meeting and you need a clean view of plan vs. actuals across the company. Headcount lives in one system, budget in another, departmental breakdowns in a third. Hours of formatting before the actual analysis starts.
Paula asked Remote MCP to do it (shown here on a demo org):
"Reconcile Q2 budgeted headcount against actuals. Show cost variance by department."
The result: 249 budgeted versus 252 actual, against a $10.3M budget, with a +$347K variance broken down by department and color-coded by status. One prompt, ready to walk into the meeting.
7. Run a cross-country compliance review
Sam Ross, Chief Legal Officer
Quarterly compliance review across multiple countries used to mean emails to local counsel across time zones and days of waiting. The contract clauses that matter in Germany aren't the ones that matter in France, and off-the-shelf compliance dashboards force you into their format.
Sam asked Remote MCP to review (shown here on a sample org across Germany and France):
"Run a compliance review across employees in Germany and France. Flag what needs attention."
The result: 9 items reviewed, with 1 expiring soon, 1 needing further review, and 7 fully clear — structured, scannable, and with suggested actions for each.
8. Give managers a real view of team PTO
For people managers
Managers don't usually have a clean view of their team's leave patterns. Some people are about to burn out without realizing it. Some have carry-over they're going to lose. The data exists, but assembling it into something useful means pulling from multiple places and formatting it yourself.
A manager asked Remote MCP to surface it:
"Give me a complete view of my team's PTO usage. Flag risk areas and suggested actions."
The result: 75 unused days across the team, 22% above target, with 4 out of 6 team members carrying more than 12 unused days at midyear. Carry-over rules broken down by country, with suggested actions for each.
9. Let employees plan their own time off, smarter
For employees
Not every Remote MCP example is about org-level workflows. Some are personal. One of the simplest demos we ran was an employee asking the agent to plan their PTO for the longest possible break.
The employee asked:
"Find the best way to combine public holidays and PTO for the longest possible break this year."
The result: the optimal days to take off, the ratio of days gained to PTO used, and a calendar view showing exactly when to book it.
What this actually changes
Remote has spent seven years building what no one else has: a single, in-house global payroll and employment infrastructure, with owned entities, our own payroll engines, and deep local expertise.
That infrastructure is now open. We're going all in on global payroll and employment, and we're opening that foundation so any company, tool, or AI agent can build on it — exactly the way that fits your team's specific work, not the way an off-the-shelf product decided for you.
Everything above the infrastructure (the dashboards, the workflows, the reports, the custom tools) can now be built by agents. Agents embedded in your apps, woven into your workflows, running autonomously on your schedule and with your permissions.
This is what we built Remote's infrastructure to enable, and we're just getting started.
