🤖 This article was translated by AI.
What It Does
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 overviews, 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 integrated into Boond: ready to use, no installation required, 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: Installing the Connector
Prerequisites
You must be a manager 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) with a plan that allows adding a custom connector. This option depends on your assistant's editor and the plan you have subscribed to.
Step 1: Install the "MCP Boond" App
Log in to Boond with your manager account.
Go to Administration > Apps > Marketplace.
Open the record for the "MCP Boond" app (editor: 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, connecting your assistant will return an error message. It is done in two phases.
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, all managers, authorized managers and all resources, or 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 upon 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 across tools:
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 app 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 authorized or requires your approval for each use.
Our recommendation: leave read tools open, and require manual approval for write tools (creation, modification, sending email).
If you use scheduled tasks or autonomous sessions (for example, Claude Cowork), remember to enable the necessary permissions: otherwise, your tasks will remain blocked awaiting 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 replies with your Boond data, the connection is active.
Part 2: Everything You Can Do with MCP
How Does It Work, in a Nutshell?
You speak to your assistant in natural language. To answer you, it relies on tools provided by Boond: searching for records, reading their content, creating or editing them. For each action, your BoondManager rights apply: the assistant only sees and edits what you could see and edit yourself in Boond.
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 Does |
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, expenses, questionnaires. |
Read a record (fetch) | Retrieves the details of a record, tab by tab: information, technical data, positionings, time, etc. |
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, etc. |
Know your perimeter (perimeter) | Identifies your agencies, managers, poles, and business units accessible. |
Know your context (context) | Knows who you are: identity, access level, perimeter. This personalizes every answer. |
For Acting
Tool | What It Does |
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: approve, reject, or unapprove a timesheet, an absence request, or an expense report. |
Send an email (send_email) | Sends an email to an employee, a contact, or a candidate, only after your explicit confirmation, and logs the exchange as an action on the record. |
Integrated Business Guides
The MCP Boond includes business guides that your assistant loads on demand. Three guides are available at launch: logging an action (note, call, email, interview, meeting) on the right record, creating a delivery on a project (assigning a resource with dates, rate, and workload), and entering an expense report (actual, flat-rate, and mileage expenses). These guides encode Boond best practices, so the assistant doesn't guess how to work in your tool: it follows the method. The list is continuously growing.
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 1 to 31."
Concrete Examples by Business Area
Sales
"List my opportunities closing this month, sorted by amount."
"Prepare an overview of Acme before my 2pm meeting: latest 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 of Lyon." The search accepts your qualification criteria, your configuration's availability ranges, and even a geographic radius.
"Summarize candidate Dupont's background and their last three actions."
"Create an opportunity for client Acme for a senior DevOps profile."
Staffing & HR
"Which consultants are finishing 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 & Finance
"Fill in my timesheet for the month: 20 days on the Acme project."
"Approve Marie Dupont's August timesheet." Approvals, rejections, and unapprovals of timesheets, absences, and expense reports follow your usual workflows, with the same rights.
"Find invoices for company Acme."
Go Further: Automations
Because MCP works with any compatible tool, you can also integrate it into broader workflows: your assistant can cross-reference Boond with your messaging, documents, or other tools. For example: identify consultants in Boond who will soon be available, then prepare the corresponding proposal emails—all in a single request.
Best Practices
Be specific. 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 edit tools: you validate each action before it executes.
Check after writing. After creating or editing, take a look at the record in Boond, especially the first few times. It's the best way to calibrate your trust.
Start with reading. Searches and overviews are the safest ways to get started with the connector before moving on 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 each 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 be handled by a dedicated module.
Reading attachments on records (resumes, attachments): planned for future updates.
FAQ
What subscription do I need to use MCP Boond?
On the Boond side, MCP is included in Advanced, Business, and Enterprise plans, with no additional subscription.
On the AI assistant side, its editor decides if your plan allows adding a custom MCP connector (also called "custom connector" or "developer mode"). These conditions change regularly and do not depend on Boond. We therefore cannot tell you which plan to subscribe to.
I can't find where to add a connector in my AI assistant. Why?
If the option does not appear, the limitation comes from the AI assistant, not Boond. Several reasons are possible: your plan does not allow adding a custom connector, the feature is not enabled in the settings, or your AI tool's manager has restricted it within your organization. Check with the editor or the person who manages the tool in your company.
The connection to Boond works, but my assistant asks me to subscribe. Is this normal?
If you were redirected to the Boond page, clicked "Authorize," and the connection was validated, the link with Boond is operational. A message asking you to subscribe or change your plan then comes from your AI assistant: it depends on your plan's limits with its editor.
I get an error when connecting. What should I check?
First, check these points on the Boond side:
your account is on an Advanced, Business, or Enterprise plan;
the "MCP Boond" app is installed (Administration > Apps > Marketplace);
its visibility includes your profile;
if visibility is restricted to authorized managers, the app is enabled for your role in Managers / Roles > APPS;
the address entered in your assistant is https://ui.boondmanager.com/api/mcp.
If the error persists, contact support specifying the AI assistant used, the step where the connection fails (adding the connector, redirecting to Boond, after "Authorize") and the exact error message, with a screenshot.
Where does my data go?
Your AI queries Boond and only sees what you can see. What it does with it next depends on your contract with its editor.
Can the AI see more than the user?
No, it has the same rights as the user using it. These rights are checked on 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.
Are our data used to train an AI?
On the Boond side: no, never. On your AI side: it depends on your plan with its editor.
Can it edit 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.