vwork
Related Servers
Alternatives to vwork
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA host-local stdio MCP server that lets AI agents read and create tasks, comment, and run a full claim/heartbeat/release/complete lifecycle with automatic process identification, all through local-first actions that sync to a task workspace without exposing a GitHub token.MIT
- AlicenseAqualityBmaintenanceLets ChatGPT, Claude Desktop, Claude Code, and other MCP clients run an allowlisted set of local commands and read files from a chosen directory, so an assistant can analyse a codebase or trigger local generators (images, sprites, assets) without metered API tokens. The server is read-only and deny-by-default by default, with no shell, path containment, opt-in writes, and required auth when exposed over HTTP.33MIT
- AlicenseNot gradedqualityBmaintenanceTurns your own computer into a remotely reachable MCP server so AI clients anywhere can read, write, and run commands against its files, toolchains, and local services. Includes a built-in Cloudflare tunnel, bearer-token auth, and switchable read-only, workspace, and full permission tiers with call logging.5MIT
- AlicenseAqualityCmaintenanceA local stdio MCP server that brings scattered tickets, transactions, and current policies together so a model can retrieve evidence, assess cases, and prepare reply and escalation drafts. All writes stay local and pending human review, with no ability to send messages, move money, change accounts, or publish content.7Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA stdio MCP server that lets any MCP client dispatch tasks to the local WorkBuddy desktop agent, wait until a run reaches a terminal state, and independently verify evidence such as session transcripts, tool-call counts, and archived copies. It also exposes read-only tools for locating WorkBuddy projects and sessions, publishing runs into the desktop app's workspace, and inspecting scheduled automation tasks, their run history, and overall scheduler health.MIT
- AlicenseNot gradedqualityFmaintenanceLocal stdio MCP server for working on Intern-hosted sites through guarded Git checkouts. It enables authentication, site preparation, testing, validation, and publishing via coding harnesses like Codex and Claude Code.37 npmMIT
TDQS
Scored across 11 tools
Most tools have a clearly distinct target: profile, tracker list/search/summary, a single task update, ticket list/detail, notifications, and a generic API escape hatch. The main overlap is vwork_my_tasks vs vwork_tracker_search (which also filters by assignee) and vwork_project_overview, which re-composes data from vwork_me, vwork_tracker_summary, vwork_tickets, and vwork_notifications. Descriptions do flag when to prefer each, keeping confusion limited.
All names share the vwork_ prefix and snake_case, with a mostly resource-oriented convention (vwork_me, vwork_tickets, vwork_ticket, vwork_notifications) plus a vwork_tracker_* namespace for the tracker family. The singular/plural pair (ticket/tickets) and the lone verb-style vwork_update_task are minor, readable deviations. No mixed camelCase or chaotic verb styles.
Eleven tools is squarely in the sweet spot for a workspace assistant covering identity, tracker, tickets, and notifications. Each tool corresponds to a recognizable user intent, and no redundant variations (e.g. process/run/execute) inflate the surface.
Read coverage is solid (list, search, aggregate, detail) and vwork_update_task covers the tracker write path, but there is no create/delete for tracker docs, no ticket create/update/comment, and no notification mark-as-read. The generic vwork_api tool is an escape hatch that partly compensates, though it requires the agent to know raw API paths and write-flag configuration.