MCP Work History Server
Related Servers
Alternatives to MCP Work History Server
No user-submitted related servers found.
Related Servers
- 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
- AlicenseBqualityFmaintenanceA Model Context Protocol server for AI agents to manage tasks and track progress across projects, with features like project isolation, search, and reporting.115 npm1MIT
- FlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that stores personal context as structured Markdown files with a knowledge graph, enabling AI agents to query identity, devices, servers, and projects on-demand.-

Lspace MCP Serverofficial
FlicenseAqualityFmaintenanceAn open-source server implementing the Model Context Protocol (MCP) that enables capturing insights from AI sessions and transforming them into persistent, searchable knowledge accessible across tools.78-- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects multiple AI models into a single workflow, enabling multi-model orchestration, conversation continuity, and tools like code review, planning, and CLI-to-CLI bridging.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to manage changelogs, projects, and content through natural language interactions with Changerawr instances.2MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'log_activity' follows a clear verb_noun pattern.
A single tool is too few for a server with a broad purpose like 'Work History,' which suggests tracking or managing activities. This minimal set severely limits functionality and likely leaves significant gaps in coverage.
The server is severely incomplete for a work history domain. It only allows logging activity but lacks essential operations like retrieving, updating, deleting, or querying logs, making it impossible for agents to perform basic CRUD workflows.