start_demo_workspace — Shiftly Staff Scheduling Demo MCP Tool Mutating
start_demo_workspace
(start demo workspace) is one of 4 tools on the
Shiftly Staff Scheduling Demo
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call start_demo_workspace from your client
- Claude Code Shiftly Staff Scheduling Demo start_demo_workspace run in your project directory
- Claude Desktop Shiftly Staff Scheduling Demo start_demo_workspace ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Shiftly Staff Scheduling Demo start_demo_workspace ~/.cursor/mcp.json
- VS Code Shiftly Staff Scheduling Demo start_demo_workspace .vscode/mcp.json
- Zed Shiftly Staff Scheduling Demo start_demo_workspace ~/.config/zed/settings.json
- Windsurf Shiftly Staff Scheduling Demo start_demo_workspace ~/.codeium/windsurf/mcp_config.json
- Cline Shiftly Staff Scheduling Demo start_demo_workspace ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Shiftly Staff Scheduling Demo start_demo_workspace ~/.gemini/settings.json
- Grok Shiftly Staff Scheduling Demo start_demo_workspace .mcp.json (in your project root)
- ChatGPT Shiftly Staff Scheduling Demo start_demo_workspace Settings → Connectors → Advanced → Developer mode
- Claude.ai Shiftly Staff Scheduling Demo start_demo_workspace Settings → Connectors → Add custom connector
- LangChain Shiftly Staff Scheduling Demo start_demo_workspace pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http shiftly-scheduling https://easyshiftplan.zhiyong.dev/mcp/demoOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 7 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.