How to connect TextRazor to OpenClaw
Connect TextRazor to OpenClaw with ClawLink: paste your TextRazor key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine.
TextRazorAPI KEYMCPTextRazor is a natural language processing API that extracts meaning, entities, and relationships from text, powering advanced content analysis and sentiment detection.. Once connected, OpenClaw can read and act on TextRazor from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to TextRazor 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 TextRazor setup: install one ClawHub skill, connect TextRazor in the browser, and OpenClaw can call real TextRazor 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 TextRazor.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect TextRazor
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with TextRazor?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 TextRazor in the ClawLink dashboard — paste your TextRazor API key once.
Verify the connection by asking OpenClaw:
Use TextRazor to account info 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once TextRazor is connected in the dashboard, that agent calls the same 6 TextRazor tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
TextRazor MCP for OpenClaw
Looking for a TextRazor MCP server for OpenClaw? ClawLink connects TextRazor to OpenClaw and exposes 6 TextRazor tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes TextRazor integration works the same way.
What the OpenClaw TextRazor integration can do
6 TextRazor tools are ready for OpenClaw once the account is connected.
All 6 TextRazor tools for OpenClaw
| Tool | What it does |
|---|---|
Account info textrazor_account_info | Retrieves comprehensive information about a TextRazor account, providing essential details |
Classify text textrazor_classify_text | Will classify text into predefined categories using TextRazor's classification capabilities |
Extract entities textrazor_extract_entities | Extract named entities (people, places, companies, etc.) from text using TextRazor's entity |
Text razor analyze content textrazor_text_razor_analyze_content | A comprehensive content analysis tool that combines multiple TextRazor extractors to perform a |
Custom classifier manager textrazor_custom_classifier_manager | Manages custom classifiers in TextRazor, allowing users to create, update, and manage custom |
Dictionary manager textrazor_dictionary_manager | Manage custom entity dictionaries in TextRazor for enhanced named entity recognition |
Try it: find the TextRazor tool you need
Browse the 6 TextRazor tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use TextRazor to account info and walk me through the result in plain English.
Use TextRazor to classify text and walk me through the result in plain English.
Use TextRazor to extract entities and walk me through the result in plain English.
Use TextRazor to text razor analyze content 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 TextRazor working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the TextRazor API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected TextRazor 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 TextRazor. | 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 TextRazor actions to the runtime in a format your agent can reliably use. | 6 tools for TextRazor are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes TextRazor 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 TextRazor in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the TextRazor key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the TextRazor skill but can't call the tools
The ClawHub skill teaches OpenClaw about TextRazor, but the calls run through the ClawLink plugin and your connected account. Make sure TextRazor 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 TextRazor 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 TextRazor tools
TextRazor 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 TextRazor 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.
TextRazor 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 TextRazor has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw TextRazor integration?
Yes. ClawLink is the fastest way to connect OpenClaw to TextRazor: link your TextRazor account once in the browser and OpenClaw can call the TextRazor API through 6 ready-made tools — no custom code or token handling.
How do I add TextRazor to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink TextRazor skill from ClawHub, then you click Connect in the dashboard to authorize TextRazor. OpenClaw calls the tools from the next message — no config files, and the TextRazor key you paste is stored server-side instead of in your environment.
How long does it take to connect TextRazor to OpenClaw?
About two minutes. Sign in, click Connect next to TextRazor in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring TextRazor 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 TextRazor working from chat.
OpenClaw installed the TextRazor skill but can't call the tools
The ClawHub skill teaches OpenClaw about TextRazor, but the calls run through the ClawLink plugin and your connected account. Make sure TextRazor 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
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
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
OpenClaw Just One API integration
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.