🤖 This article was translated by AI.
What is it for
The MCP connector allows your AI assistant (Claude, ChatGPT, or any other MCP-compatible tool) to work directly with your Boond data: answer your questions, find information, prepare syntheses, and even create or update records, always under your control.
Your data remains protected: the assistant only sees what the logged-in user is allowed to see in Boond, and you retain control over the actions it can perform.
MCP or Boond Pulse?
Boond Pulse is the AI assistant built into Boond: ready to use, no installation, directly in the product.
The MCP connector connects YOUR AI assistant to your Boond data: ideal if your organization already uses Claude or ChatGPT and wants to integrate Boond alongside its other tools.
Part 1: Install the connector
Prerequisites
You must be an administrator of your Boond account (permission to manage apps and roles).
Your account must be on an Advanced, Business, or Enterprise plan.
You must have an MCP-compatible AI assistant (for example, Claude or ChatGPT).
Step 1: Install the "MCP Boond" app
Log in to Boond with your administrator account.
Go to Administration > Apps > Marketplace.
Open the "MCP Boond" app record (publisher: Boond).
Click the Install button at the top right of the record.
A confirmation window opens and displays the permissions requested by the app. By clicking Confirm, you accept the marketplace terms and the app's access to your data.
You can revoke the app at any time from Installed Apps.
Step 2: Configure access rights
This step is essential. Without it, the connection to your assistant will return an error message. It is done in two stages.
2.1: Set app visibility
On the app record, click the cogwheel next to the Install button.
In "App visibility", choose the desired perimeter: accessible only to authorized managers, to all managers, to authorized managers and all resources, or to all managers and resources.
Click Edit to save.
2.2: Enable the app for authorized managers
This step is only necessary if you chose visibility "accessible only to authorized managers". If you opened the app to all managers, go directly to step 3.
Go to Managers / Roles, APPS tab.
Enable MCP Boond for each manager (or role) who should be able to use the connector.
⚠️ Most common oversight
Activation at the role level, when visibility is limited to authorized managers. If a user gets an error when logging in while the app is installed, check that the app has been enabled for their role in Managers / Roles > APPS.
Step 3: Connect your AI assistant
The connection is made from your AI tool, not from Boond. The process is similar for each tool:
In your AI assistant, open the connectors / integrations (MCP) settings and add a new connector.
Enter the MCP Boond server address: https://ui.boondmanager.com/api/mcp
Your tool redirects you to a Boond page. Check that the displayed application is yours (e.g., ChatGPT) and that the redirect address looks legitimate, then click Authorize
A validation screen confirms the connection. You are then redirected to your assistant, now connected.
Step 4: Set tool permissions
Once connected, your assistant has access to a set of Boond tools. In the connector settings, you choose for each tool whether it is always allowed or whether it requires your approval for each use.
Our recommendation: leave read tools open access, and require manual approval for write tools (creation, modification, email sending).
If you use scheduled tasks or autonomous sessions (for example, Claude Cowork), remember to enable the necessary permissions: otherwise, your tasks will remain blocked waiting for a click on "authorize".
Step 5: Check that it works
Ask your assistant a simple question, for example: "List my latest opportunities" or "Give me the information for company X".
If the assistant responds with your Boond data, the connection is active.
Part 2: Everything you can do with MCP
How it works, in a nutshell
You speak to your assistant in natural language. To answer you, it relies on tools provided by Boond: search for records, read their content, create or modify them. For each action, your BoondManager rights apply: the assistant only sees and modifies what you could see and modify yourself in Boond.
The tools available to your assistant
The connector exposes twelve tools, which your assistant freely combines according to your request.
For reading and understanding
Tool | What it allows |
Search (search) | Multi-criteria and paginated search across all your modules: candidates, resources, companies, contacts, opportunities, projects, positionings, deliveries, purchases, orders, invoices, products, actions, timesheets, absences, expense reports, questionnaires. |
Read a record (fetch) | Retrieves the details of a record, tab by tab: information, technical data, positionings, time... |
Understand your configuration (describe) | Discovers your modules, tabs, and fields, including custom fields from your no-code apps, with your own labels. |
Read your dictionaries (dictionary) | Uses your value lists as configured on your account: states, types, titles, countries... |
Know your perimeter (perimeter) | Identifies your Agencies, Managers, Poles, and Business units accessible. |
Know your context (context) | Knows who you are: identity, rights level, perimeter. This personalizes each response. |
For acting
Tool | What it allows |
Create (create) | Creates a new record: a candidate, an action, an opportunity, a delivery... Some modules remain read and edit only (invoices, orders, purchases). |
Edit (update) | Updates an existing record, field by field, including custom fields. |
Validate or reject (transition) | Applies your validation workflows: validate, reject, or unvalidate a timesheet, absence request, or expense report. |
Send an email (send_email) | Sends an email to an employee, contact, or candidate, only after your explicit confirmation, and logs the exchange as an action on the record. |
Integrated business guides
MCP Boond includes business guides that your assistant loads on demand. Three guides are available at launch: log an action (note, call, email, interview, meeting) on the right record, create a delivery on a project (assign a resource with its dates, rate, and schedule), and enter an expense report (actual, flat-rate, and mileage expenses). These guides encode Boond best practices, so the assistant does not guess how to work in your tool: it applies the method. The list is continuously enriched.
You don't have to do anything to benefit: the assistant loads the right guide according to your request. You can also request it explicitly, for example: "Load the delivery creation guide, then assign Jean Dupont to the Acme project from October 1st to 31st."
Concrete examples, by business area
Sales
"List my opportunities closing this month, sorted by amount."
"Prepare a synthesis of Acme company before my 2pm meeting: last actions, ongoing opportunities, active projects."
"Create a follow-up action for contact Martin Durand, due Friday."
Recruitment
"Find candidates with Java skills, available within 1 month, within a 50 km radius around Lyon." The search accepts your qualification criteria, availability ranges from your configuration, and even a geographic radius.
"Summarize candidate Dupont's background and his last three actions."
"Create an opportunity for client Acme on a senior DevOps profile."
Staffing and HR
"Which consultants finish their assignment in the next 30 days?"
"Create my absence request: one day off on the 15th." The assistant creates the request, which then follows your usual validation workflow.
Management and Finance
"Fill in my timesheet for the month: 20 days on the Acme project."
"Validate Marie Dupont's August timesheet." Validations, rejections, and unvalidations of timesheets, absences, and expense reports follow your usual workflows, with the same rights.
"Find invoices for Acme company."
Go further: automations
Because MCP works with any compatible tool, you can also integrate it into broader workflows: your assistant combines Boond with your messaging, documents, or other tools. For example: identify consultants soon available in Boond, then prepare the corresponding proposal emails, all in one request.
Best practices
Be precise. The more your request names things (module, period, client), the more accurate the answer will be the first time.
Keep control over writing. Set manual approval for creation and modification tools: you validate each action before it is executed.
Check after writing. After a creation or modification, take a look at the record in Boond, especially the first times. It's the best way to calibrate your trust.
Start with reading. Searches and syntheses are the safest uses to get started with the connector before moving to writing actions.
Your data and your rights
The assistant only sees what the logged-in user is allowed to see in BoondManager. Rights apply to every request, without exception.
Boond never links data from different clients.
Your organization chooses which tools are accessible, and each user can require approval before every action.
What MCP does not cover today
Bulk data processing and aggregated reporting (calculations on your entire database): this is a work in progress, which will go through a dedicated module.
Reading documents attached to records (resumes, attachments): planned for future developments.
FAQ
Where does my data go?
Your AI queries Boond and only sees what you can see. What it does with it afterwards depends on your contract with its publisher.
Can AI see more than the user?
No, it has the same rights as the user who uses it. These rights are checked with every call.
Does Boond keep or read our conversations?
No, Boond does not keep the conversation. It only receives tool calls, executed as actions performed by the user in Boond.
Is our data used to train an AI?
On Boond's side: no, never. On your AI's side: it depends on your agreement with its publisher.
Can it modify or delete without us seeing?
No deletion tool exists. Writing actions (create, edit, validate, email) require manual approval by default, which the admin can disable.