# How to connect LMNT to OpenClaw (paste one key, 8 tools) > Connect LMNT to OpenClaw with ClawLink: paste your LMNT key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/lmnt The usual route to LMNT 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 LMNT setup: install one ClawHub skill, connect LMNT in the browser, and OpenClaw can call real LMNT 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/lmnt ## Setup It takes three steps to connect OpenClaw to LMNT. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect LMNT** — 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 lmnt # connect LMNT (browser OAuth) npx -y @useclawlink/cli actions lmnt # list available actions npx -y @useclawlink/cli run lmnt --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 LMNT in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your LMNT API key once. Verify the connection by asking OpenClaw: > Create it in LMNT 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 LMNT is connected in the dashboard, that agent calls the same 8 LMNT 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). ## LMNT MCP for OpenClaw Looking for a LMNT MCP server for OpenClaw? ClawLink connects LMNT to OpenClaw and exposes 8 LMNT 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 LMNT integration](https://claw-link.dev/hermes/lmnt) works the same way. ## What the OpenClaw LMNT integration can do 8 LMNT tools are ready for OpenClaw once the account is connected. The 7 below are the ones people reach for most; your agent can call all 8. ### 7 of 8 LMNT tools for OpenClaw | Tool | What it does | |---|---| | **Create voice** `lmnt_create_voice` | Creates a custom voice in LMNT by training on uploaded audio samples. The voice can then be used for text-to-speech synthesis. Returns the voice ID and metadata upon successful creation. | | **Generate speech with metadata** `lmnt_generate_speech_with_metadata` | Generates speech from text and returns JSON with base64-encoded audio and optional word-level timing metadata. Use when you need the synthesis seed or word timestamps for subtitle synchronization. | | **Get account** `lmnt_get_account` | Retrieves account information including subscription plan details and current usage statistics. | | **Get voice info** `lmnt_get_voice_info` | Gets metadata for a specific LMNT voice, including active status, supported languages, and plan availability. Useful for validating a voice ID before using it in synthesis requests. | | **Get voices list** `lmnt_get_voices_list` | Retrieves a list of available voices from LMNT. Returns both system-provided preset voices and any custom voices you have created. | | **Synthesize speech** `lmnt_synthesize_speech` | Synthesizes speech from text using LMNT's AI voices. Converts text (up to 5000 characters) into natural-sounding speech audio using a specified voice. | | **Update voice** `lmnt_update_voice` | Updates information about a specific voice in LMNT. You can update the name, description, gender, starred status, and unfreeze state of a voice. | ## Example prompts **Create Voice** > Create it in LMNT for me, then confirm the important fields before you finish. **Generate Speech With Metadata** > Use LMNT to generate speech with metadata and walk me through the result in plain English. **Get Account** > Pull the relevant data from LMNT, summarize it in plain English, and point out anything that needs attention. **Get Voice Info** > Pull the relevant data from LMNT, 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 LMNT working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the LMNT API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected LMNT 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 LMNT. | 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 LMNT actions to the runtime in a format your agent can reliably use. | 8 tools for LMNT are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes LMNT 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 LMNT in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the LMNT 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 LMNT skill but can't call the tools The ClawHub skill teaches OpenClaw about LMNT, but the calls run through the ClawLink plugin and your connected account. Make sure LMNT 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 LMNT 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 LMNT tools LMNT 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 LMNT 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. ### LMNT 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 LMNT has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw LMNT integration? Yes. ClawLink is the fastest way to connect OpenClaw to LMNT: link your LMNT account once in the browser and OpenClaw can call the LMNT API through 8 ready-made tools — no custom code or token handling. ### How do I add LMNT to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink LMNT skill from ClawHub, then you click Connect in the dashboard to authorize LMNT. OpenClaw calls the tools from the next message — no config files, and the LMNT key you paste is stored server-side instead of in your environment. ### How long does it take to connect LMNT to OpenClaw? About two minutes. Sign in, click Connect next to LMNT in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring LMNT 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 LMNT working from chat. ### OpenClaw installed the LMNT skill but can't call the tools The ClawHub skill teaches OpenClaw about LMNT, but the calls run through the ClawLink plugin and your connected account. Make sure LMNT 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 - [Connect DataRobot](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Connect Chatbotkit](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [ElevenLabs](https://claw-link.dev/openclaw/elevenlabs) — Generate speech and voice cloning