# How to connect Rentman to OpenClaw (paste one key, 130 tools) > Connect Rentman to OpenClaw with ClawLink: paste your Rentman key once and 130 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/rentman The usual route to Rentman access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Rentman setup: install one ClawHub skill, connect Rentman in the browser, and OpenClaw can call real Rentman actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/rentman ## Setup It takes three steps to connect OpenClaw to Rentman. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Rentman** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect rentman # connect Rentman (browser OAuth) npx -y @useclawlink/cli actions rentman # list available actions npx -y @useclawlink/cli run rentman --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Rentman in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Rentman API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Rentman, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Rentman is connected in the dashboard, that agent calls the same 130 Rentman tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Rentman MCP for OpenClaw Looking for a Rentman MCP server for OpenClaw? ClawLink connects Rentman to OpenClaw and exposes 130 Rentman tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Rentman integration](https://claw-link.dev/hermes/rentman) works the same way. ## What the OpenClaw Rentman integration can do 130 Rentman tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 130. ### 30 of 130 Rentman tools for OpenClaw | Tool | What it does | |---|---| | **Get accessories collection** `rentman_get_accessories_collection` | Retrieve a collection of accessories from Rentman | | **Get appointment crew** `rentman_get_appointment_crew` | Retrieve the linked crew members for a specific appointment | | **Get appointmentcrew collection** `rentman_get_appointmentcrew_collection` | Retrieve appointmentcrew collection from Rentman | | **Get appointments collection** `rentman_get_appointments_collection` | Retrieve a collection of appointments from Rentman | | **Get contact contactpersons** `rentman_get_contact_contactpersons` | Retrieve all contactpersons linked to a specific contact in Rentman | | **Get contact file folders** `rentman_get_contact_file_folders` | Get file folders linked to a contact | | **Get contact files** `rentman_get_contact_files` | Get files linked to a contact | | **Get contact person files** `rentman_get_contact_person_files` | Retrieve files linked to a contact person in Rentman | | **Get contact persons** `rentman_get_contact_persons` | Retrieve the collection of contact persons from Rentman | | **Get contactperson file folders** `rentman_get_contactperson_file_folders` | Retrieve file folders linked to a contact person in Rentman | | **Get contacts collection** `rentman_get_contacts_collection` | Retrieve a collection of contacts from Rentman | | **Get contract invoicelines** `rentman_get_contract_invoicelines` | Retrieves invoicelines linked to a specific contract | | **Get contract item files** `rentman_get_contract_item_files` | Retrieve files linked to a specific contract | | **Get contracts collection** `rentman_get_contracts_collection` | Retrieve a collection of contracts from Rentman | | **Get costs collection** `rentman_get_costs_collection` | Retrieve costs collection from Rentman | | **Get crew appointments** `rentman_get_crew_appointments` | Retrieve appointments for a specific crew member | | **Get crew availability** `rentman_get_crew_availability` | Retrieve crew availability records for a specific crew member in Rentman | | **Get crew availability collection** `rentman_get_crew_availability_collection` | Retrieve crew availability collection from Rentman | | **Get crew collection** `rentman_get_crew_collection` | Retrieve crew collection from Rentman | | **Get crew file folders** `rentman_get_crew_file_folders` | Retrieve file folders linked to a crew member | | **Get crew files** `rentman_get_crew_files` | Retrieve files linked to a crew member | | **Get crew member** `rentman_get_crew_member` | Retrieve a crew member item by ID from Rentman | | **Get crew rates** `rentman_get_crew_rates` | Get crew rates linked collection for a specific crew member | | **Get crewrates** `rentman_get_crewrates` | Retrieve crewrates collection from Rentman | | **Get equipment accessories** `rentman_get_equipment_accessories` | Get accessories linked to a specific equipment item | | **Get equipment collection** `rentman_get_equipment_collection` | Get the equipment collection from Rentman | | **Get equipment file folders** `rentman_get_equipment_file_folders` | Get file folders linked to equipment | | **Get equipment files** `rentman_get_equipment_files` | Get files linked to equipment | | **Get equipment repairs** `rentman_get_equipment_repairs` | Retrieve repairs linked to a specific equipment item | | **Get equipment serialnumbers** `rentman_get_equipment_serialnumbers` | Retrieve serial numbers linked to a specific equipment item | ## Example prompts **Get Accessories Collection** > Pull the relevant data from Rentman, summarize it in plain English, and point out anything that needs attention. **Get Appointment Crew** > Pull the relevant data from Rentman, summarize it in plain English, and point out anything that needs attention. **Get Appointmentcrew Collection** > Pull the relevant data from Rentman, summarize it in plain English, and point out anything that needs attention. **Get Appointments Collection** > Pull the relevant data from Rentman, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Rentman working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Rentman API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Rentman account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Rentman. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Rentman actions to the runtime in a format your agent can reliably use. | 130 tools for Rentman are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Rentman to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Rentman in the browser, and the 130 tools above work from chat. There is no SDK and no config file, and the Rentman key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Rentman skill but can't call the tools The ClawHub skill teaches OpenClaw about Rentman, but the calls run through the ClawLink plugin and your connected account. Make sure Rentman is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Rentman from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Rentman tools Rentman tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Rentman call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Rentman returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Rentman has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Rentman integration? Yes. ClawLink is the fastest way to connect OpenClaw to Rentman: link your Rentman account once in the browser and OpenClaw can call the Rentman API through 130 ready-made tools — no custom code or token handling. ### How do I add Rentman to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Rentman skill from ClawHub, then you click Connect in the dashboard to authorize Rentman. OpenClaw calls the tools from the next message — no config files, and the Rentman key you paste is stored server-side instead of in your environment. ### How long does it take to connect Rentman to OpenClaw? About two minutes. Sign in, click Connect next to Rentman in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Rentman up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Rentman working from chat. ### OpenClaw installed the Rentman skill but can't call the tools The ClawHub skill teaches OpenClaw about Rentman, but the calls run through the ClawLink plugin and your connected account. Make sure Rentman is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [DocuSign tools](https://claw-link.dev/openclaw/docusign) — Send, sign, and manage agreements and envelopes - [Trello tools](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [Moco](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions.