How to connect Typecast to OpenClaw
Connect Typecast to OpenClaw with ClawLink: paste your Typecast key once and 7 tools work from chat. No MCP server to run, nothing stored on your machine.
TypecastAPI KEYMCPTypecast is an AI voice platform for generating expressive speech, discovering voices, and managing custom voices.. Once connected, OpenClaw can read and act on Typecast from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Typecast 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 Typecast setup: install one ClawHub skill, connect Typecast in the browser, and OpenClaw can call real Typecast 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 Typecast.
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 Typecast
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Typecast?"
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 Typecast in the ClawLink dashboard — paste your Typecast API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Typecast, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Typecast is connected in the dashboard, that agent calls the same 7 Typecast tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Typecast MCP for OpenClaw
Looking for a Typecast MCP server for OpenClaw? ClawLink connects Typecast to OpenClaw and exposes 7 Typecast tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Typecast integration works the same way.
What the OpenClaw Typecast integration can do
7 Typecast tools are ready for OpenClaw once the account is connected.
All 7 Typecast tools for OpenClaw
| Tool | What it does |
|---|---|
Get subscription typecast_get_subscription | Get the connected Typecast API plan, credit usage, concurrency limit, and custom-voice allowance |
Get voice typecast_get_voice | Get one voice's metadata, supported models, and available emotions by voice ID |
List voices typecast_list_voices | List available built-in and owned custom Typecast voices, optionally filtered by speech model |
Recommend voices typecast_recommend_voices | Find and rank Typecast voices that match a natural-language description |
Compose speech typecast_compose_speech | Generate one audio file from an ordered sequence of speech and pause segments |
Generate speech typecast_generate_speech | Generate a complete WAV or MP3 audio file from text using a Typecast voice |
Generate speech with timestamps typecast_generate_speech_with_timestamps | Generate speech plus word, character, or both alignment timestamp arrays |
Try it: find the Typecast tool you need
Browse the 7 Typecast tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Typecast, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Typecast, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Typecast, group them by priority, and recommend what OpenClaw should do next.
Use Typecast to recommend voices 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 Typecast working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Typecast API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Typecast 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 Typecast. | 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 Typecast actions to the runtime in a format your agent can reliably use. | 7 tools for Typecast are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Typecast 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 Typecast in the browser, and the 7 tools above work from chat. There is no SDK and no config file, and the Typecast 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 Typecast skill but can't call the tools
The ClawHub skill teaches OpenClaw about Typecast, but the calls run through the ClawLink plugin and your connected account. Make sure Typecast 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 Typecast 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 Typecast tools
Typecast 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 Typecast 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.
Typecast 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 Typecast 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 Typecast integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Typecast: link your Typecast account once in the browser and OpenClaw can call the Typecast API through 7 ready-made tools — no custom code or token handling.
How do I add Typecast to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Typecast skill from ClawHub, then you click Connect in the dashboard to authorize Typecast. OpenClaw calls the tools from the next message — no config files, and the Typecast key you paste is stored server-side instead of in your environment.
How long does it take to connect Typecast to OpenClaw?
About two minutes. Sign in, click Connect next to Typecast in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Typecast 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 Typecast working from chat.
OpenClaw installed the Typecast skill but can't call the tools
The ClawHub skill teaches OpenClaw about Typecast, but the calls run through the ClawLink plugin and your connected account. Make sure Typecast 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.
OpenClaw Chatbotkit integration
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.