How to connect Clientary to OpenClaw
Connect Clientary to OpenClaw with ClawLink: paste your Clientary key once and 57 tools work from chat. No MCP server to run, nothing stored on your machine.
ClientaryAPI KEYMCPA full-suite platform to manage Clients, Invoices, Projects, Proposals, Estimates, Hours, Payments, Contractors and Staff.. Once connected, OpenClaw can read and act on Clientary from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Clientary 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 Clientary setup: install one ClawHub skill, connect Clientary in the browser, and OpenClaw can call real Clientary actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Clientary.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Clientary
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Clientary?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Clientary in the ClawLink dashboard — paste your Clientary API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Clientary, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Clientary is connected in the dashboard, that agent calls the same 57 Clientary tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Clientary MCP for OpenClaw
Looking for a Clientary MCP server for OpenClaw? ClawLink connects Clientary to OpenClaw and exposes 57 Clientary tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Clientary integration works the same way.
What the OpenClaw Clientary integration can do
57 Clientary 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 57.
30 of 57 Clientary tools for OpenClaw
| Tool | What it does |
|---|---|
Get client clientary_get_client | Fetch details for a specific client using its ID |
Get contact clientary_get_contact | Retrieve a single contact by its ID |
Get estimate clientary_get_estimate | Retrieve details for a single estimate by ID |
Get expense clientary_get_expense | Retrieve details for a single expense record in Clientary |
Get hour clientary_get_hour | Obtain details about a specific time entry in Clientary |
Get invoice clientary_get_invoice | Retrieve detailed information for a specific invoice by ID |
Get lead clientary_get_lead | Retrieve a single lead by its ID |
Get project clientary_get_project | Retrieve a single project by its identifier |
Get staff clientary_get_staff | Retrieve a single staff member by their ID |
Get task clientary_get_task | Retrieve a specific task by its ID |
List client contacts clientary_list_client_contacts | Retrieve all contacts for a specific client with pagination support |
List client estimates clientary_list_client_estimates | Retrieve all estimates for a specific client with pagination support (30 results per page) |
List client expenses clientary_list_client_expenses | Retrieve all expenses for a specific client within an optional date range |
List client invoices clientary_list_client_invoices | Retrieve all invoices for a specific client with pagination support (30 results per page) |
List client payment profiles clientary_list_client_payment_profiles | Retrieve payment profiles for a specific client |
List client projects clientary_list_client_projects | Retrieve all projects associated with a specific client with pagination support (10 results per |
List clients clientary_list_clients | Retrieve all clients with pagination support (10 results per page) |
List estimates clientary_list_estimates | Retrieve all estimates with pagination support (30 results per page) |
List expenses clientary_list_expenses | Retrieve expenses by date range (defaults to current fiscal year) |
List leads clientary_list_leads | Retrieve all leads with pagination support |
List payments clientary_list_payments | Retrieve all payments with pagination support (30 results per page) |
List project estimates clientary_list_project_estimates | Retrieve estimates scoped to a particular project with pagination support (30 results per page) |
List project expenses clientary_list_project_expenses | Retrieve all expenses for a specific project within an optional date range |
List project hours clientary_list_project_hours | Retrieve all time tracking entries logged against a specific project |
List project invoices clientary_list_project_invoices | Retrieve all invoices linked to a specific project with pagination support (30 results per page) |
List project tasks clientary_list_project_tasks | Retrieve all tasks for a specific project |
List projects clientary_list_projects | Retrieve all projects with pagination support (10 results per page) |
List recurring schedule invoices clientary_list_recurring_schedule_invoices | Retrieve all invoices generated by a specific recurring schedule with pagination support (30 |
List staff clientary_list_staff | Retrieve all staff members for an account |
List tasks clientary_list_tasks | Retrieve all tasks with pagination support (50 results per page) |
Try it: find the Clientary tool you need
Browse the 30 Clientary tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Clientary, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Clientary, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Clientary, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Clientary, 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 Clientary working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Clientary API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Clientary 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 Clientary. | 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 Clientary actions to the runtime in a format your agent can reliably use. | 57 tools for Clientary are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Clientary 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 Clientary in the browser, and the 57 tools above work from chat. There is no SDK and no config file, and the Clientary key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Clientary skill but can't call the tools
The ClawHub skill teaches OpenClaw about Clientary, but the calls run through the ClawLink plugin and your connected account. Make sure Clientary 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 Clientary 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 Clientary tools
Clientary 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 Clientary 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.
Clientary 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 Clientary has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Clientary integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Clientary: link your Clientary account once in the browser and OpenClaw can call the Clientary API through 57 ready-made tools — no custom code or token handling.
How do I add Clientary to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Clientary skill from ClawHub, then you click Connect in the dashboard to authorize Clientary. OpenClaw calls the tools from the next message — no config files, and the Clientary key you paste is stored server-side instead of in your environment.
How long does it take to connect Clientary to OpenClaw?
About two minutes. Sign in, click Connect next to Clientary in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Clientary 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 Clientary working from chat.
OpenClaw installed the Clientary skill but can't call the tools
The ClawHub skill teaches OpenClaw about Clientary, but the calls run through the ClawLink plugin and your connected account. Make sure Clientary 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.
