Skip to main content
Integrations & API

AI chat (LLM) via MCP

Operating MCP server

Written By Matti Parviainen

Last updated About 9 hours ago

This video explains how to get started with MCP

Known supported LLM providers our customers have been happy with

Using ChatGPT or Codex? Use the official Operating app instead of a custom setup. Admins set it up once for the whole workspace with Set up the Operating app for ChatGPT and Codex. After that, everyone follows Use Operating in ChatGPT and Codex.

  1. Claude & Claude Code

  2. ChatGPT — use the official Operating app for ChatGPT

  3. Codex — use the same Operating app, or add the MCP server directly in the IDE extension (see Operating app for ChatGPT)

  4. Gemini CLI

    1. If the mcp add command does not work it is worth trying with gemini mcp add --scope user

  5. Sana

Microsoft Copilot, including Copilot Studio, and the Gemini app are not supported. Gemini CLI is supported. Contact support if you run into any setup issues. These are limitations in Microsoft and Google applications, not our MCP server.

What’s the power of a great LLM & your ops data

This is just a naive example – not something we necessarily recommend, but kind of cool chain of three prompts with Claude.

Use casual language, the model will figure it out:

Ask it to recommend things:

Create one-off artifacts or reusable agentic workflows based on Operating data:

Of course, for some things like this you might go for tools like Claude for Excel or ChatGPT for Excel instead of the chat interface. Operating MCP works there just as well.


MCP Server Capabilities Summary (updated August 10th 2026)

When a tool is deprecated, Operating shows a notice with its replacement on your personal MCP Setup page in Settings (the same notice also appears on the admin MCP Server settings page).

The Operating MCP server exposes 31 tools across these categories, including List Invoices and Get Invoice for billing documents:

Tenant selection

list_tenants — pick which tenant to work with before calling any other tool

Reference data (read-only)

list_reference_data — one tool for the lookups other tools need. Choose which groups to return and filter within each group. Use it to find the IDs that the manage tools and the filtered list tools expect.

The groups include roles, seniorities, skills, skill levels, skill sentiments, sites, groups, companies, statuses, client and project tags, task lists, rate cards, vendors and expense categories.

People (read + write)

list_people — search/filter people by site, role, group, availability. Each person includes their site history and their employment start and end dates

get_person — full detail on one person:

  • site history and company history
  • employment start and end dates
  • roles with their start and end dates
  • position history
  • time off
  • working hours

The person's company is the company that applies today.

get_person and manage_person also return the person's links to the same person in other systems, such as an HR system. Each link has the system's name, the person's ID in that system, a name and a web address. The list is empty when the person has no links, and list_people does not return it.

manage_person — create or update a person, including their roles, skills, groups, costs, site history and company history.

  • Site: give the person's starting site when you create them. After that, change their site by adding, moving or removing dated site assignments, for example "Anna moves to the Berlin site from 1 October". If sites are imported from your HR system (for example HiBob), a linked person's site history is managed there and can't be changed through manage_person.

  • Company: change a person's company by adding, moving or removing dated company assignments, for example "Anna moves to the Operating UK company from 1 October".

Use the assignment IDs that get_person returns.

Clients (read + write)

list_clients — list clients, with search, owner, tag, internal and archived filters. Use it to find client IDs before you create or filter projects

manage_client — create or update one client. A field that a connected system writes for the client, such as a VAT ID kept by an accounting system, can't be changed here; change it in that system

Projects (read + write)

list_projects — filter by client, owner, status, site, tags. Each project shows when it was archived, if it is archived

get_project — a single project with its details, plus the CRM deals linked to it (each with its stage, probability, value, and close date). Each position on the project lists its own Groups, and each task assignment shows when it was archived, if it is archived

get_project and manage_project also return the project's links to other systems. Each link has the system's name, the project's ID in that system, a name and a web address. The list is empty when the project has no links, and list_projects does not return it.

manage_project — create or update a project, or archive or unarchive it.

You can also add, update and remove project notes. To add a note, give the note text and the note date. To update or remove a note, use the note's ID, which get_project returns with the project's notes.

Archiving follows the same rules as in the app:

  • The time off project can't be archived.
  • All confirmed allocations must end today at the latest.
  • A project with an archived client can't be unarchived.

An archive request changes only the archived state, so send other project changes in a separate request. See How to archive and unarchive projects.

Invoices (read-only)

list_invoices — list invoices with filters and sorting.

  • Filters: project, client, company, status, type, date, due date, or sent/ready-to-send state.
  • Sorting: by invoice date, status, or amount, ascending or descending.
  • Paging: results page by cursor.

get_invoice — a single invoice with line items, per-project amounts, linked time entries, expenses, payment methods, and PDF link

Reports (read-only)

report_actual — actual work hours and earned revenue over a date range.

  • Grouping: by project or person.
  • Buckets: week, month, or total.
  • Options: breakdowns, non-person revenue, and opt-in costs.
  • Actuals end date: the result includes actualsThrough, the last date the actuals cover, in YYYY-MM-DD format. This date is today. Time entries, expenses and recognized revenue dated after today are not counted, even when the date range ends later.
  • Paging: results page with limit and meta.nextCursor.

report_planned — planned work, tentative work, revenue, and utilization over a date range.

  • Grouping: by project or person.
  • Buckets: week, month, or total.
  • Options: breakdowns and opt-in costs.
  • Paging: results page with limit and meta.nextCursor.

Positions (read + write)

list_positions — person-to-project assignments with filters, including a filter for the position's own Groups (separate from the project's Groups). Each position lists its Groups

get_position — a single position with all its allocations and its Groups

manage_positions — create, update, archive or restore positions

move_positions — move positions between projects

Allocations (read + write)

list_allocations — scheduled time blocks, filterable by person/project/date

manage_allocations — create, update, move or remove allocations, with a result for each one so that failed changes can be retried

move_allocations — move allocations between positions

Time tracking

list_time_entries — logged hours, filterable by project/person/date

track_time — log hours against a project

start_timer — start your timer on a project. When you stop the timer, it becomes a time entry

get_timer — read your running timer

stop_timer — stop your timer and create a time entry, or add the time to a matching time entry that is not submitted, approved or invoiced

submit_timesheet — submit a person's unsubmitted time entries up to and including a date

Budgets & phases (write)

manage_project_financial_plan — create, update or remove a project's budgets, budget schedules (how a retainer is set up), planned expenses and rate card assignments

A capped time-and-materials budget caps by amount or by hours, set in capBasis:

  • amount: the budget's amount is the cap. This is the default when you create a budget.
  • hours: capSeconds is the cap in billable seconds, for example 360000 for 100 hours. The budget has no amount. To switch an existing budget to an hour cap, send capBasis hours, capSeconds and amount null.

A budget schedule always caps by amount. Budgets that the tools return show capBasis and capSeconds.

Budgets and budget schedules also take targets. Each target has a metric (hours, cost, margin or effective_hourly_rate) and a value, and names one role, seniority, person or task, or none for the whole budget. A margin is a fraction, so 0.35 is 35%.

  • Replace: send targets to replace the current targets. Leave it out to keep them, or send an empty list to remove them all.
  • Schedules: a budget schedule copies its targets onto every budget it generates.
  • Reads: get_project and manage_project_financial_plan return each budget's and schedule's targets. A target value you may not see comes back empty.
  • Turned off: on a project with Targets turned off, a save with targets is refused with "Targets are turned off for this project."

See How budget targets work.

Phases are added, updated and removed with manage_project.

manage_budget_progress — create, update or remove the progress entries of a budget.

A progress entry records how much of a fixed-price budget is complete on a date, and it drives revenue recognition. The amount is money in the budget's currency, counted from the budget's start, not a percentage. An entry can also have a note.

  • Create: send items without an id. A new entry needs a date and a progressAmount.
  • Update: send items with the entry's id and only the fields to change. For example, send id and note to change only the note.
  • Remove: send the entry IDs in remove.
  • Order: the tool removes entries first, then creates or updates them in the order you send.
  • Limits: items and remove take at most 100 entries each.

The tool applies all changes together. If Operating refuses one change, it applies none. Get the budget ID and the entry IDs from get_project.

The tool uses the same rules as the app:

  • Dates: an entry's date must fall inside the budget's dates.
  • Reduction: an entry with a lower amount than the entry before it is a reduction. It needs a note, and only the latest entry can be one.
  • Milestones: an entry that a milestone created changes only through its milestone.
  • Permission: you need the Manage rates, budgets, planned expenses and baselines permission for the project.

Expenses (read + write)

list_expenses — logged expenses

manage_project_expenses — create, update or remove actual expenses and their line items. An expense that is already invoiced can't be removed.

An expense has two flags, reimbursable and reimbursed. list_expenses and manage_project_expenses return both flags for each expense.

  • Create: you can mark a new expense as reimbursable. A new expense always starts as not reimbursed, so a create request that sets reimbursed to true is refused. Create the expense first, then mark it reimbursed in an update.

  • Update: you can change either flag, and a flag you leave out keeps its value. Only a reimbursable expense can be marked reimbursed, and turning reimbursable off also clears reimbursed.

What you can do with it

An LLM connected to this MCP server can:

  1. Check availability — Find who's free in the next 7/30 days, filtered by role, site, or group

  2. Staff projects — Create positions and allocations to assign people to projects

  3. Reorganize assignments — Move positions between projects or allocations between positions

  4. Track time — Log hours for yourself or others against projects and tasks

  5. Browse the org — Look up people's details, skills, project history, and working hours

  6. Query project data — List and filter projects by client, owner, status, or tags

  7. Manage financials — create and adjust project budgets, expenses, and phases

  8. Create and update projects — spin up new projects, edit their properties, and archive or unarchive them

  9. Update people — change a person's details, roles, skills, groups, site or company from a given date