Stytch MCP connector
The Stytch connector lets Claude, ChatGPT, Cursor and the Elaichi Agent read and change your Stytch project settings and email templates, with every action running as the person who signed in and recorded in an audit log.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Stytch to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Stytch once
-
Open Connections, choose Add connection, and pick Stytch.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Stytch. Stytch's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
Google Workspace
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Stytch MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Stytch MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Stytch MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Stytch to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Stytch through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering
Check a project's settings before a release
Ask what a Stytch project is configured to do right now and get the current settings read back in plain language, without opening the dashboard.
-
Marketing
Refresh sign-in email templates
Update the wording and branding in Stytch email templates, such as the magic link or password reset email, and have the change land in the right project.
-
Security
Compare live and test project settings
Line up the settings of two Stytch projects and spot the differences before a change reaches customers.
-
Product
Draft a new onboarding email in Stytch
Describe the email a new user should receive and have the template written and saved in Stytch for review.
-
IT
Keep workspace configuration consistent
Ask across every Stytch project for a given setting and tidy up the ones that drifted.
-
Support
Confirm what a customer's sign-in email says
Pull up the exact Stytch email template a customer received so you can answer their question with the real text in front of you.
Try asking
- “Show me the email templates in our production Stytch project”
- “Compare settings between our test and live Stytch projects”
- “Update the password reset email template with the new wording”
Compare
Elaichi vs Zapier MCP vs Composio for Stytch
All three can connect Stytch to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Stytch tools | Allow or restrict single Stytch tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Stytch call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
See it in Elaichi
What connecting Stytch gets you
5 screens from the product, each doing one job for your Stytch account.
The agent
Ask about your Stytch projects in plain language.
Check project settings and email templates from live Stytch records, no console digging.
- projects
- email templates
- settings
- workspaces
Ask Elaichi to work across your apps.
Show me the email templates in our production Stytch project
Compare settings between our test and live Stytch projects
Update the password reset email template with the new wording
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Stytch to every AI client.
Claude, ChatGPT and Cursor reach Stytch through one org endpoint, no SDK, no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Stytch toolbox.
Security scopes project settings, Marketing scopes email templates, each team sees only its toolbox.
- Engineering
- Security
- Product
- Marketing
ElaichiToolboxesShared connections
Share a Stytch connection without sharing a credential.
One admin connects Stytch, teams work through it, and nobody else touches the sign-in.
- Production
- Staging
- Security
- Platform team
ElaichiConnectionsAudit log
Every Stytch change answers who did what.
When, who, what happened and which project or template, in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts Stytch work and finishes it.
Project settings are fetched, grouped and drafted into a digest, approved, then posted to Stytch.
Stytch digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch projects
Stytch
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Stytch
Queued
Collections and dashboards
Stytch health, computed on a schedule, no model.
Four metrics, 14 days of email templates created, and a breakdown by team, refreshed automatically.
Stytch health
Refreshed 4 minutes ago · every 15 minutes · from the projects collection
Projects
1,284 ↓ 12%
Email templates
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Projects created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Security 21%
Platform team 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Stytch to Claude?
Connect Stytch in Elaichi first, where you sign in to Stytch over OAuth in your browser; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on it works with Stytch as you.
Does Stytch work with ChatGPT and Cursor as well as Claude?
Yes. Once Stytch is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Stytch once and every client you use picks it up.
What can an AI agent actually do with my Stytch data?
An agent can read and change the configuration of your Stytch workspace, such as project settings and email templates. You can ask it what a project is set to, compare two projects, or update the wording of a password reset email, and it does the work in Stytch for you. Exactly what is available depends on what your Stytch account has set up, and short, specific asks work better than long sentences.
Does connecting Stytch give the AI access to everything in my workspace?
No. Every call to Stytch runs inside the access of the person who signed in, so the agent can only see and change the projects and templates that person already could. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what Stytch itself allows that person.
Can I stop an agent from deleting or changing things in Stytch?
Yes. Restrictions in Elaichi work per action, so you can allow reading Stytch project settings while blocking any change to them, or allow editing email templates while blocking everything else. A restricted action is never advertised to the AI client at all, so no prompt, however worded, can reach it.
What happens to a Stytch connection when someone leaves?
Offboarding that person in Elaichi ends their access to Stytch through every AI client at once. If they had shared a Stytch connection with a team, it keeps working for everyone else. If you want Stytch gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Stytch MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Stytch is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Stytch?
Yes. Both let Claude, ChatGPT or Cursor use Stytch. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Stytch call.
How is Elaichi different from Composio for Stytch?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Stytch: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Stytch in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.