# How to connect MX Technologies to OpenClaw (paste one key, 36 tools) > Connect MX Technologies to OpenClaw 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/openclaw/mx-technologies The usual route to MX Technologies 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 MX Technologies setup: install one ClawHub skill, connect MX Technologies in the browser, and OpenClaw can call real MX Technologies 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 MX Technologies. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect MX Technologies** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **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 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 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 MX Technologies in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your MX Technologies account details once. Verify the connection by asking OpenClaw: > Create it in MX Technologies for me, then confirm the important fields before you finish. ### 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 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 OpenClaw Looking for a MX Technologies MCP server for OpenClaw? ClawLink connects MX Technologies to OpenClaw 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 Hermes instead? The [Hermes MX Technologies integration](https://claw-link.dev/hermes/mx-technologies) works the same way. ## What the OpenClaw MX Technologies integration can do 36 MX Technologies 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 36. ### 30 of 36 MX Technologies tools for OpenClaw | 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 OpenClaw should do next. **List Account Owners** > List the relevant items in MX Technologies, group them by priority, and recommend what OpenClaw should do next. **List Accounts** > List the relevant items in MX Technologies, group them by priority, and recommend what OpenClaw 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 OpenClaw. 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 OpenClaw 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. ### OpenClaw installed the MX Technologies skill but can't call the tools The ClawHub skill teaches OpenClaw about MX Technologies, but the calls run through the ClawLink plugin and your connected account. Make sure MX Technologies 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 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 OpenClaw MX Technologies integration? Yes. ClawLink is the fastest way to connect OpenClaw to MX Technologies: link your MX Technologies account once in the browser and OpenClaw can call the MX Technologies API through 36 ready-made tools — no custom code or token handling. ### How do I add MX Technologies to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink MX Technologies skill from ClawHub, then you click Connect in the dashboard to authorize MX Technologies. OpenClaw calls the tools 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 OpenClaw? About two minutes. Sign in, click Connect next to MX Technologies in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want MX Technologies working from chat. ### OpenClaw installed the MX Technologies skill but can't call the tools The ClawHub skill teaches OpenClaw about MX Technologies, but the calls run through the ClawLink plugin and your connected account. Make sure MX Technologies 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 - [PostHog tools](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [OpenClaw DataforSEO integration](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [OpenClaw Metabase integration](https://claw-link.dev/openclaw/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.