Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Shiftyasan Shift Scheduling

by shiftyasanversion 0.3.0i★ –iComputer or cloud
Registry namecom.shiftyasan/mcp-server

Install

Overview

Description from the maker (original English)

Generate optimized work shift schedules from staffing demand, availability and fairness rules.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Other
  • You need to fill in: SHIFTYASAN_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: SHIFTYASAN_API_KEY, SHIFTYASAN_BASE_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://api.shiftyasan.com/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "shiftyasan": {
      "command": "npx",
      "args": [
        "-y",
        "@shiftyasan/mcp-server"
      ],
      "env": {
        "SHIFTYASAN_API_KEY": "your-value",
        "SHIFTYASAN_BASE_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http shiftyasan https://api.shiftyasan.com/mcp

Or run it on your computer

claude mcp add shiftyasan --env SHIFTYASAN_API_KEY=your-value --env SHIFTYASAN_BASE_URL=your-value -- npx -y @shiftyasan/mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "shiftyasan": {
      "url": "https://api.shiftyasan.com/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "shiftyasan": {
      "command": "npx",
      "args": [
        "-y",
        "@shiftyasan/mcp-server"
      ],
      "env": {
        "SHIFTYASAN_API_KEY": "your-value",
        "SHIFTYASAN_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "shiftyasan": {
      "type": "http",
      "url": "https://api.shiftyasan.com/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "shiftyasan": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@shiftyasan/mcp-server"
      ],
      "env": {
        "SHIFTYASAN_API_KEY": "your-value",
        "SHIFTYASAN_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://api.shiftyasan.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • SHIFTYASAN_API_KEY secret required env
    API key from https://platform.shiftyasan.com/dashboard/ (free during public beta).
  • SHIFTYASAN_BASE_URL env
    Override the API base URL. Defaults to https://api.shiftyasan.com

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain shiftyasan.com (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32691 servers in this category
  • Published to the registry more recently than 22% of the other 32691 servers in this category
  • Basic checks equal to or better than 100% of the other 32691 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Shiftyasan Shift Scheduling safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SHIFTYASAN_API_KEY

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Dialyne

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Dialyne

by dialyne

Real phone calls in France for AI agents: dial +33 numbers, menus, hold, AI disclosure.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@shiftyasan/mcp-server

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, and get_solve_job

(async polling for large problems). Usage queries (get_usage) coming next.


Most people no longer need this package

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.jsnot needed20 or newer required
API keyissued automatically when you connectyou create and paste it yourself
Updatesserver-side, nothing to doyou update the package
Claude.ai (web) / ChatGPTworkscannot 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.


What is Shiftyasan?

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

Tools

ToolDescriptionCharged?
validate_shift_inputValidate a SolveRequest payload against the public-API schema (no solver).No
solve_shiftRun the solver. Small/medium problems return synchronously; large problems (roughly 25+ employees) are queued and return 202 with a job_id.Yes
get_solve_jobPoll 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).

Prompts

PromptWhat it does
plan_shiftWalks 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.

Constraints the schema accepts but the solver does not apply yet

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.

FieldStatusWorkaround
employees[].preferences[].type: "avoided_shift"Not appliedRemove 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.maxOnly min is usedUse 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.

Install

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

Setup

1. Get an API key

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

2. Configure your MCP host
Claude Desktop

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 Code
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.)

Cursor / Continue / other MCP hosts

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.

Using from ChatGPT

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

  1. ChatGPT → My GPTs → Create a GPT → Configure → Actions → Import from URL, and enter /v1/public/openapi.json (base URL = the one you received with your API key; default https://api.shiftyasan.com).
  2. If you were given a beta base URL, also edit the imported schema's servers[0].url to /v1/public.
  3. Authentication → API Key → Auth Type Bearer → paste your sk_live_... token.
  4. Suggested GPT instructions:

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.

Environment variables

VariableRequiredDescription
SHIFTYASAN_API_KEYyesBearer API key. Format: `sk_(live\test)_<64 hex chars>`.
SHIFTYASAN_BASE_URLnoOverride base URL (default https://api.shiftyasan.com). Useful for staging or self-host.

Example session

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").

Pricing

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.

Local development

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

Reporting issues

License

MIT — see LICENSE.

Ask PopNx