# How to connect Maintainx to Hermes Agent (paste one key, 30 tools)

> Connect Maintainx to Hermes with ClawLink: paste your Maintainx key once and 30 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/maintainx

Most guides for giving Hermes Agent Maintainx access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Maintainx setup: pair once in the browser and your always-on Hermes agent can act on Maintainx for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

## Setup

It takes three steps to connect Hermes to Maintainx.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Maintainx** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**Paste this into Hermes to set up ClawLink:**

> Set up ClawLink for Hermes and tell me when it's ready.
> 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable`
> 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait.
> 3. I'll approve it in my browser, then reply "approved".
> 4. When I say approved, finish setup: `hermes clawlink finish`
> 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

**Alternative for any agent (no plugin needed):** if the Hermes Agent 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 maintainx  # connect Maintainx (browser OAuth)
npx -y @useclawlink/cli actions maintainx  # list available actions
npx -y @useclawlink/cli run maintainx <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

```bash
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test
```

Then connect Maintainx in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Maintainx API key once.

Verify the connection by asking Hermes:

> Use Maintainx to find entity and walk me through the result in plain English.

### Using a different agent?

The Hermes 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 Maintainx is connected in the dashboard, that agent calls the same 30 Maintainx 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).

## Maintainx MCP for Hermes

Looking for a Maintainx MCP server for Hermes Agent? ClawLink connects Maintainx to Hermes Agent and exposes 30 Maintainx 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 OpenClaw instead? The [OpenClaw Maintainx integration](https://claw-link.dev/openclaw/maintainx) works the same way.

## What the Hermes Agent Maintainx integration can do

30 Maintainx tools are ready for Hermes Agent once the account is connected. The 28 below are the ones people reach for most; your agent can call all 30.

### 28 of 30 Maintainx tools for Hermes

| Tool | What it does |
|---|---|
| **Find entity** `maintainx_find_entity` | A tool to search and find specific entities within MaintainX by specified fields |
| **Get category** `maintainx_get_category` | Retrieve detailed information about a specific category by its ID |
| **Get location** `maintainx_get_location` | Retrieve detailed information about a specific location by its ID |
| **Get user** `maintainx_get_user` | Retrieve detailed information about a specific user by their ID |
| **Get vendor** `maintainx_get_vendor` | Retrieve detailed information about a specific vendor by its ID |
| **Get workorders costs** `maintainx_get_workorders_costs` | Retrieve costs information for a specific work order by its ID |
| **List asset criticalities** `maintainx_list_asset_criticalities` | Retrieve a list of asset criticalities from MaintainX |
| **List assets** `maintainx_list_assets` | Allows users to retrieve a list of all assets in their organization |
| **List categories** `maintainx_list_categories` | Retrieves a list of all categories in your MaintainX organization |
| **List locations** `maintainx_list_locations` | Retrieves a list of all available locations in the organization's MaintainX account |
| **List meters** `maintainx_list_meters` | List all meters in your organization |
| **List parts** `maintainx_list_parts` | List parts/inventory items with pagination and filtering |
| **List procedure templates** `maintainx_list_procedure_templates` | List procedure templates from MaintainX |
| **List teams** `maintainx_list_teams` | Retrieves a list of all teams in your MaintainX organization |
| **List work orders** `maintainx_list_work_orders` | List work orders from MaintainX |
| **List work request portals** `maintainx_list_work_request_portals` | List all work request portals in your MaintainX organization |
| **List work requests** `maintainx_list_work_requests` | Retrieve a list of work requests from MaintainX |
| **Create category** `maintainx_create_category` | Create a new category in MaintainX for organizing work orders, assets, and other items |
| **Create location** `maintainx_create_location` | Create a new location in MaintainX |
| **Create procedure template** `maintainx_create_procedure_template` | Create a new procedure template in MaintainX with checklist items for work orders |
| **Create work order** `maintainx_create_work_order` | Creates a new work order in MaintainX |
| **Create work order comment** `maintainx_create_work_order_comment` | Creates a new comment on an existing work order in MaintainX |
| **Create work request** `maintainx_create_work_request` | Create a new work request in MaintainX |
| **Create work request portal** `maintainx_create_work_request_portal` | Creates a new work request portal in MaintainX |
| **Update vendors attachment** `maintainx_update_vendors_attachment` | Update a vendor attachment in MaintainX |
| **Update work order** `maintainx_update_work_order` | Allows users to update an existing work order in MaintainX by modifying specific attributes |
| **Update work order status** `maintainx_update_work_order_status` | Allows users to update the status of a specific work order in MaintainX |
| **Update work request portal** `maintainx_update_work_request_portal` | Updates an existing work request portal in MaintainX |

## Example prompts

**Find Entity**

> Use Maintainx to find entity and walk me through the result in plain English.

**Get Category**

> Pull the relevant data from Maintainx, summarize it in plain English, and point out anything that needs attention.

**Get Location**

> Pull the relevant data from Maintainx, summarize it in plain English, and point out anything that needs attention.

**Get User**

> Pull the relevant data from Maintainx, 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Maintainx working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Maintainx API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Maintainx 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 Maintainx. | 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 Maintainx actions to the runtime in a format your agent can reliably use. | 30 tools for Maintainx are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Maintainx 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 Hermes Agent users instead. You install the plugin once, connect Maintainx in the browser, and the 30 tools above work from chat. There is no SDK and no config file, and the Maintainx 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.

### Hermes paired but still can't use Maintainx
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

### Connection succeeds but no tools appear
Reconnect Maintainx 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 Maintainx tools
Maintainx 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 Maintainx 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.

### Maintainx 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 Maintainx has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a Hermes Agent Maintainx integration?
Yes. ClawLink is the fastest way to connect Hermes to Maintainx: link your Maintainx account once in the browser and Hermes Agent can call the Maintainx API through 30 ready-made tools — no custom code or token handling.

### How do I connect Maintainx to Hermes with ClawLink?
Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Maintainx in the dashboard and Hermes can use it from the next message — no config files, and the Maintainx key you paste is stored server-side instead of in your environment.

### How long does it take to connect Maintainx to Hermes Agent?
About two minutes. Sign in, click Connect next to Maintainx in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Maintainx up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Maintainx working from chat.

### Hermes paired but still can't use Maintainx
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

## Related

- [Hermes Trello integration](https://claw-link.dev/hermes/trello) — Manage boards, lists, and cards
- [Connect Moco](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions.
- [Connect ClickUp](https://claw-link.dev/hermes/clickup) — Manage tasks, docs, goals, and sprints
