WorkMCP
Related Servers
Alternatives to WorkMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to query a local, versioned knowledge graph of a software project, retrieving overviews, context packs, evidence, and explanations to make informed changes.MIT
- AlicenseAqualityBmaintenanceProvides agent coordination for Claude Code through a shared blackboard, decision tracking with rationale, and local semantic search over git-trackable JSONL files. It enables users to assemble tailored context packages and manage a lightweight knowledge graph for complex development tasks.15208 npm7MIT
- FlicenseNot gradedqualityAmaintenanceProvides AI agents and LLMs queryable access to a codebase's structure and data flow via Joern Code Property Graphs, enabling CPGQL querying, taint tracing, program slicing, and vulnerability hunting across many languages.-
- AlicenseNot gradedqualityBmaintenanceEnables agents to build and query a locally renewable code context graph for structured code exploration, context retrieval, and impact analysis, reducing repetitive grep and file reads.1MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI coding agents with fast, deterministic access to code graphs, knowledge lifecycle state, and cross-document symbol links, enabling compact context retrieval and seamless session handoffs.1MIT
- FlicenseNot gradedqualityDmaintenanceProvides persistent codebase memory and semantic context for AI agents via AST-aware chunking and symbol graph indexing.1-
TDQS
Scored across 24 tools
Tools mostly target distinct sources or actions: search_jobs (BA), search_arbeitnow, and get_ats_jobs are separated by source, and get_salary (official median) vs adzuna_salary (histogram) is explained in descriptions. Slight overlap remains between search_knowledge and get_changes/get_history, and between find_automation_signals and commoncrawl_lookup, but boundaries are mostly clear.
Dominant verb_noun snake_case pattern (search_jobs, get_job_details, import_reference_data, export_knowledge) is applied consistently. Minor deviations exist with noun-first/source-prefixed names (adzuna_salary, commoncrawl_lookup, graph_neighbors, knowledge_stats) and single verbs (crosswalk, remember), but the convention stays readable.
24 tools is heavy and sits in the borderline range, though the server spans several sub-domains (job search, occupation/task/skill data, salary, knowledge graph, change tracking, export). Each tool maps to a real operation, but the surface is large enough to burden tool selection.
Coverage is broad: multi-source job search and details, occupation/task/skill lookups, salary data, crosswalks, versioned memory storage, change/history tracking, graph traversal, export, and source health checks. Minor gaps like no explicit delete/forget tool for stored records and no direct occupation-to-job matching helper, but agents can work around these.