e-worker-mcp
Related Servers
Alternatives to e-worker-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceA local-first open-source MCP server that acts as a personal secretary, memory manager, and automation hub—it syncs Calendar, Gmail, Canvas, GitHub, and Health into a typed temporal memory graph, and enables approval-gated write actions like creating events, drafting/sending mail, and filing issues, all with telegram/slack/CLI interfaces and a SQLite-backed audit trail.33Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server that enables AI-assisted coding through workspace-scoped tools for file reading/editing, command execution, jobs, Git, LSP, media, browser, and desktop workflows. It enforces OAuth, workspace ACL, trust policies, and file/secret guards so owners can safely grant inspect, edit, or trusted capabilities.346 npmMIT
- AlicenseNot gradedqualityFmaintenanceA local MCP server that records completed tasks to daily JSONL files and promotes substantial work to a cumulative weekly Markdown worklog, providing persistent, searchable logs of AI-assisted productivity.MIT
- AlicenseCqualityBmaintenanceA local-first MCP server that enables coding agents to see and operate a browser and desktop, transcribe microphone input, and use local memory, research, workflow and privacy-session tools under code-enforced, user-granted permissions. Every action reports verified result states, so agents can act on real machines without silently overstepping consent.78MIT

SmileWorkofficial
AlicenseNot gradedqualityBmaintenanceA local, stdio-based MCP server that lets multiple coding agents share one project database for tasks, verification evidence, signals, knowledge, and conversation indexes. It enforces workflows with allowlisted verification runners and gate checks on acceptance criteria, evidence, dependencies, and high-risk approval before work can be closed.59 npmMIT- AlicenseNot gradedqualityBmaintenanceLocal-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.1MIT
TDQS
Scored across 25 tools
Each tool has a clearly distinct purpose: read-only queries, preview dry-runs, and apply mutations are separated with explicit _preview and _apply suffixes. Resource-specific operations (todo, time, file, db, diagnose) are well compartmentalized, leaving no ambiguity between tools.
Most tools follow a resource_action or resource_action_preview/apply pattern in snake_case (e.g., todo_list, todo_create_apply, db_export). However, a few outliers like safety_policy, report_daily, report_weekly, diagnose_report, and diagnose_collect deviate from the verb_noun convention, making the set slightly inconsistent.
At 25 tools, the server covers multiple domains (todos, time logging, reports, diagnostics, file management, DB import/export), which explains the large count. While each tool serves a purpose, the set feels heavy and may overwhelm agents; it sits at the top of the 'borderline' range for tool count.
The tool surface covers core workflows: todo lifecycle (create, update, transition, list, get), time logging, daily/weekly reports, file operations, diagnostics, and DB import/export. Minor gaps exist, such as no update/delete for time logs, no explicit todo delete (though archived status may suffice), and diagnostic suggestions are not executable within the server.