Add the server address
In your assistant’s MCP or connected-app settings, add the address above.
Prepare the roster together. Leave the decision with the manager.
Shiftly provides an MCP connection for a manager and their AI assistant. The manager explicitly selects which store workspaces to share; the assistant can read those stores’ scheduling context, interpret a request and calculate a draft. The manager reviews and confirms it in Shiftly.
Connect an assistant
Use this address in an MCP-compatible client. Shiftly uses OAuth sign-in and PKCE; you do not need to copy an API key. The client will show a Shiftly sign-in and consent screen before it can read a workspace. Choose exactly which store workspaces the assistant may use. You can review or disconnect approved assistants later in Shiftly’s Connection settings.
https://easyshiftplan.zhiyong.dev/mcpView connection metadata ↗Sign in as the store manager
Check the assistant name, store selection and requested permissions on Shiftly’s consent screen.
Review the draft in Shiftly
Use the returned preview as a proposal. It is not saved or published automatically.
Try it without connecting a store
Use the public demo endpoint in an MCP-compatible assistant. It creates a separate sample workspace for each demo session, with fictional staff and shifts. No Shiftly account is needed.
https://easyshiftplan.zhiyong.dev/mcp/demoStart a sample workspace
Call start_demo_workspace and choose an industry. Keep the returned demo ID for the next calls.
Review the sample setup
Call get_demo_workspace to see the fictional team, shift template and baseline rules.
Run the full draft flow
Call complete_demo_schedule_workflow. It interprets the request, builds a roster, checks it and states what remains. If a required detail is unclear, it stops and asks instead of claiming the schedule is done.
Sample data only; nothing is saved or published.
Each signed demo ID is time-limited and expires after two hours. It identifies only the fictional industry and expiry, not a merchant. Requests and rosters are returned to the calling assistant but not stored in the demo workspace or MCP usage metrics. Operational traffic logs may separately record the request path, IP address, browser identifier and response status. A completed result still requires the manager to review it. If you include a natural-language request, the instruction and relevant fictional setup are sent to Shiftly’s currently configured scheduling parser, which may use a cloud AI provider. That provider’s privacy practices also apply. Send sample details only—never real employee, customer or store information.
What the connected assistant can do
For a real store, access is limited to the workspaces and permissions the manager selected.
list_stores · get_store_contextRead the authorized store list and the staff, roles, availability, time off and rules needed for scheduling.
complete_schedule_workflowRun the whole process in one call: interpret, generate, check and return a clear review status.
parse_schedule_request · generate_schedule_previewUse individual steps when needed. The result may include an aggregate cost estimate, but not individual pay rates.
submit_feedback · shiftly:feedbackWith separate permission, send a short, generalized product observation to Shiftly’s admin review queue.
The assistant does not run the store.
It cannot save employee or store settings, confirm a roster, publish it, or message employees. Staff names and scheduling details from only the selected stores are shared with the assistant you authorize; do not connect a client you do not trust. Exact pay rates are not shared. Read the data-handling summary.
Feedback that can improve the product
If an assistant has the separate feedback permission, it can submit a concise observation such as “The request parser did not preserve a one-week-only rule.” Feedback is encrypted, visible only to Shiftly administrators, and kept for up to 180 days. It must not contain employee names, contact details, wage amounts, exact shift content, or private store data.
Use Shiftly to prepare a draft for this week. Show me what you understood before generating. I will review the result in Shiftly.
Common questions
Does an AI assistant need a Shiftly account?
A manager signs in and approves access to use real store data. The separate public demo needs no account and contains fictional sample data only.
Can I disconnect an assistant later?
Yes. Open Connection settings in Shiftly, review the assistants connected to your account, and disconnect any one of them. Its access is blocked immediately.
Will Shiftly send product promotions through my assistant?
No. The assistant gets a tagged public link only if someone asks what Shiftly is or asks to share a scheduling tool. It is instructed not to promote Shiftly unsolicited.
Does feedback include my prompt or schedule?
No. Usage statistics record which tool ran and whether it succeeded, not the request text or roster result. Feedback is a separate voluntary note, reviewed by an administrator.
Can the assistant publish a roster?
No. Only the manager can make final schedule changes and confirm or publish them in Shiftly.
For a manager who wants to take the next step
The public demo uses fictional data and does not save a real store roster. When someone asks about Shiftly, pricing or what to do after a demo, an assistant can call get_public_product_info for current product fit, published prices, and separate links to try it, review plans or contact a person. It cannot submit the form or start payment for them.
Published prices are US$20 per month or US$199 per year for one store, each with a 14-day trial. Payment details are required for a paid-plan trial; Stripe shows the first charge before confirmation.