EasyShiftPlan MCP Bridge
Related Servers
Alternatives to EasyShiftPlan MCP Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables locally configured MCP servers to be called over stdio and mixed with xAI server-side tools, without relying on hosted xAI MCP.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Cursor and Claude Desktop to connect to a remote host daemon over stdio and invoke its MCP tools, including device listing and single-tool calls.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code, Cursor, OpenCode/LunaCode, and other MCP clients to invoke the harness's shell, file, code, scheduling, and device-control tools over stdio.MIT
- AlicenseNot gradedqualityDmaintenanceEnables stdio-only MCP clients to connect to Agent Community's hosted Streamable HTTP MCP server for accessing hosted agents and tools.16 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to access hosted models and services via a local stdio bridge, with live model discovery, pricing, balance checks, and paid execution requiring cost estimates.MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible hosts such as OpenCode to drive the Codex CLI through codex app-server over stdio, exposing tools to run prompts, inspect status, list threads, and interrupt running turns.-
TDQS
Scored across 5 tools
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.
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.
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.
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.