# How to connect Msg91 to OpenClaw (paste one key, 8 tools) > Connect Msg91 to OpenClaw with ClawLink: paste your Msg91 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/msg91 The usual route to Msg91 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 Msg91 setup: install one ClawHub skill, connect Msg91 in the browser, and OpenClaw can call real Msg91 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 Msg91. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Msg91** — 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 msg91 # connect Msg91 (browser OAuth) npx -y @useclawlink/cli actions msg91 # list available actions npx -y @useclawlink/cli run msg91 --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 Msg91 in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Msg91 API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Msg91, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Msg91 is connected in the dashboard, that agent calls the same 8 Msg91 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). ## Msg91 MCP for OpenClaw Looking for a Msg91 MCP server for OpenClaw? ClawLink connects Msg91 to OpenClaw and exposes 8 Msg91 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 Msg91 integration](https://claw-link.dev/hermes/msg91) works the same way. ## What the OpenClaw Msg91 integration can do 8 Msg91 tools are ready for OpenClaw once the account is connected. ### All 8 Msg91 tools for OpenClaw | Tool | What it does | |---|---| | **Get event types** `msg91_get_event_types` | Retrieves all event types configured in MSG91 Segmento | | **Get failed events** `msg91_get_failed_events` | Retrieve failed user events from a MSG91 Segmento campaign | | **List campaigns** `msg91_list_campaigns` | List all campaigns in Segmento | | **Create user events** `msg91_create_user_events` | Create and track user events in MSG91 Segmento for customer behavior analysis and segmentation | | **Resend otp** `msg91_resend_otp` | Resend OTP to the same mobile number via text message or voice call | | **Send otp** `msg91_send_otp` | Send OTP (One-Time Password) to a mobile number using a pre-configured MSG91 template | | **Send sms v5** `msg91_send_sms_v5` | Send SMS messages using pre-defined templates via MSG91 Flow API v5 | | **Verify otp** `msg91_verify_otp` | Verify an OTP (One-Time Password) sent to a mobile number | ## Example prompts **Get Event Types** > Pull the relevant data from Msg91, summarize it in plain English, and point out anything that needs attention. **Get Failed Events** > Pull the relevant data from Msg91, summarize it in plain English, and point out anything that needs attention. **List Campaigns** > List the relevant items in Msg91, group them by priority, and recommend what OpenClaw should do next. **Create User Events** > Create it in Msg91 for me, then confirm the important fields before you finish. ## 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 Msg91 working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Msg91 API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Msg91 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 Msg91. | 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 Msg91 actions to the runtime in a format your agent can reliably use. | 8 tools for Msg91 are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Msg91 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 Msg91 in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Msg91 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 Msg91 skill but can't call the tools The ClawHub skill teaches OpenClaw about Msg91, but the calls run through the ClawLink plugin and your connected account. Make sure Msg91 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 Msg91 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 Msg91 tools Msg91 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 Msg91 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. ### Msg91 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 Msg91 has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Msg91 integration? Yes. ClawLink is the fastest way to connect OpenClaw to Msg91: link your Msg91 account once in the browser and OpenClaw can call the Msg91 API through 8 ready-made tools — no custom code or token handling. ### How do I add Msg91 to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Msg91 skill from ClawHub, then you click Connect in the dashboard to authorize Msg91. OpenClaw calls the tools from the next message — no config files, and the Msg91 key you paste is stored server-side instead of in your environment. ### How long does it take to connect Msg91 to OpenClaw? About two minutes. Sign in, click Connect next to Msg91 in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Msg91 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 Msg91 working from chat. ### OpenClaw installed the Msg91 skill but can't call the tools The ClawHub skill teaches OpenClaw about Msg91, but the calls run through the ClawLink plugin and your connected account. Make sure Msg91 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 - [SendGrid](https://claw-link.dev/openclaw/sendgrid) — Deliver transactional and marketing emails - [Dialpad](https://claw-link.dev/openclaw/dialpad) — Business phone, messaging, and video conferencing - [Discord Bot](https://claw-link.dev/openclaw/discord-bot) — Automate Discord server actions with bot-specific permissions