How to connect Stytch to OpenClaw
Connect Stytch to OpenClaw with ClawLink in one click — 21 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
StytchOAUTH2MCPStytch MCP lets authorized agents configure Stytch projects, redirect URLs, SDK settings, email templates, API keys, and other workspace-management resources.. Once connected, OpenClaw can read and act on Stytch from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Stytch 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 Stytch setup: install one ClawHub skill, connect Stytch in the browser, and OpenClaw can call real Stytch actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Stytch skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Stytch" (hith3sh/stytch-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/stytch-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Stytch.
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 Stytch
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Stytch?"
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 Stytch in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Use Stytch to mcp get all email templates 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 Stytch is connected in the dashboard, that agent calls the same 21 Stytch tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Stytch MCP for OpenClaw
Looking for a Stytch MCP server for OpenClaw? ClawLink connects Stytch to OpenClaw and exposes 21 Stytch tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Stytch integration works the same way.
What the OpenClaw Stytch integration can do
21 Stytch tools are ready for OpenClaw once the account is connected. The 17 below are the ones people reach for most; your agent can call all 21.
17 of 21 Stytch tools for OpenClaw
| Tool | What it does |
|---|---|
Mcp get all email templates stytch_mcp_get_all_email_templates | Retrieve all email templates for a project |
Mcp get all public tokens stytch_mcp_get_all_public_tokens | Retrieve all active public tokens for a project |
Mcp get all redirect ur ls stytch_mcp_get_all_redirect_ur_ls | Retrieve all redirect URLs for a project |
Mcp get b2 bsdk config stytch_mcp_get_b2_bsdk_config | Retrieves the SDK Configuration for a B2B project |
Mcp get consumer sdk config stytch_mcp_get_consumer_sdk_config | Retrieves the SDK Configuration for a Consumer project |
Mcp get password strength config stytch_mcp_get_password_strength_config | Retrieve the password strength configuration for a project |
Mcp list projects stytch_mcp_list_projects | List all Stytch Projects |
Mcp create email template stytch_mcp_create_email_template | Creates an custom email template for the project |
Mcp create project stytch_mcp_create_project | Create new Stytch Project |
Mcp create public token stytch_mcp_create_public_token | Creates a public token for a project |
Mcp create redirect URL stytch_mcp_create_redirect_url | Create a redirect URL for your project |
Mcp create secret stytch_mcp_create_secret | Create a new secret for a project |
Mcp set password strength config stytch_mcp_set_password_strength_config | Set the password strength configuration for a project |
Mcp update b2 bsdk config stytch_mcp_update_b2_bsdk_config | Updates the SDK Configuration for a B2B project |
Mcp update consumer sdk config stytch_mcp_update_consumer_sdk_config | Updates the SDK Configuration for a Consumer project |
Mcp update email template stytch_mcp_update_email_template | Update an email template for a project |
Mcp update redirect URL stytch_mcp_update_redirect_url | Update valid types for a redirect URL for a project |
Try it: find the Stytch tool you need
Browse the 17 Stytch tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Stytch to mcp get all email templates and walk me through the result in plain English.
Use Stytch to mcp get all public tokens and walk me through the result in plain English.
Use Stytch to mcp get all redirect ur ls and walk me through the result in plain English.
Use Stytch to mcp get b2 bsdk config 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 Stytch working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Stytch app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Stytch 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 Stytch. | 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 Stytch actions to the runtime in a format your agent can reliably use. | 21 tools for Stytch are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Stytch 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 Stytch in the browser, and the 21 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 comparison.
Troubleshooting
OpenClaw installed the Stytch skill but can't call the tools
The ClawHub skill teaches OpenClaw about Stytch, but the calls run through the ClawLink plugin and your connected account. Make sure Stytch 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 Stytch 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 Stytch tools
Stytch 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 Stytch 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.
Stytch 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 Stytch and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Stytch integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Stytch: link your Stytch account once in the browser and OpenClaw can call the Stytch API through 21 ready-made tools — no custom code or token handling.
How do I add Stytch to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Stytch skill from ClawHub, then you click Connect in the dashboard to authorize Stytch. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Stytch to OpenClaw?
About two minutes. Sign in, click Connect next to Stytch in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Stytch 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 Stytch working from chat.
OpenClaw installed the Stytch skill but can't call the tools
The ClawHub skill teaches OpenClaw about Stytch, but the calls run through the ClawLink plugin and your connected account. Make sure Stytch 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
GitHub
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture tools
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.