Webinar (Wednesday, October 21) — Aligning HR, Finance, and Sales: Mastering Sales Comp Without Breaking Your Plan
Register- Qobra and Dust are now official partners. The Qobra MCP is available in the Dust marketplace for both regions: Qobra EU and Qobra US.
- Dust agents get 65 actions: 45 to read (quota attainment, statements with line-by-line breakdowns and underlying records, commission plans, reports, dashboards, audit logs) and 20 to write (users and groups, data tables and records, quotas, plans, reports and dashboards, requests).
- Access is scoped to the user. Agents get the same permissions as the person in the Qobra app, and every write is recorded in the audit trail, tagged as done through the MCP.
- Setup takes minutes: a Qobra admin enables MCP access in Settings, then each user signs in to Qobra from the Dust chat.
- Customers like Doctolib already run it in production, from answering reps' compensation questions to tracking bonus landing across teams.
Qobra, the sales compensation platform, has entered a partnership with Dust, the platform companies use to build and run multiplayer AI agents on their own data. Starting today, the Qobra MCP is listed natively in the Dust integrations marketplace. Any Dust agent can retrieve quota attainment, commission statements, plans, and reports from Qobra, and act on them: assign users, fill quotas, adjust records, answer requests, all within each user's own Qobra permissions. No custom connector, no URL to paste.
Why connect sales compensation to AI agents
Compensation data is the most asked-about data in a sales organization and the least accessible one. A rep wants to know where they stand against quota. A manager wants to know what the team will land. A comp admin spends hours each cycle answering "why did my commission change?" with screenshots, then more hours adding users, filling quotas, and adjusting deals by hand. The answers and the actions live in Qobra, but the questions are asked in Slack, in email, or in the AI assistant the company already uses.
Dust is that assistant for a growing number of companies. More than 3,000 organizations build agents on Dust, connected to their CRM, their documents, and their internal tools. Our customers were among the first to connect Qobra to it, through the Qobra API and then through our MCP server. The partnership makes that path official, supported, and available to every Dust workspace in one click.
"Sales teams do not want another dashboard, they want an answer. With Dust, a rep asks where they stand and gets the number, the deals behind it, and the plan rule that explains it, in the tool they already use every day. That is what the Qobra MCP and our AI agents are for."
Antoine Fort, CEO at Qobra
"Compensation is a domain where accuracy and permissions matter more than anywhere else, and Qobra's MCP gets both right. Dust customers can now bring accurate, precise quota and commission data into any workflow, safely."
Thibault Martin, Ecosystem Lead at Dust
What the Qobra MCP can do in Dust: read, analyze, administrate
The Qobra integration in Dust exposes 65 actions: 45 to read and 20 to write. They cover five areas.
Administration
The write actions let an agent run Qobra, centrally and under control: add a user to the right group, create a quota and fill its targets per user and period, add or split a record in a data table, create a plan and attach a commission rule, build a report or a dashboard, open a request or reply in its thread, update exchange rates. The admin stays in charge; the agent does the clicking.
Each action respects the permissions of the Qobra user who signed in. A sales rep connecting from Dust sees fewer tools than an administrator, exactly as in the Qobra app. Every write shows up in the Qobra audit trail, tagged as an MCP action, so nothing changes without a trace. Statements and payouts are never edited by an agent.
Quota attainment and statements
Current and past quota values for a person, a team, or a period, plus the commission statements that go with them: the line-by-line compensation breakdown and the underlying records. "Where are we against quota this quarter?" returns the attainment and the values behind it. "Why did my commission change between March and April?" gets answered by comparing the two statements and naming the deals that moved.
Plans and commission letters
The rules each person is paid on. The agent reads the plan to explain a number in context instead of restating it.
Reports, dashboards, and audit logs
Any report built in Qobra becomes a data source for an agent. Audit logs let a controller ask who changed what, and when.
High-value use cases our customers run today
The examples below come from customers who connected Qobra to Dust before the native listing. The companies are not named; the workflows are real.
Answering reps' compensation questions in minutes
A European healthcare technology company with several thousand Dust users receives compensation requests from its sales team every week: a missing deal, a rate that looks wrong, a bonus that did not land as expected. The comp team built a Dust agent that reads the request, pulls the rep's statement, the underlying records, and the plan from Qobra, and drafts an answer with the calculation spelled out. The person who runs the process told us the main gain is speed: when people have questions about their pay, they want an answer fast, and sensitive topics get a documented reply instead of a back-and-forth.
"On requests, it works very, very well. The main point for me is that it lets me answer faster. When people have questions about their compensation, they want a quick answer."
Jean de Keerle, Sales Ops at Doctolib
Tracking bonus landing across teams without exports
The same company's sales operations team used to export data from Qobra and from its HR system into a spreadsheet to track bonus attainment across plans. With the MCP, a Dust agent reads Qobra reports directly, compares attainment by team and by period, and flags the KPIs that drift. The spreadsheet export is gone, and the analysis runs on the same numbers the statements are paid on.
"The huge use cases we have are on the MCP. Building the first reports with it is excellent, and there is still a lot more to unlock."
Benoît Di Loreto, Sales Ops & Strategy at Doctolib
Combining CRM pipeline and Qobra plans to forecast earnings
Dust agents already connect to Salesforce and HubSpot. Add Qobra, and a rep can ask "what do I earn if I close these three deals this month?" The agent reads open pipeline from the CRM, the rep's current attainment and plan rules from Qobra, and returns an estimate with the accelerator thresholds that apply. For managers, the same agent answers "which reps are within one deal of their next tier?" Qobra remains the source of truth for the actual payout; the agent gives the forward view that used to live in a personal spreadsheet.
Cutting low-value admin tasks in run mode
Running a compensation plan is mostly small, repetitive work: adding new hires to the right plan, checking that the CRM export and Qobra records match, filling in quotas for the quarter, adjusting a deal, recording an exception, answering the request that flagged it. With the write actions, the agent that answers a rep's question also acts on it, under the admin's review: it assigns the user, sets the quota, splits the deal between two reps, and replies in the request thread. The admin validates, the agent executes, and every step is in the audit trail.
Monitoring changes for finance and controllers
Audit logs are part of the MCP. A finance team can set up an agent that summarizes plan and quota changes each week, or that answers "who edited this rate and when?" before payroll closes. With agents now able to write, this trail is also how finance verifies what the agents did.
How to connect Qobra to Dust in 3 steps
- A Qobra administrator enables MCP access in Qobra: Settings > AI > MCP.
- In Dust, open the integrations marketplace and add Qobra. Pick the server that matches your account: Qobra EU or Qobra US.
- Sign in with your Qobra account from the Dust chat. The connection uses OAuth, so no API key is shared and the authorization can be revoked at any time.
Each user connects with their own Qobra login, which is what keeps the agent's answers and actions within that user's permissions. The technical details, including the full list of tools, are in the Qobra MCP documentation.
What's next
Two directions from here: more tools so you can adapt the MCP to your own workflows, and a connection to Qobra's modeling capabilities, so an agent can stress-test a plan and measure its efficiency before it goes live. If you already run Qobra and Dust, tell your account manager which workflow you want to automate next. If you use Dust and still calculate commissions in spreadsheets, this is a good moment to see what Qobra does with your sales data.
About Dust
Dust is the platform teams use to build, share, and run multiplayer AI agents on their company's knowledge and tools. Used by 3,000+ organizations, Dust connects agents to CRMs, documents, and internal systems so that every team can automate its own workflows with the governance enterprises require.
About Qobra
Qobra is a sales compensation platform that lets RevOps, finance, and HR teams design, calculate, and communicate commissions without code. Qobra has processed $1B+ in commissions across 300+ companies, and is recognized as a Momentum Leader by G2. Sales reps see their earnings in real time, managers track team performance, and finance closes payroll in days instead of weeks. Learn more at qobra.co.

Frequently asked questions
What does the Qobra and Dust partnership include?
An official partnership between the two companies and the native listing of the Qobra MCP in the Dust integrations marketplace, for EU and US accounts.
What can a Dust agent read and do in Qobra?
Read: quota attainment, commission statements and their underlying records, commission plans and letters, reports, dashboards, and audit logs, through 45 actions. Write: users and groups, data tables and records, quotas, plans, reports, dashboards, and requests, through 20 actions.
Can an agent modify data in Qobra?
Yes, within limits. Agents can create and update users and groups, data tables and records, quotas, plans, reports, dashboards, and requests, with the same role permissions as the Qobra app. Every change is recorded in the audit trail as an MCP action. Statements and payouts are never edited by an agent.
Who can see what?
Each user connects with their own Qobra account, and every action is scoped to that user's Qobra permissions. A rep sees their own data; an admin sees and does what an admin can in the app.
Do I need a Dust Enterprise plan or a custom connector?
No custom connector. Qobra is listed in the Dust marketplace, so any workspace can add it from the integrations page. Check with Dust for plan-specific availability.
Is the Qobra MCP available outside Dust?
Yes. The same MCP server works with Claude and ChatGPT. See the documentation.
Ready to put your agents to work on commissions? Book a demo and see the Qobra x Dust integration live.






