AI agents (MCP)
RentProg opens your company data to AI agents (Claude Code, Cursor, Cowork and any MCP client) through the MCP protocol. The agent acts on your behalf using a personal key. When you issue the key, you choose what the agent can do in each area separately. A key never gets more than your own rights: the same branches, records and fields you see in the interface.
1. Agent key
The “MCP for AI agents” service must be included in your company's plan. If the keys tab says the service is not included, contact RentProg support.
- Open Profile → tab “AI agent keys”.
- Click “Create key” and give it a name (e.g. “Claude Code — laptop”).
- Choose access by area (section 2) and click “Create”.
- Copy the key: it starts with
rpa_and is shown once.
Up to 5 active keys per employee, valid for one year. A key can be revoked on the same tab at any time and stops working immediately. Partners and agents (external roles) cannot issue keys. Every tool call is logged: who, which tool, when, outcome.
Where the data goes. Everything the key can see, including your clients' personal data, is sent by the agent to the AI service you connect (Claude, ChatGPT and others). Your company chooses that service and, as the data controller, is responsible for sharing data with it: make sure such a transfer is permitted by the laws of your country and your agreements with clients. If the agent does not need clients' personal data, issue the key to an employee with the guest role and set CRM to “No access”: guest does not see names, phones and other data of individual clients, while CRM leads and conversations contain client contacts for any role.
2. Access by area
A key covers four areas, each with its own level:
| Area | What it includes |
|---|---|
| CRM | leads, pipeline, conversations with clients, CRM tasks |
| Fleet and bookings | bookings, cars, clients, schedule, fines |
| Money | debts and deposits, money for a period, fleet economics, staff performance, suspicious operations |
| Staff | no tools yet |
| Level | What the agent can do |
|---|---|
| No access | does not see the area |
| Read | only looks at data |
| Write with approval | prepares a change that runs only after you approve it (section 5) |
| Write with preview | first gets the result of the change (for example, the reply text to a client) and then confirms it itself; the result is valid for 10 minutes |
| Write immediately | makes the change at once, without preview or confirmation |
By default a new key only reads: CRM, fleet and money — “Read”, staff — “No access”. Levels above what your role allows are not offered. If your role or rights are reduced later, the key immediately works within the new rights. We recommend “Write with approval” for money and “Write with preview” for CRM. Combining CRM read access with “Write immediately” for money is risky: a client's message could push the agent into a payment, and the key dialog warns about it.
Keys issued before access by area was introduced are marked “Read only, previous format”: they see the previous 16 tools without CRM. Reissue the key to get the new tools.
3. Installing the plugin in Claude Code
In Claude Code run:
/plugin marketplace add RentProg/rentprog-claude-plugin
/plugin install rentprog@rentprogClaude Code asks for two values: the key (your rpa_…) and the MCP address
(keep the default https://rentprog.net/mcp). To check, run /mcp: it lists the
rentprog server with its tools. To set a new key, run /plugin configure rentprog and then
reconnect the server in /mcp.
Ready-made scenarios (skills): morning brief, debtors, fleet load, client dossier, period summary — for
example, /rentprog:morning-brief. You can also ask in your own words: “what's going out today”,
“who owes for more than five days”, “which leads are waiting for a reply”. Every record in an answer links to its
card in RentProg. Plugin repository: github.com/RentProg/rentprog-claude-plugin.
4. Other MCP clients
The server is plain MCP over HTTP: any client that lets you set a request header will work. No separate account or setup on our side is needed — the key is the same.
Cursor. Create .cursor/mcp.json in your project (or ~/.cursor/mcp.json
for all projects):
{
"mcpServers": {
"rentprog": {
"url": "https://rentprog.net/mcp",
"headers": { "Authorization": "Bearer rpa_your_key" }
}
}
}Reload the MCP server list in Cursor settings — the rentprog server appears with the same tools
as in Claude Code. Skills are Claude Code commands and are not available in Cursor: ask in your own words, the
tool descriptions are self-contained. Do not commit the file with the key; if it leaks, revoke the key on the tab.
ChatGPT. Not supported yet: its connectors accept either no authentication or OAuth, so a personal key cannot be entered. OAuth support is separate work.
Common address for any client: https://rentprog.net/mcp, header
Authorization: Bearer rpa_… (Streamable HTTP). Per-key limits are counted separately: reads — 60 calls
per minute and 1000 per hour, changes — 20 per minute and 300 per hour.
5. Changes through the agent and approval
The agent can currently make changes in CRM: reply to a client, create and edit a lead, move it through the pipeline, link a booking or a contact, save a file from a conversation, add a note and a task, mark as read, archive a lead, convert it into a client, add to the Avito blacklist. Changes go through the same checks as in the interface: what the screen does not allow, the agent cannot do either.
With “Write with approval”, a prepared change goes to “Awaiting approval” (menu item and a bell notification). There you see what the agent is going to do; an approved change runs immediately, a rejected one does not. Without a decision the operation expires after 24 hours. The agent learns the outcome with its operation status tool.
A client reply and the Avito blacklist reach the outside world: a sent message cannot be recalled. That is why we recommend preview or approval for CRM.
6. What the agent sees by role
Key levels cap the agent from above, and the employee's role also limits the data scope and fields:
| Role | Data scope | Key levels | Fields and tools |
|---|---|---|---|
| superadmin | the whole branch group | up to “Write immediately” in every area | everything, including car cost and the money report |
| admin | own branch — the whole group only with the “change branch” right | up to “Write immediately” in every area | everything, including car cost and the money report |
| manager | own branch — the whole group only with the “change branch” right | up to “Write immediately” in every area | operational booking amounts; no car cost and no money report |
| user | own branch — the whole group only with the “change branch” right | up to “Write immediately”, except the Staff area | operational booking amounts; no car cost, money report, fleet economics, staff performance or suspicious operations |
| guest | the whole branch group | “Read” only, except the Staff area | money in full; no personal data of individual clients (name, phone, email, date of birth, tax ID, balance); companies in full; CRM leads and conversations as on the CRM screen, with contacts |
| partner, agent | — | no key is issued | — |
The CRM area is available only if CRM is enabled for your company and the employee has CRM access — the same as the CRM screen in the interface. Otherwise the key dialog marks it “Not available for your role or plan”.
RentProg API reference for developers: Swagger. Pricing: rentprog.com/en/tariffs.