🤖 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 synthesis, and even create or update cards, 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 keep 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, 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 a manager of your Boond account (right 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 manager account.
Go to Administration > Apps > Marketplace.
Open the card for the "MCP Boond" app (publisher: Boond).
Click the Install button at the top right of the card.
A confirmation window opens and shows the rights 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: Set 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 the app visibility
On the app card, 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: Activate 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.
Activate MCP Boond for each manager (or role) who should be able to use the connector.
⚠️ Most common mistake
Activation at the role level, when visibility is limited to authorized managers. If a user gets a log in error while the app is installed, check that the app has been activated 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 from one tool to another:
In your AI assistant, open the connectors / integrations (MCP) settings and add a new connector.
Enter the address of the MCP Boond server: 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 allowed 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 activate 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 of 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 talk to your assistant in natural language. To answer you, it relies on tools provided by Boond: search for cards, read their content, create or edit them. For each action, your BoondManager rights apply: the assistant only sees and edits what you could see and edit 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 in all your modules: candidates, resources, companies, contacts, opportunities, projects, positionings, deliveries, purchases, orders, invoices, products, actions, timesheets, absences, expense reports, questionnaires. |
Read a card (fetch) | Retrieves the details of a card, 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, access level, perimeter. This personalizes each answer. |
For acting
Tool | What it allows |
Create (create) | Creates a new card: a candidate, an action, an opportunity, a delivery... Some modules remain read and edit only (invoices, orders, purchases). |
Edit (update) | Updates an existing card, field by field, including custom fields. |
Validate or reject (transition) | Applies your validation workflows: validate, reject, or unvalidate a timesheet, an absence request, or an 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 card. |
Integrated business guides
The 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 card, 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 1 to 31."
Concrete examples, by business
Sales
"List my opportunities closing this month, sorted by amount."
"Prepare a synthesis of the Acme company 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 skill, available within 1 month, within a 50 km radius around Lyon." The search accepts your qualification criteria, your configuration's availability ranges, 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 go through your usual workflows, with the same rights.
"Find the invoices for the Acme company."
Go further: automations
Because MCP works with any compatible tool, you can also integrate it into broader sequences: your assistant combines Boond with your messaging, documents, or other tools. For example: identify in Boond the consultants soon available, then prepare the corresponding proposal emails, all in a single 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 on creation and edit tools: you validate each action before it executes.
Check after writing. After a creation or edit, take a look at the card in Boond, especially the first times. It's the best way to calibrate your trust.
Start with reading. Searches and synthesis are the safest uses to get started with the connector before moving to writing.
Your data and your rights
The assistant only sees what the logged-in user is allowed to see in BoondManager. Rights apply to each 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 go through a dedicated module.
Reading documents attached to cards (resumes, attachments): planned for future updates.