# How to connect MX Technologies to Hermes Agent (paste one key, 36 tools) > Connect MX Technologies to Hermes with ClawLink: paste your MX Technologies key once and 36 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/mx-technologies Most guides for giving Hermes Agent MX Technologies 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 MX Technologies setup: pair once in the browser and your always-on Hermes agent can act on MX Technologies 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 MX Technologies. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect MX Technologies** — 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 mx-technologies # connect MX Technologies (browser OAuth) npx -y @useclawlink/cli actions mx-technologies # list available actions npx -y @useclawlink/cli run mx-technologies --input '' # 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 MX Technologies in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your MX Technologies account details once. Verify the connection by asking Hermes: > Create it in MX Technologies for me, then confirm the important fields before you finish. ### 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 MX Technologies is connected in the dashboard, that agent calls the same 36 MX Technologies 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). ## MX Technologies MCP for Hermes Looking for a MX Technologies MCP server for Hermes Agent? ClawLink connects MX Technologies to Hermes Agent and exposes 36 MX Technologies 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 MX Technologies integration](https://claw-link.dev/openclaw/mx-technologies) works the same way. ## What the Hermes Agent MX Technologies integration can do 36 MX Technologies tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 36. ### 30 of 36 MX Technologies tools for Hermes | Tool | What it does | |---|---| | **Create audience API credentials** `mx_technologies_create_audience_api_credentials` | Retrieve Audience API credentials | | **List account numbers by member** `mx_technologies_list_account_numbers_by_member` | List account numbers for a specific member | | **List account owners** `mx_technologies_list_account_owners` | List account owners for a specific member | | **List accounts** `mx_technologies_list_accounts` | List all accounts for a user | | **List budgets** `mx_technologies_list_budgets` | List all budgets for a specific MX user | | **List categories** `mx_technologies_list_categories` | List all categories for a user | | **List challenges** `mx_technologies_list_challenges` | List MFA challenges for a member | | **List favorite institutions** `mx_technologies_list_favorite_institutions` | List the partner's favorite financial institutions, sorted by popularity | | **List goals** `mx_technologies_list_goals` | List all financial goals for a specific MX user | | **List institution credentials** `mx_technologies_list_institution_credentials` | List credential fields required by a given institution | | **List institutions** `mx_technologies_list_institutions` | List financial institutions supported by MX | | **List member accounts** `mx_technologies_list_member_accounts` | List accounts for a specific member | | **List members** `mx_technologies_list_members` | List all members (financial institution connections) for a specific user | | **List rewards** `mx_technologies_list_rewards` | Lists rewards and loyalty program data for a specific member | | **List statements by member** `mx_technologies_list_statements_by_member` | Retrieve a paginated list of monthly account statements (PDF) for a specific member | | **List taggings** `mx_technologies_list_taggings` | List all taggings for a specific MX user | | **List tags** `mx_technologies_list_tags` | List all custom tags associated with a specific MX user | | **List transactions** `mx_technologies_list_transactions` | Retrieve all financial transactions for an MX user across all their connected accounts and | | **List transactions by member** `mx_technologies_list_transactions_by_member` | List transactions for a member | | **List users** `mx_technologies_list_users` | List all users in the MX Platform | | **Read account** `mx_technologies_read_account` | Retrieve details for a specific account | | **Read category** `mx_technologies_read_category` | Retrieve a default category by GUID | | **Read fdx account** `mx_technologies_read_fdx_account` | Retrieve details for a specific account using the FDX 4.6 standard API | | **Read institution** `mx_technologies_read_institution` | Retrieve details for a specific institution by code | | **Read transaction** `mx_technologies_read_transaction` | Retrieve details for a specific transaction by its GUID | | **Read transaction by account** `mx_technologies_read_transaction_by_account` | Retrieve details for a specific transaction by account | | **Read transaction rule** `mx_technologies_read_transaction_rule` | Retrieve details for a specific transaction rule by its GUID | | **Create account** `mx_technologies_create_account` | Creates a manual account for a specified user in MX Platform | | **Create member** `mx_technologies_create_member` | Create a member to connect a user to a financial institution | | **Create partner account** `mx_technologies_create_partner_account` | Create a new user (partner account) in the MX Platform | ## Example prompts **Create Audience Api Credentials** > Create it in MX Technologies for me, then confirm the important fields before you finish. **List Account Numbers By Member** > List the relevant items in MX Technologies, group them by priority, and recommend what Hermes should do next. **List Account Owners** > List the relevant items in MX Technologies, group them by priority, and recommend what Hermes should do next. **List Accounts** > List the relevant items in MX Technologies, group them by priority, and recommend what Hermes should do next. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual credential 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 MX Technologies working from chat. | | Manual | ClawLink | |---|---|---| | **Setup flow** | Collect and store the right MX Technologies credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link MX Technologies without custom integration screens. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for MX Technologies. | 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 MX Technologies actions to the runtime in a format your agent can reliably use. | 36 tools for MX Technologies are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes MX Technologies 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 MX Technologies in the browser, and the 36 tools above work from chat. There is no SDK and no config file, and the MX Technologies 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 MX Technologies 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 MX Technologies 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 MX Technologies tools MX Technologies 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 MX Technologies 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. ### MX Technologies 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. ### The setup form accepts credentials but calls still fail Re-enter the credentials carefully and verify the account-level permissions for MX Technologies. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles. ### Is there a Hermes Agent MX Technologies integration? Yes. ClawLink is the fastest way to connect Hermes to MX Technologies: link your MX Technologies account once in the browser and Hermes Agent can call the MX Technologies API through 36 ready-made tools — no custom code or token handling. ### How do I connect MX Technologies 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 MX Technologies in the dashboard and Hermes can use it from the next message — no config files, and the MX Technologies key you paste is stored server-side instead of in your environment. ### How long does it take to connect MX Technologies to Hermes Agent? About two minutes. Sign in, click Connect next to MX Technologies in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring MX Technologies up myself? The alternative to ClawLink is usually manual credential 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 MX Technologies working from chat. ### Hermes paired but still can't use MX Technologies 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 - [PostHog](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags - [Hermes DataforSEO integration](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Connect Metabase](https://claw-link.dev/hermes/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.