# 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.

Source: https://elaichi.ai/connectors/stytch/

## Facts

| | |
| --- | --- |
| Application | Stytch |
| Category | SSO |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Stytch builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | support@stytch.com |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Stytch is connected

- 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

## Connect Stytch in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Stytch.
2. Optionally set Share with, then press Connect.
3. Approve it in Stytch. Stytch's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Stytch tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Stytch MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Stytch to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Stytch tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Stytch through Elaichi

### Check a project's settings before a release

Engineering. 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.

### Refresh sign-in email templates

Marketing. 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.

### Compare live and test project settings

Security. Line up the settings of two Stytch projects and spot the differences before a change reaches customers.

### Draft a new onboarding email in Stytch

Product. Describe the email a new user should receive and have the template written and saved in Stytch for review.

### Keep workspace configuration consistent

IT. Ask across every Stytch project for a given setting and tidy up the ones that drifted.

### Confirm what a customer's sign-in email says

Support. Pull up the exact Stytch email template a customer received so you can answer their question with the real text in front of you.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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 my team share one Stytch connection?

Yes. One person connects Stytch in Elaichi and shares the connection with a team, and nobody else ever handles a credential or signs in to Stytch directly. Each teammate still signs in to Elaichi as themselves, so every change to a Stytch project or template is logged under their own name.

### 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.