# How to connect Modem to OpenClaw (paste one key, 30 tools) > Connect Modem to OpenClaw with ClawLink: paste your Modem key once and 30 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/modem The usual route to Modem 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 Modem setup: install one ClawHub skill, connect Modem in the browser, and OpenClaw can call real Modem 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 Modem. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Modem** — 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 modem # connect Modem (browser OAuth) npx -y @useclawlink/cli actions modem # list available actions npx -y @useclawlink/cli run modem --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 Modem in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Modem API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Modem, 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 Modem is connected in the dashboard, that agent calls the same 30 Modem 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). ## Modem MCP for OpenClaw Looking for a Modem MCP server for OpenClaw? ClawLink connects Modem to OpenClaw and exposes 30 Modem 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 Modem integration](https://claw-link.dev/hermes/modem) works the same way. ## What the OpenClaw Modem integration can do 30 Modem tools are ready for OpenClaw once the account is connected. ### All 30 Modem tools for OpenClaw | Tool | What it does | |---|---| | **Get channel** `modem_get_channel` | Get one channel's source details, connection state, context, timestamps, and message count by | | **Get company** `modem_get_company` | Get one company's core details, connection values, domain, logo, and VIP status by decimal ID | | **Get company activity** `modem_get_company_activity` | Get one company's message count, weekly activity series, and source-level message breakdown | | **Get company history** `modem_get_company_history` | Get up to 50 company audit records plus merge history | | **Get company identities** `modem_get_company_identities` | Get external platform identities linked to one company by Modem's identify operation | | **Get current organization** `modem_get_current_organization` | Return the organization selected by the connected API key | | **Get person** `modem_get_person` | Get one person's complete profile, including company, connections, tags, sources, timestamps | | **Get person history** `modem_get_person_history` | Get up to 50 person audit records plus merge history | | **Get person identities** `modem_get_person_identities` | Get all external platform identities linked to one person | | **Get person source stats** `modem_get_person_source_stats` | Get one person's message counts broken down by source platform | | **Get topic** `modem_get_topic` | Get one topic's complete details, including its summary, classification, lifecycle, priority | | **Get topic groups** `modem_get_topic_groups` | Get every message group assigned to one topic in ascending or descending group-time order | | **Get topic history** `modem_get_topic_history` | Get up to 50 topic audit records plus action and merge history | | **Get topic people** `modem_get_topic_people` | Get every unique person who participated in one topic, including source identities, company | | **List channels** `modem_list_channels` | List organization channels with connection state and message counts, optionally filtered by | | **List companies** `modem_list_companies` | List companies with person and message aggregates, optionally searching and sorting the result | | **List groups** `modem_list_groups` | List message groups for exactly one company or one person, returning compact message content | | **List people** `modem_list_people` | List people with aggregated message statistics, optionally filtering by search text, ecosystem | | **List topics** `modem_list_topics` | List or search topics by keywords or semantic meaning with organization, participant, source | | **Add people to company** `modem_add_people_to_company` | Associate one or more existing people with an existing company | | **Create companies** `modem_create_companies` | Create one to 50 companies in one batch | | **Create people** `modem_create_people` | Create one to 50 people in one batch | | **Identify external records** `modem_identify_external_records` | Upsert links from external platform records to Modem people and companies in batches of 50 | | **Update companies** `modem_update_companies` | Update one to 50 companies in one batch | | **Update people** `modem_update_people` | Update one to 50 people in one batch | | **Update topic** `modem_update_topic` | Update one topic's priority, lifecycle, issue type, complete keyword list, or archive state | | **Update topics** `modem_update_topics` | Set priority or archive state for one to 100 topics at once | | **Merge companies** `modem_merge_companies` | Irreversibly merge one or more source companies into one surviving target | | **Merge people** `modem_merge_people` | Irreversibly merge one or more source people into one surviving target | | **Merge topics** `modem_merge_topics` | Irreversibly merge 1 to 50 source topics into one surviving target | ## Example prompts **Get Channel** > Pull the relevant data from Modem, summarize it in plain English, and point out anything that needs attention. **Get Company** > Pull the relevant data from Modem, summarize it in plain English, and point out anything that needs attention. **Get Company Activity** > Pull the relevant data from Modem, summarize it in plain English, and point out anything that needs attention. **Get Company History** > Pull the relevant data from Modem, 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 Modem working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Modem API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Modem 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 Modem. | 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 Modem actions to the runtime in a format your agent can reliably use. | 30 tools for Modem are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Modem 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 Modem in the browser, and the 30 tools above work from chat. There is no SDK and no config file, and the Modem 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 Modem skill but can't call the tools The ClawHub skill teaches OpenClaw about Modem, but the calls run through the ClawLink plugin and your connected account. Make sure Modem 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 Modem 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 Modem tools Modem 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 Modem 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. ### Modem 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 Modem has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Modem integration? Yes. ClawLink is the fastest way to connect OpenClaw to Modem: link your Modem account once in the browser and OpenClaw can call the Modem API through 30 ready-made tools — no custom code or token handling. ### How do I add Modem to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Modem skill from ClawHub, then you click Connect in the dashboard to authorize Modem. OpenClaw calls the tools from the next message — no config files, and the Modem key you paste is stored server-side instead of in your environment. ### How long does it take to connect Modem to OpenClaw? About two minutes. Sign in, click Connect next to Modem in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Modem 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 Modem working from chat. ### OpenClaw installed the Modem skill but can't call the tools The ClawHub skill teaches OpenClaw about Modem, but the calls run through the ClawLink plugin and your connected account. Make sure Modem 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 - [DataforSEO tools](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase](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.