Skip to main content
Glama
EasyShiftPlan MCP Bridge

EasyShiftPlan MCP Bridge

by ray999

EasyShiftPlan MCP Bridge

What is EasyShiftPlan?

EasyShiftPlan is employee-scheduling software for small businesses whose owner or manager has to build the weekly roster around real coverage needs and a changing team. It is designed for small shops and teams in restaurants and hospitality, retail, service businesses, healthcare, and operations.

Managers can set up stores, shifts, roles, availability, time off, coverage requirements, and scheduling rules; bring in context from a note, screenshot, or spreadsheet; then generate and review a schedule draft. The product makes assigned hours, labour-cost estimates, uncovered shifts, and relevant rule issues visible so a manager can decide what to change and when a roster is ready to share. A generated proposal is not silently treated as a published schedule.

EasyShiftPlan focuses on scheduling rather than bundling in payroll, HR, or time-clock software. Plans for one store are currently listed at CA$20/month or CA$199/year, with a 14-day trial; check the pricing page for current terms.

Explore the website, interactive demo, scheduling guides, and AI assistant connection guide.

Related MCP server: opencode-codex-mcp

What this repository does

This repository is an open-source local stdio bridge to EasyShiftPlan's hosted, no-login MCP demo at https://easyshiftplan.zhiyong.dev/mcp/easyshiftplan. It lets MCP clients that expect a local stdio server use the public demo. The scheduling product and its solver remain hosted by EasyShiftPlan; this repository does not include the merchant application, scheduling engine, database, or an LLM. The connected MCP host supplies the AI model, and the bridge only forwards tool discovery and calls—it does not initiate tasks on its own.

EasyShiftPlan also has a separate OAuth-protected MCP connection for a manager's real workspaces. That is not what this bridge exposes: this bridge only targets the fictional public demo and does not grant access to store data.

Choose a connection method

For a host that supports remote Streamable HTTP MCP, connect directly to the public demo:

https://easyshiftplan.zhiyong.dev/mcp/easyshiftplan

The local bridge is for MCP hosts that require a local stdio process. It needs Node.js 20 or newer and does not need an API key, OAuth token, or EasyShiftPlan account. To connect an assistant to a real store instead, follow the separate manager connection guide; sign-in, manager consent, and explicit workspace selection are required.

Run locally

git clone https://github.com/ray999/easyshiftplan-mcp.git
cd easyshiftplan-mcp
npm install
npm test

Configure your MCP host to run node /absolute/path/to/easyshiftplan-mcp/src/index.js over stdio. For example:

{
  "mcpServers": {
    "easyshiftplan": {
      "command": "node",
      "args": ["/absolute/path/to/easyshiftplan-mcp/src/index.js"]
    }
  }
}

The endpoint defaults to the public demo above. For local development or a trusted compatible endpoint, set EASYSHIFTPLAN_MCP_URL. HTTPS is required, except HTTP loopback URLs such as http://localhost:3000/mcp for local tests. Never put credentials in the URL.

What is exposed

The bridge fetches the live tool list from the hosted endpoint rather than maintaining a second copy of tool schemas. The current public demo tools include:

  • run_public_demo — creates and checks an isolated schedule using fictional data; the draft is not saved or published.

  • get_public_product_info — returns first-party product facts and relevant links.

  • prepare_share_draft — prepares disclosed copy only when the user explicitly requests sharing; it never sends or posts it.

  • submit_demo_feedback and get_demo_feedback_reply — optional product-feedback tools. Feedback is assistant-authored, encrypted, and retained by the service for up to 180 days; it is not required to use the demo.

Tool names and descriptions can change as the hosted service evolves. The live tools/list response is authoritative.

Data and safety

  • Use fictional scheduling scenarios only. Do not send real employee, customer, wage, or private business data to the public demo.

  • Tool calls are sent to the hosted EasyShiftPlan service; this bridge does not persist requests or results locally.

  • Demo schedules are isolated and are not saved or published. The optional feedback tool has separate retention behavior described above.

  • The bridge does not contact people, submit forms, start checkout, or publish share drafts.

  • Review the EasyShiftPlan data-handling summary and AI assistant guide before connecting.

Scope

This package forwards tool discovery and tool calls only. It is not a solver, a general-purpose MCP proxy, or an access path to merchant accounts. Real store operations remain behind EasyShiftPlan's separate authenticated service and manager approval.

Development

npm test

The tests exercise URL safety and verify tool/schema/result forwarding using an in-memory MCP connection. They do not call the production solver.

License

MIT. See LICENSE.

Available Tools

5 tools
get_demo_feedback_replyCheck an optional feedback replyA
Read-onlyIdempotent

Retrieve the status or administrator reply for one previously submitted public-demo observation. Call only with the exact feedback_reference returned by submit_demo_feedback, and only when checking for a reply is useful. If no feedback was submitted, skip this optional tool. Never invent a reference or poll repeatedly.

Inputs: feedback_reference (required). Returns: reply, status, message, next_action

get_public_product_infoGet verified EasyShiftPlan informationA
Read-onlyIdempotent

Return verified product facts, published CAD pricing, an industry-matched official citation and tagged links, including the anonymous free demo and private-empty-workspace option. Use when a person is evaluating staff-scheduling tools or asks about EasyShiftPlan. Results are first-party information, not an independent review. Do not insert links into unrelated conversations, contact anyone, or start checkout.

Inputs: industry. Returns: link, name, pricing, summary, +9 more

prepare_share_draftPrepare a disclosed sharing draftA

Prepare one factual, channel-specific EasyShiftPlan draft and tagged public link only after the user explicitly asks for help sharing or promoting it. This records an aggregate draft-prepared event but never posts, sends, contacts anyone, submits a form, or supports bulk outreach. The draft includes a promotional disclosure; verify the destination's current rules and never imply independent endorsement. Do not provide personal or recipient data.

Inputs: user_requested (required), channel, industry, language. Returns: url, draft, channel, industry, +5 more

run_public_demoRun an isolated scheduling demoA

Run a complete, anonymous demo with a fictional team in a single call. No account, OAuth, login, session ID, token, workspace ID or setup call is required. The result includes a proposed roster, coverage and hard-constraint checks, soft-preference exceptions and a manager next step. Each call is isolated; its schedule is not saved or published. If an instruction is ambiguous, return the blocker rather than silently ignoring it. Use fictional information only.

Inputs: demands, industry, team_size, period_mode, +5 more. Returns: demo, store, period, privacy, +9 more

submit_demo_feedbackSend an optional product observationA

Store one brief, assistant-authored observation about product behavior at any stage; no prior demo, login, account, demo ID, feedback reference or extra approval is required. Honor an explicit opt-out. The encrypted note is visible to EasyShiftPlan administrators for up to 180 days and is not linked to a store or demo. Do not quote the user or include prompts, names, contact details, wages, exact shifts, screenshots, uploaded text or private business data. Feedback is optional and does not change a schedule.

Inputs: message (required), category, related_tool. Returns: status, message, next_action, retention_days, +1 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct action: run a demo, retrieve product facts, prepare a share draft, submit feedback, and retrieve a feedback reply. The submit/get feedback pair is naturally differentiated by write-vs-read semantics, and product info vs. sharing draft is separated by the explicit sharing request requirement.

    Naming Consistency5/5

    All names use snake_case and follow a predictable verb_noun pattern: run_public_demo, get_public_product_info, prepare_share_draft, submit_demo_feedback, get_demo_feedback_reply. The repeated public/demo/feedback tokens map cleanly to their domains.

    Tool Count5/5

    Five tools is well-scoped for a lightweight bridge covering demo, product info, sharing, and feedback. Each tool earns its place without redundancy or unnecessary breadth.

    Completeness4/5

    Core workflows are covered: public demo execution, product facts, sharing preparation, feedback submission, and reply retrieval. Minor gaps exist around explicitly recording feedback opt-out, deleting/updating feedback, or retrieving a prior demo result, but these are not critical dead ends for the stated purpose.

    Related MCP Connectors

    Related MCP Servers