MCP Stytch B2b Okr Manager 5a20ec2b

MCPAI代理

提供方 lgong-rms · 包名 @modelcontextprotocol/inspector@latest

AI代理 stdio · 本地进程 Token 社区 / 第三方
查看接入方式

一个基于Cloudflare Workers的OKR管理系统,集成了静态网站、REST API和MCP服务器功能,使用Stytch进行身份管理。

一句话选型结论

按资料字段整理

MCP Stytch B2b Okr Manager 5a20ec2b 属于AI代理类 MCP 服务器,stdio · 本地进程,Token,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权Token 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

适用场景

OKR管理TypeScript本地部署身份验证RBAC多租户AI代理

安装与配置

stdio · 本地进程 Token
客户端在本机拉起子进程,数据不出本机
npx @modelcontextprotocol/inspector@latest

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Stytch B2b Okr Manager 5a20ec2b当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方lgong-rms上游标注的维护方 lgong-rms
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时@modelcontextprotocol/inspector@latest · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

6.2 KB
来自项目仓库与上游目录的原文,未做删改

Workers + Stytch OKR Manager 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

Member, Tenant, and client identity is managed using Stytch. Put together, these three features show how to extend a traditional full-stack CRUD application for use by an AI agent.

This demo uses the Stytch B2B product, which is purpose-built for B2B SaaS authentication requirements like multi-tenancy, MFA, and RBAC.
If you are more interested in Stytch's Consumer product, see this demo instead.

Set up

Follow the steps below to get this application fully functional and running using your own Stytch credentials.

We will be creating a complex RBAC policy with 3 personas that interacts with both Stytch-defined resources and custom resources managed by the application.
At the end we will have:
- A stytch_admin role with universal access to all resources within an organization. They will have control over objectives, key_results, and all predefined Stytch resources like members, authentication settings, and SSO configuration.
- A manager role with partial access to most resources - they may invite new members and manage key_results, but cannot set top-level company objectives
- A stytch_member role with limited access to most resources - they may view objectives and update their progress on achieving key_results

We will also create a set of scopes that our users can grant to third-party applications. In order for a user to grant a scope to an application, they must have all of the permissions that scope encompasses. For example
- The read:okrs scope requests only read access on resources, and is grantable by all members
- The manage:krs scope requests write access to the key_results resource, and is grantable by members with the manager or stytch_admin role, but not members with the stytch_user role
- The manage:objectives scope requests write access to the objectives, and is only grantable by members with the stytch_admin role

In the Stytch Dashboard

  1. Create a Stytch account. Within the sign up flow select B2B 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.

  5. Navigate to Management API and create a new workspace management key. Copy the Key ID and Secret, you will need these values later.

On your machine

  1. In your terminal, clone the project and install dependencies:```bash
    git clone https://github.com/cloudflare/agents.git
    cd agents/demos/mcp-stytch-b2b-okr-manager
    npm i

2. Create an `.env.local` file by running the command below which copies the contents of `.env.template`.```bash
cp .env.template .env.local
cp .dev.vars.template .dev.vars
  1. Open .env.local in the text editor of your choice, and set the environment variables using the public_token and project domain 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
VITE_STYTCH_DOMAIN=https://project-domain.customers.stytch.dev


4. Open `.dev.vars` in the text editor of your choice, and set the environment variables using the `Project ID`, `Project Domain` and `Secret`  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_PROJECT_SECRET=secret-test-.....
STYTCH_DOMAIN=https://project-domain.customers.stytch.dev
  1. Update your Stytch RBAC Policy by running the following command, using the workspace management Key ID and Secret you created earlier, and the Project ID found on Project Settings. You can view and edit the created RBAC Roles, Resources and Scopes in Roles & Permissions.```
    // Using example credentials, replace with your own
    npm run update-policy -- --key-id "workspace-key-prod-4881b817-6336-410a-a953-6eceabaf5xc9" --secret "6ZcNGH7v9Oxxxxxxxxxx" --project-id "project-test-6c20cd16-73d5-44f7-852c-9a7e7b2ccf62"

## Running locally

After completing all the setup steps above the application can be run with the command:```bash
npm run dev

The application will be available at http://localhost:3000 and the MCP server will be available at http://localhost:3000/sse.

Test your MCP server using the MCP Inspector```bash
npx @modelcontextprotocol/inspector@latest


Navigate to the URL where the Inspector is running, and input the following values:
- Transport Type: `SSE`
- URL: `http://localhost:3000/sse`

Click Connect to test the authorization flow and interacting with the Objectives and Key Results via your MCP Server!

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

1. Create a KV namespace for the OKR Manager app to use```
npx wrangler kv namespace create OKRManagerKV
  1. Update the KV namespace ID in wrangler.jsonc with the ID you received:```
    "kv_namespaces": [
    {
    "binding": "OKRManagerKV",
    "id": "your-kv-namespace-id"
    }
    ]

3. Upload your Stytch Project ID and Secret Env Vars for use by the worker```bash
npx wrangler secret bulk .dev.vars
  1. Deploy the workernpm run deploy

  2. Grant your deployment access to your Stytch project. Assuming your Stytch project was deployed at https://mcp-stytch-b2b-okr-manager.$YOUR_ACCOUNT_NAME.workers.dev:

  3. Add https://mcp-stytch-b2b-okr-manager.$YOUR_ACCOUNT_NAME.workers.dev/authenticate as an allowed Redirect URL
  4. Add https://mcp-stytch-b2b-okr-manager.$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!

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
MCP Stytch B2b Okr Manager 5a20ec2b 怎么安装?

在客户端按下面的安装命令接入:npx @modelcontextprotocol/inspector@latest。对应的包名是 @modelcontextprotocol/inspector@latest。装完在客户端配置里引用同一个包或端点。

MCP Stytch B2b Okr Manager 5a20ec2b 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

MCP Stytch B2b Okr Manager 5a20ec2b 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP Stytch B2b Okr Manager 5a20ec2b 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

MCP Stytch B2b Okr Manager 5a20ec2b 能提供哪些能力?

资料显示能力标签包括 多租户、TypeScript、身份验证、AI代理。具体工具清单以官方文档为准。

MCP Stytch B2b Okr Manager 5a20ec2b 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

MCP Stytch B2b Okr Manager 5a20ec2b 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。