# How to connect Peec AI to OpenClaw (no API keys) > Connect Peec AI to OpenClaw with ClawLink in one click — 84 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/openclaw/peec-ai The usual route to Peec AI 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 Peec AI setup: install one ClawHub skill, connect Peec AI in the browser, and OpenClaw can call real Peec AI 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 Peec AI. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Peec AI** — 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 peec-ai # connect Peec AI (browser OAuth) npx -y @useclawlink/cli actions peec-ai # list available actions npx -y @useclawlink/cli run peec-ai --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 Peec AI in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking OpenClaw: > Use Peec AI to mcp get actions 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 Peec AI is connected in the dashboard, that agent calls the same 84 Peec AI 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). ## Peec AI MCP for OpenClaw Looking for a Peec AI MCP server for OpenClaw? ClawLink connects Peec AI to OpenClaw and exposes 84 Peec AI 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 Peec AI integration](https://claw-link.dev/hermes/peec-ai) works the same way. ## What the OpenClaw Peec AI integration can do 84 Peec AI 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 84. ### 30 of 84 Peec AI tools for OpenClaw | Tool | What it does | |---|---| | **Mcp get actions** `peec_ai_mcp_get_actions` | Get Peec's opportunity-scored action recommendations for improving brand visibility in AI | | **Mcp get agent visits** `peec_ai_mcp_get_agent_visits` | Aggregate AI agent visit counts from access logs over a date range | | **Mcp get brand perception attribute rankings** `peec_ai_mcp_get_brand_perception_attribute_rankings` | How the project's own brand ranks against competitors for each brand-perception attribute | | **Mcp get brand perception attribute sources** `peec_ai_mcp_get_brand_perception_attribute_sources` | The sources feeding one brand-perception attribute: the URLs AI answers cited when describing | | **Mcp get brand perception brand attributes** `peec_ai_mcp_get_brand_perception_brand_attributes` | How AI models describe the project's own brand: attribute clusters (e.g | | **Mcp get brand perception competitive breakdown** `peec_ai_mcp_get_brand_perception_competitive_breakdown` | The full competitive breakdown matrix: for every brand-perception attribute, the average | | **Mcp get brand perception objection sources** `peec_ai_mcp_get_brand_perception_objection_sources` | The sources AI models retrieved when asked about one objection | | **Mcp get brand perception objections** `peec_ai_mcp_get_brand_perception_objections` | The recurring arguments AI models make against the project's brand when a buyer is deciding | | **Mcp get brand report** `peec_ai_mcp_get_brand_report` | Get a report on brand visibility, sentiment, and position across AI search engines | | **Mcp get chat** `peec_ai_mcp_get_chat` | Get the full content of a single chat (one AI engine's response to one prompt on one date) | | **Mcp get chats report** `peec_ai_mcp_get_chats_report` | Aggregate counts and rich-answer-feature shares over a project's chats for a date range | | **Mcp get domain report** `peec_ai_mcp_get_domain_report` | Get a report on source domain visibility and citations across AI search engines | | **Mcp get product** `peec_ai_mcp_get_product` | Get one product's detailed metrics over a date range — the drill-down companion to | | **Mcp get project profile** `peec_ai_mcp_get_project_profile` | Read a project's brand profile — the description, industry, brand-identity adjectives, target | | **Mcp get prompt suggestion generation** `peec_ai_mcp_get_prompt_suggestion_generation` | Read the authoritative status of a run returned by generate_prompt_suggestions | | **Mcp get shopping attributes** `peec_ai_mcp_get_shopping_attributes` | Compare the qualitative characteristics and features that AI engines associate with a product | | **Mcp get shopping summary** `peec_ai_mcp_get_shopping_summary` | Return catalog-wide shopping metrics over a date range — avg_visibility, avg_win_rate, and | | **Mcp get shopping trend** `peec_ai_mcp_get_shopping_trend` | Return a per-bucket shopping time series (visibility, win_rate, avg_position, sov) for specific | | **Mcp get URL content** `peec_ai_mcp_get_url_content` | Fetches and returns the content of a URL for downstream analysis — the markdown Peec extracted | | **Mcp get URL report** `peec_ai_mcp_get_url_report` | Get a report on source URL visibility and citations across AI search engines | | **Mcp list bots** `peec_ai_mcp_list_bots` | List all known AI crawler/agent bots that visit the site (e.g | | **Mcp list brand perception attribute clusters** `peec_ai_mcp_list_brand_perception_attribute_clusters` | The editable attribute taxonomy behind brand perception: every cluster with its id, label and | | **Mcp list brand social channels** `peec_ai_mcp_list_brand_social_channels` | List the social channels configured for a project's own brand and competitors | | **Mcp list brands** `peec_ai_mcp_list_brands` | List brands tracked in a project — includes the user's own brand and competitors | | **Mcp list categories** `peec_ai_mcp_list_categories` | List a project's product categories | | **Mcp list chats** `peec_ai_mcp_list_chats` | List chats (individual AI responses) for a project over a date range | | **Mcp list domain classifications** `peec_ai_mcp_list_domain_classifications` | List the custom domain classifications defined for a project | | **Mcp list global brands** `peec_ai_mcp_list_global_brands` | Search Peec's global brand catalog — the shared registry of real-world brands (e.g | | **Mcp list merchants** `peec_ai_mcp_list_merchants` | List the merchants (sellers, e.g | | **Mcp list model channels** `peec_ai_mcp_list_model_channels` | List the AI engine channels tracked by Peec | ## Example prompts **Mcp Get Actions** > Use Peec AI to mcp get actions and walk me through the result in plain English. **Mcp Get Agent Visits** > Use Peec AI to mcp get agent visits and walk me through the result in plain English. **Mcp Get Brand Perception Attribute Rankings** > Use Peec AI to mcp get brand perception attribute rankings and walk me through the result in plain English. **Mcp Get Brand Perception Attribute Sources** > Use Peec AI to mcp get brand perception attribute sources and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app 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 Peec AI working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Peec AI app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Peec AI through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Peec AI. | 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 Peec AI actions to the runtime in a format your agent can reliably use. | 84 tools for Peec AI are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Peec AI 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 Peec AI in the browser, and the 84 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Peec AI skill but can't call the tools The ClawHub skill teaches OpenClaw about Peec AI, but the calls run through the ClawLink plugin and your connected account. Make sure Peec AI 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 Peec AI 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 Peec AI tools Peec AI 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 Peec AI 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. ### Peec AI 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. ### OAuth finished in the browser but the account is still missing Try reconnecting Peec AI and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a OpenClaw Peec AI integration? Yes. ClawLink is the fastest way to connect OpenClaw to Peec AI: link your Peec AI account once in the browser and OpenClaw can call the Peec AI API through 84 ready-made tools — no custom code or token handling. ### How do I add Peec AI to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Peec AI skill from ClawHub, then you click Connect in the dashboard to authorize Peec AI. OpenClaw calls the tools from the next message — no config files or API keys to manage. ### How long does it take to connect Peec AI to OpenClaw? About two minutes. Sign in, click Connect next to Peec AI in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Peec AI up myself? The alternative to ClawLink is usually manual OAuth app 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 Peec AI working from chat. ### OpenClaw installed the Peec AI skill but can't call the tools The ClawHub skill teaches OpenClaw about Peec AI, but the calls run through the ClawLink plugin and your connected account. Make sure Peec AI 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 PostHog integration](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [DataforSEO](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.