Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Generate optimized work shift schedules from staffing demand, availability and fairness rules.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
SHIFTYASAN_API_KEY, SHIFTYASAN_BASE_URL标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://api.shiftyasan.com/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"shiftyasan": {
"command": "npx",
"args": [
"-y",
"@shiftyasan/mcp-server"
],
"env": {
"SHIFTYASAN_API_KEY": "your-value",
"SHIFTYASAN_BASE_URL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http shiftyasan https://api.shiftyasan.com/mcpclaude mcp add shiftyasan --env SHIFTYASAN_API_KEY=your-value --env SHIFTYASAN_BASE_URL=your-value -- npx -y @shiftyasan/mcp-server运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"shiftyasan": {
"url": "https://api.shiftyasan.com/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"shiftyasan": {
"command": "npx",
"args": [
"-y",
"@shiftyasan/mcp-server"
],
"env": {
"SHIFTYASAN_API_KEY": "your-value",
"SHIFTYASAN_BASE_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"shiftyasan": {
"type": "http",
"url": "https://api.shiftyasan.com/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"shiftyasan": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@shiftyasan/mcp-server"
],
"env": {
"SHIFTYASAN_API_KEY": "your-value",
"SHIFTYASAN_BASE_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://api.shiftyasan.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
SHIFTYASAN_BASE_URL env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 shiftyasan.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:SHIFTYASAN_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.3.0)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, LexPact UK Contracts
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Generate UK-law contracts: NDA, service, freelance, recruiter terms of business, IR35.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Model Context Protocol (MCP) server for the Shiftyasan public solver API. Lets AI agents (Claude Desktop, Cursor, Continue, etc.) call the shift-scheduling solver from any MCP-aware host.
Status: open beta —
validate_shift_input,solve_shift, andget_solve_job
(async polling for large problems). Usage queries (
get_usage) coming next.
Shiftyasan now runs a remote MCP server, which is the recommended way to connect:
https://api.shiftyasan.com/mcp
| Remote (recommended) | This npm package | |
|---|---|---|
| Node.js | not needed | 20 or newer required |
| API key | issued automatically when you connect | you create and paste it yourself |
| Updates | server-side, nothing to do | you update the package |
| Claude.ai (web) / ChatGPT | works | cannot run a local process |
Connecting from Claude.ai or ChatGPT opens a Shiftyasan sign-in page in your browser; approve it once and you are done. Revoke a connection any time from the dashboard under "Connected apps".
This package is still supported and existing setups keep working. Reach for it when you want the server to run locally — for example on a host that cannot reach the internet directly, or when you prefer to hold your own API key.
See the quickstart for the remote setup.
Shiftyasan is a SaaS that auto-generates work shifts for businesses (retail, hospitality, healthcare, etc.) using a constraint-optimization engine. The same solver is exposed as a public HTTP API at https://api.shiftyasan.com/v1/public/*. This MCP server is a thin client wrapper that turns the API into discoverable tools for AI agents.
Developer documentation — quickstart, the full list of supported constraints, and pricing — lives at [https://platform.shiftyasan.com](https://platform.shiftyasan.com) (Japanese and English).
| Tool | Description | Charged? |
|---|---|---|
validate_shift_input | Validate a SolveRequest payload against the public-API schema (no solver). | No |
solve_shift | Run the solver. Small/medium problems return synchronously; large problems (roughly 25+ employees) are queued and return 202 with a job_id. | Yes |
get_solve_job | Poll an asynchronous job until completed / failed. | No |
The full SolveRequest / SolveResponse schema lives in the OpenAPI spec at GET /v1/public/openapi.json (base URL = SHIFTYASAN_BASE_URL, default https://api.shiftyasan.com).
| Prompt | What it does |
|---|---|
plan_shift | Walks the agent through building a schedule: what to ask the user for, when to validate, and how to present the finished roster. |
Both arguments (period, context) are optional, so it can be invoked bare. In Claude Code it shows up as /mcp__shiftyasan__plan_shift; other hosts surface prompts in their own UI.
Use it when you want the agent to interview you for the inputs rather than guessing them, or when a previous attempt produced a roster you could not check at a glance. The prompt tells the agent to render one row per person with the per-person totals on the right, which is what a shift manager reads first.
The server also sends workflow guidance in its initialize response (call validate_shift_input before solve_shift, poll get_solve_job on 202, how to read shortage markers and the infeasibility diagnosis). Hosts may add this to the model's system prompt; Claude Code does, Claude Desktop currently does not, which is why the same ordering rules also live in the tool descriptions.
A few fields are accepted by the API and then dropped during translation, because the solver has no equivalent. validate_shift_input and solve_shift print an explicit warning listing exactly what was dropped, so an agent never reports them as honored.
| Field | Status | Workaround |
|---|---|---|
employees[].preferences[].type: "avoided_shift" | Not applied | Remove the shift from that employee's assignable_shift_ids (hard), or state a preferred_shift for the shift they should get instead |
employees[].working_days_per_week.max | Only min is used | Use working_days_per_month for an upper bound over the period |
constraints.employee_pairings[].rule: "require" | Not applied (only exclude works) | Use fixed_assignments to place them on the same shift |
Everything else in the schema is applied by the solver.
Running locally requires Node.js 20 or newer. If you would rather not manage that, use the
remote server instead.
Use directly via npx (no global install needed):
npx -y @shiftyasan/mcp-server
Also listed in the MCP Registry as com.shiftyasan/mcp-server.
Or install globally:
npm install -g @shiftyasan/mcp-server
shiftyasan-mcp-server
Issue an sk_live_... key in the self-service dashboard: [https://platform.shiftyasan.com/dashboard/](https://platform.shiftyasan.com/dashboard/) (your existing Shiftyasan account works; sign-up is also available). If anything goes wrong, email (Japanese or English).
Treat the token like a password: it grants access to your solver quota.
Beta note: you may receive a base URL different from the default —
set it via
SHIFTYASAN_BASE_URL(see below).
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows):
{
"mcpServers": { "shiftyasan": { "command": "npx", "args": ["-y", "@shiftyasan/mcp-server"], "env": { "SHIFTYASAN_API_KEY": "sk_live_..." } } } }
Restart Claude Desktop. The shiftyasan server appears in the tools menu and exposes validate_shift_input, solve_shift, and get_solve_job.
claude mcp add shiftyasan -e SHIFTYASAN_API_KEY=sk_live_... -- npx -y @shiftyasan/mcp-server
(Add -e SHIFTYASAN_BASE_URL=... if you were given a beta base URL.)
Add to your MCP server config in the same shape (command + args + env). Refer to your host's docs for the exact config file path.
ChatGPT cannot spawn local stdio MCP servers like this package, so use the HTTP API directly through a Custom GPT with Actions (the OpenAPI spec is designed to be Actions-compatible — fully inlined schemas, no external refs):
/v1/public/openapi.json (base URL = the one you received with your API key; default https://api.shiftyasan.com).servers[0].url to /v1/public.sk_live_... token.You can build optimized work shift schedules with the Shiftyasan actions.
Always call the validate action first (free), then solve. Large problems
return 202 with a job_id — poll the job endpoint every ~15 seconds until
the status is "completed" or "failed".
Notes: creating custom GPTs requires a paid ChatGPT plan, and the API key is stored inside the GPT — do not share that GPT publicly.
ChatGPT's MCP connectors only support hosted MCP endpoints (Streamable HTTP), not local stdio processes. A hosted MCP endpoint is on our roadmap; until then, use Actions as above.
| Variable | Required | Description | |
|---|---|---|---|
SHIFTYASAN_API_KEY | yes | Bearer API key. Format: `sk_(live\ | test)_<64 hex chars>`. |
SHIFTYASAN_BASE_URL | no | Override base URL (default https://api.shiftyasan.com). Useful for staging or self-host. |
In Claude Desktop, after configuring:
You: Schedule 3 employees over the first week of June across morning and
evening shifts. Use Shiftyasan.
Claude will discover the tools, call validate_shift_input to confirm the payload it constructed is acceptable, then call solve_shift to get the assignment. Errors from the API (RFC 7807) are surfaced inline so Claude can self-correct (e.g., "staffing_demand length must equal schedule_days").
The open beta is free. Each API key comes with a free usage quota (solve_shift consumes units per call; validate_shift_input is always free). Check your remaining quota with GET /v1/public/usage using your key. When you run out, email to get more.
Paid plans are planned after the beta. The MCP server itself never charges; all metering happens against your SHIFTYASAN_API_KEY on the API side.
git clone https://github.com/shiftyasan/mcp-server.git
cd mcp-server npm install npm run build npm test
To run against a local gateway:
SHIFTYASAN_API_KEY=sk_test_... \
SHIFTYASAN_BASE_URL=http://localhost:8080 \ npm run dev
Test interactively with the MCP inspector:
npx @modelcontextprotocol/inspector node dist/index.js
MIT — see LICENSE.