OpenBot WorkBuddy Bridge
Related Servers
Alternatives to OpenBot WorkBuddy Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceConnects an MCP-compatible assistant running locally to a native Revit session through a pyRevit bridge, exposing document and selection context, status checks, and optionally unsandboxed IronPython scripting that can modify models and files.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding orchestrators to delegate local development and self-testing to the WorkBuddy desktop CLI via stdio, exposing tools to start tasks, query progress, record independent review verdicts, continue rework in the original session, and cancel runs.Apache 2.0
- AlicenseAqualityCmaintenanceEnables another WorkBuddy/CodeBuddy client to list and chat with any WorkBuddy AI (international) model through MCP tools such as wb_ai_models, wb_ai_chat, and wb_ai_status, with tool calling relayed for Agent mode. It reuses the already-signed-in desktop app's credential read-only, so no API key is required.3MIT

aiinbx-mcpofficial
AlicenseNot gradedqualityBmaintenanceProvides a stdio MCP bridge to the hosted AI Inbx workspace server, letting assistants read and send email, manage threads, domains, pacing, suppressions, webhooks, and other workspace operations using an API key. It serves as a fallback for clients that can only start MCP servers as a command.704 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables an AI assistant to read bookings, check availability and session conditions, and prepare unsaved booking, cancellation or waitlist previews for a TheirCare / FullyBooked account through a local stdio MCP connection. Final saving and terms acceptance are deliberately left to the user, who confirms them personally in the bundled local companion web interface.MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Desktop or Claude Code to drive the local daemon through stdio, listing agents and sessions, running agents, and reporting costs.-
TDQS
Scored across 4 tools
The tools map to distinct lifecycle actions: status, run, continue, and cancel. run and continue could be confused because both can reuse a saved conversation, but the descriptions clarify that continue targets a specific existing conversation while run executes a task.
All tools use a consistent snake_case workbuddy_verb pattern. The names are predictable and immediately indicate the action.
Four tools are well-scoped for a narrow desktop bridge: check status, run, continue, and cancel. There is no obvious bloat, and each tool has a clear role.
The surface covers the core lifecycle of checking status, running, continuing, and cancelling a WorkBuddy conversation. A minor gap is the lack of an explicit tool to list or discover existing conversations, which may be needed before continue can be used confidently.