Stytch MCP Server

Official Stytch MCP server. Manage projects, redirect URLs, email templates, SDK configs, and public tokens via the Stytch Workspace Management API.

Developer Tools by Stytch OAuth2 active

Connect (Remote Server) Docs

Overview

Stytch's official MCP server is a remote, provider-hosted server that exposes the Stytch Workspace Management API to AI agents and developer IDEs. It lets an MCP-capable client (Cursor, VS Code, Claude, and others) configure Stytch authentication infrastructure programmatically through natural language, without needing to click through the Stytch dashboard or wire up direct API calls.

The server reports approximately 21 enabled tools covering Stytch's Programmatic Workspace Actions. Documented capabilities include listing and creating projects, reading and registering OAuth redirect URLs, configuring the Consumer and B2B SDKs, managing public tokens, and editing email templates. According to Stytch, anything that can be done via the Programmatic Workspace Actions API is callable as a tool.

Authentication is handled through an OAuth flow rather than static API keys. After installing the server, the IDE prompts a "Needs Authentication" step that grants the client scoped access to your Stytch workspace, after which the available tools are exposed in the client.

Tools

Tool	Description
`listProjects`	List the projects in your Stytch workspace and their IDs.
`createProject`	Create a new Stytch project in your workspace.
`getAllRedirectURLs`	Retrieve the redirect URLs registered for a project.
`createRedirectURLs`	Register new redirect URLs as default callbacks for login and signup actions.
`updateConsumerSDKConfig`	Update the Consumer SDK configuration, including enabling the SDK and authorizing domains.
`getAllPublicTokens`	Retrieve the public tokens associated with a project.
`createPublicToken`	Generate a new public token for a project.
`Email template tools`	Read and modify email templates used for auth flows (exact tool names not enumerated in public docs).

Setup Guide

Stytch hosts the MCP server itself, so there is nothing to clone or install locally. You point your MCP client at the remote URL and complete an OAuth flow.

One-click install: Visit mcp.stytch.dev and click the install button for Cursor or VS Code.

Manual install (Cursor): Open Cursor Settings, go to Tools & Integrations, and click "Add Custom MCP" to edit mcp.json:

{
  "mcpServers": {
    "stytch": {
      "url": "https://mcp.stytch.dev/mcp"
    }
  }
}

Restart the IDE. In the Tools & Integrations panel, click "Needs Authentication" next to the Stytch entry. This launches an OAuth flow that authorizes the client against your Stytch workspace. Once complete, the client will show the enabled tools (approximately 21).

Prerequisites:

An active Stytch workspace account
An MCP-capable client that supports streamable HTTP transport (Cursor, VS Code, Claude, and others)
Network access to https://mcp.stytch.dev/mcp

Tool calls require per-call approval by default. You can configure auto-run permissions in your client if you trust the agent to act unattended.

Use Cases

Bootstrap a new Stytch project end to end from an IDE: create the project, register redirect URLs, enable the Consumer SDK on your domains, and fetch the public token, all from a single agent prompt.
Have an AI agent register additional OAuth redirect URLs when you deploy a new preview environment, so dev and staging callbacks stay in sync with your code.
Audit which projects exist in your workspace and surface their public tokens and authorized domains without opening the Stytch dashboard.
Update Consumer or B2B SDK configuration (authorized domains, enabled features) as part of an automated provisioning workflow.
Edit Stytch email templates conversationally instead of clicking through the dashboard UI.

Example Prompts

"List all projects in my Stytch workspace and show me the public tokens for the Consumer Test project."
"Create a new Stytch Consumer project called 'staging', register https://staging.example.com/authenticate as a LOGIN and SIGNUP redirect URL, and enable the SDK on staging.example.com."
"Add https://preview-42.example.com/callback as a LOGIN redirect URL to my main Stytch project."
"Update the Consumer SDK config for project X to authorize the domain app.example.com."
"What public token should I use for the Stytch project named 'production'?"

Pros

Official, provider-hosted server with nothing to install or self-host.
OAuth-based auth, so you do not need to mint and rotate workspace API keys for your IDE.
Broad coverage of the Workspace Management API (projects, redirect URLs, SDK config, public tokens, email templates), roughly 21 tools.
One-click installation flow for Cursor and VS Code.

Limitations

Covers workspace and project configuration only, not end-user authentication operations like logging users in or issuing sessions at runtime.
Public documentation does not enumerate every tool by name, so the exact surface area requires connecting the server to see the full list.
Requires an existing Stytch workspace account, which limits utility for users not already on Stytch.

Alternatives

WorkOS MCP for similar auth platform configuration via MCP.
Auth0 Management API wrapped in a community MCP server for Auth0 users.
Clerk's developer tooling for those on the Clerk auth stack.