# How to connect Algolia to OpenClaw (paste one key, 127 tools) > Connect Algolia to OpenClaw with ClawLink: paste your Algolia key once and 127 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/algolia The usual route to Algolia 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 Algolia setup: install one ClawHub skill, connect Algolia in the browser, and OpenClaw can call real Algolia 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/algolia ## Setup It takes three steps to connect OpenClaw to Algolia. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Algolia** — 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 algolia # connect Algolia (browser OAuth) npx -y @useclawlink/cli actions algolia # list available actions npx -y @useclawlink/cli run algolia --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 Algolia in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Algolia API key once. Verify the connection by asking OpenClaw: > Use Algolia to add ab test and walk me through the result in plain English. ### 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 Algolia is connected in the dashboard, that agent calls the same 127 Algolia 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). ## Algolia MCP for OpenClaw Looking for a Algolia MCP server for OpenClaw? ClawLink connects Algolia to OpenClaw and exposes 127 Algolia 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 Algolia integration](https://claw-link.dev/hermes/algolia) works the same way. ## What the OpenClaw Algolia integration can do 127 Algolia 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 127. ### 30 of 127 Algolia tools for OpenClaw | Tool | What it does | |---|---| | **Add AB test** `algolia_add_ab_test` | Create an A/B test comparing search performance between two index variants | | **Add or replace record** `algolia_add_or_replace_record` | Add or replace a specific record in an index by objectID | | **Add record** `algolia_add_record` | Add a record to an index with auto-generated objectID | | **Browse index** `algolia_browse_index` | Retrieve all records from an index | | **Clear objects** `algolia_clear_objects` | Clear records of an index without affecting settings | | **Export rules** `algolia_export_rules` | Export all rules defined on an index | | **Find object** `algolia_find_object` | Find the first object matching a query or filter in an index | | **Get AB test** `algolia_get_ab_test` | Retrieve detailed information about an A/B test by its ID | | **Get add to cart rate** `algolia_get_add_to_cart_rate` | Retrieve add-to-cart rate metrics for e-commerce search analytics | | **Get API key** `algolia_get_api_key` | Retrieve the permissions and details of a specific API key | | **Get app task** `algolia_get_app_task` | Check the status of an application task | | **Get authentication** `algolia_get_authentication` | Retrieve an authentication resource by its ID | | **Get average click position** `algolia_get_average_click_position` | Retrieve average click position metrics from Algolia Analytics | | **Get click positions** `algolia_get_click_positions` | Retrieve the distribution of clicks by position from Algolia Analytics | | **Get click through rate** `algolia_get_click_through_rate` | Retrieve click-through rate (CTR) for searches with at least one click event | | **Get config** `algolia_get_config` | Retrieve a Query Suggestions configuration by index name | | **Get config2** `algolia_get_config2` | Retrieve the advanced personalization configuration | | **Get conversion rate** `algolia_get_conversion_rate` | Retrieve conversion rate for searches with conversion events | | **Get destination** `algolia_get_destination` | Retrieve a destination by its ID | | **Get dictionary languages** `algolia_get_dictionary_languages` | List available languages for dictionary entries | | **Get dictionary settings** `algolia_get_dictionary_settings` | Retrieve dictionary settings for all dictionaries | | **Get logs** `algolia_get_logs` | Retrieve log entries for API requests made to your Algolia application | | **Get no click rate** `algolia_get_no_click_rate` | Retrieve the rate of searches that received no clicks | | **Get no results rate** `algolia_get_no_results_rate` | Retrieve the fraction of searches that didn't return any results | | **Get no results searches** `algolia_get_no_results_searches` | Retrieve the most frequent searches that produced zero results | | **Get object position** `algolia_get_object_position` | Retrieve an object’s position in a result set | | **Get objects** `algolia_get_objects` | Retrieve multiple records from an index | | **Get purchase rate** `algolia_get_purchase_rate` | Retrieve purchase rate metrics for searches that led to purchase events | | **Get recommend rule** `algolia_get_recommend_rule` | Retrieve a Recommend rule that was previously created in the Algolia dashboard | | **Get recommend task status** `algolia_get_recommend_task_status` | Check the status of a Recommend task | ## Example prompts **Add Ab Test** > Use Algolia to add ab test and walk me through the result in plain English. **Add Or Replace Record** > Use Algolia to add or replace record and walk me through the result in plain English. **Add Record** > Use Algolia to add record and walk me through the result in plain English. **Browse Index** > Use Algolia to browse index and walk me through the result in plain English. ## 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 Algolia working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Algolia API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Algolia 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 Algolia. | 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 Algolia actions to the runtime in a format your agent can reliably use. | 127 tools for Algolia are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Algolia 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 Algolia in the browser, and the 127 tools above work from chat. There is no SDK and no config file, and the Algolia 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 Algolia skill but can't call the tools The ClawHub skill teaches OpenClaw about Algolia, but the calls run through the ClawLink plugin and your connected account. Make sure Algolia 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 Algolia 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 Algolia tools Algolia 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 Algolia 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. ### Algolia 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 Algolia has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Algolia integration? Yes. ClawLink is the fastest way to connect OpenClaw to Algolia: link your Algolia account once in the browser and OpenClaw can call the Algolia API through 127 ready-made tools — no custom code or token handling. ### How do I add Algolia to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Algolia skill from ClawHub, then you click Connect in the dashboard to authorize Algolia. OpenClaw calls the tools from the next message — no config files, and the Algolia key you paste is stored server-side instead of in your environment. ### How long does it take to connect Algolia to OpenClaw? About two minutes. Sign in, click Connect next to Algolia in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Algolia 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 Algolia working from chat. ### OpenClaw installed the Algolia skill but can't call the tools The ClawHub skill teaches OpenClaw about Algolia, but the calls run through the ClawLink plugin and your connected account. Make sure Algolia 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 - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.