workbuddy-ai
Related Servers
Alternatives to workbuddy-ai
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents like Claude Code, Codex, Cursor, and OpenCode to delegate tasks to the WorkBuddy CLI as a sub-agent via an MCP tool, with one-command setup and configurable model/permission options.1146 npm2MIT
- FlicenseNot gradedqualityDmaintenanceEnables multi-AI collaborative analysis by proxying requests to existing login-based MCP servers (Gemini CLI and Codex CLI) from Claude Desktop or Claude Code.-
- AlicenseAqualityAmaintenanceEnables a main agent to delegate execution tasks to WorkBuddy through MCP, supporting multi-turn sessions, task status tracking, permission approvals, execution reports, and CLI fallback.1031 npmMIT
- FlicenseNot gradedqualityDmaintenanceBridges any local agent or LLM to Microsoft Work IQ's remote MCP server for enterprise context grounding, tools, and chat via CLI or local MCP proxy.-
- FlicenseNot gradedqualityDmaintenanceEnables AI clients like Claude to interact with Cartena tools via MCP, supporting remote OAuth or local stdio authentication.-
- AlicenseNot gradedqualityCmaintenanceEnables external AI applications to access MCP tools by providing a user-hosted HTTPS endpoint that forwards requests to a paired desktop client.MIT
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: listing available models, performing a chat completion, and checking account/connection status. No overlap in operation or expected inputs, so an agent can easily select the right tool.
All tools use the same `wb_ai_` prefix followed by a concise noun describing the resource or action. The pattern is predictable and readable, with no mixed casing or verb-style inconsistencies.
Three tools is a well-scoped minimal surface for an AI gateway wrapper: discovery, execution, and status/authentication. Each tool earns its place, and there is no redundant or thin filler.
The core lifecycle for using the service is covered: discover models, invoke a model, and verify connection/credits. Minor gaps exist around explicit login/token refresh and multi-turn conversation management, but these are not required for the stated one-shot completion purpose.