Stytch Consumer TODO MCP Server
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Stytch Consumer TODO MCP Serveradd a todo to buy milk"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Workers + Stytch TODO App MCP Server
This is a Workers server that composes three functions:
A static website built using React and Vite on top of Worker Assets
A REST API built using Hono on top of Workers KV
A Model Context Protocol Server built using on top of Workers Durable Objects
User and client identity is managed using Stytch. Put together, these three features show how to extend a traditional full-stack application for use by an AI agent.
This demo uses the Stytch Consumer product, which is purpose-built for Consumer SaaS authentication requirements. If you are more interested in Stytch's B2B product, see this demo instead.
Set up
Follow the steps below to get this application fully functional and running using your own Stytch credentials.
In the Stytch Dashboard
Create a Stytch account. Within the sign up flow select Consumer Authentication as the authentication type you are interested in. Once your account is set up a Project called "My first project" will be automatically created for you.
Navigate to Frontend SDKs to enable the Frontend SDK in Test
Navigate to Connected Apps to enable Dynamic Client Registration
Navigate to Project Settings to view your Project ID and API keys. You will need these values later.
On your machine
In your terminal clone the project and install dependencies:
git clone https://github.com/stytchauth/mcp-stytch-consumer-todo-list.git
cd mcp-stytch-consumer-todo-list
npm iNext, create an .env.local file by running the command below which copies the contents of .env.template.
cp .env.template .env.localOpen .env.local in the text editor of your choice, and set the environment variables using the public_token found on Project Settings.
# This is what a completed .env.local file will look like
VITE_STYTCH_PUBLIC_TOKEN=public-token-test-abc123-abcde-1234-0987-0000-abcd1234Create a .dev.vars file by running the command below which copies the contents of .dev.vars.template
cp .dev.vars.template .dev.varsOpen .dev.vars in the text editor of your choice, and set the environment variables using the Project ID, Secret, and Project Domain found on Project Settings.
// This is what a completed .dev.vars file will look like
STYTCH_PROJECT_ID=project-test-6c20cd16-73d5-44f7-852c-9a7e7b2ccf62
STYTCH_SECRET=your-stytch-secret-key
STYTCH_DOMAIN=https://cname-word-1234.customers.stytch.devRelated MCP server: Todo Markdown MCP Server
Running locally
After completing all the setup steps above the application can be run with the command:
npm run devThe application will be available at http://localhost:3000 and the MCP server will be available at http://localhost:3000/mcp.
Test your MCP server using the MCP Inspector
npx @modelcontextprotocol/inspector@latestNavigate to the URL where the Inspector is running, and input the following values:
Transport Type:
Streamable HTTPURL:
http://localhost:3000/mcp
Deploy to Cloudflare Workers
Click the button - you'll need to configure environment variables after the initial deployment.
Or, if you want to follow the steps by hand:
Create a KV namespace for the TODO app to use
wrangler kv namespace create TODOSUpdate the KV namespace ID in
wrangler.jsoncwith the ID you received:
"kv_namespaces": [
{
"binding": "TODOS",
"id": "your-kv-namespace-id"
}
]Upload your Stytch Env Vars for use by the worker
npx wrangler secret bulk .dev.varsDeploy the worker
npm run deployGrant your deployment access to your Stytch project. Assuming your Stytch project was deployed at
https://mcp-stytch-consumer-todo-list.$YOUR_ACCOUNT_NAME.workers.dev:Add
https://mcp-stytch-consumer-todo-list.$YOUR_ACCOUNT_NAME.workers.dev/authenticateas an allowed Redirect URLAdd
https://mcp-stytch-consumer-todo-list.$YOUR_ACCOUNT_NAME.workers.devas an allowed Authorized Application in the Frontend SDKs configuration
Get help and join the community
:speech_balloon: Stytch community Slack
Join the discussion, ask questions, and suggest new features in our Slack community!
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/stytchauth/mcp-stytch-consumer-todo-list'
If you have feedback or need assistance with the MCP directory API, please join our Discord server