1. Conduid
  2. Cloud
  3. Stytch Consumer Todo List
MCP server · Cloud

Stytch Consumer Todo List

Workers + Stytch TODO App MCP Server

Unclaimed MIT last commit 7 months ago cloud
60Good

Scored 5 months ago · breakdown

About Stytch Consumer Todo List

Stytch Consumer Todo List is an MCP server published by stytchauth in the Cloud category: workers + Stytch TODO App MCP Server.

The repository has 27 stars and 10 forks, with the last commit 7 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/stytchauth/mcp-stytch-consumer-todo-list

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Stytch Consumer Todo List

Powered by Claude · Grounded in docs

I know everything about Stytch Consumer Todo List. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository yesterday. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

Workers + Stytch TODO App MCP Server

This is a Workers server that composes three functions:

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

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

  2. Navigate to Frontend SDKs to enable the Frontend SDK in Test

  3. Navigate to Connected Apps to enable Dynamic Client Registration

  4. 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 i

Next, create an .env.local file by running the command below which copies the contents of .env.template.

cp .env.template .env.local

Open .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-abcd1234

Create a .dev.vars file by running the command below which copies the contents of .dev.vars.template

cp .dev.vars.template .dev.vars

Open .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.dev

Running locally

After completing all the setup steps above the application can be run with the command:

npm run dev

The 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@latest

Navigate to the URL where the Inspector is running, and input the following values:

  • Transport Type: Streamable HTTP
  • URL: http://localhost:3000/mcp

Deploy to Cloudflare Workers

Click the button - you'll need to configure environment variables after the initial deployment.

Deploy to Cloudflare

Or, if you want to follow the steps by hand:

  1. Create a KV namespace for the TODO app to use
wrangler kv namespace create TODOS
  1. Update the KV namespace ID in wrangler.jsonc with the ID you received:
"kv_namespaces": [
   {
      "binding": "TODOS",
      "id": "your-kv-namespace-id"
   }
]
  1. Upload your Stytch Env Vars for use by the worker
npx wrangler secret bulk .dev.vars
  1. Deploy the worker
npm run deploy
  1. Grant 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:
    1. Add https://mcp-stytch-consumer-todo-list.$YOUR_ACCOUNT_NAME.workers.dev/authenticate as an allowed Redirect URL
    2. Add https://mcp-stytch-consumer-todo-list.$YOUR_ACCOUNT_NAME.workers.dev as 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!

README fetched from the repository yesterday. The original is authoritative.

Questions

About Stytch Consumer Todo List

How do I install Stytch Consumer Todo List?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Stytch Consumer Todo List safe to use with an AI agent?

Its trust score is 60 out of 100 (good). It passes 4 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Stytch Consumer Todo List still maintained?

The last commit was 7 months ago and 2 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.