Skip to main content
Glama
Saaalil

Workforce MCP

by Saaalil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Workforce MCP

No user-submitted related servers found.

    Related Servers

    • cairn

      Shashank2577
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides coding agents with persistent repository context, including code maps, specs, timeline, team memory, and past session history, through MCP tools.
      136 PyPI
      Apache 2.0

    • User Context MCP Server

      HappyMonkeyAI
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes a developer's local context (communication preferences, stack, repos, memory models) to AI agents via MCP tools and resources, enabling them to bootstrap with local guidelines and reduce context hallucination.
      MIT

    • cortex

      Buzburg
      A
      license
      B
      quality
      A
      maintenance
      Enables AI coding agents and local LLMs to store and recall project memory, compact verbose logs, look up code symbols, create and rewind workspace snapshots, detect risky commands and loops, pack context optimally, and draft tokens through MCP tools.
      10
      1
      Apache 2.0

    • Forja MCP Server

      gilsonfiho
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes specialized agents as MCP tools so users can manage and triage Jira tasks, analyze repositories for health and conventions, generate commit/PR/DevOps patterns, assemble reports, produce slides and infographics, and run semantic search over a knowledge base. Everything is invokable directly from inside a coding session in Claude Code, Cursor, or Claude Desktop.
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation3/5

    Most tools are distinct, but workforce_as and workforce_specialize are explicitly aliases, creating a clear overlap. The descriptions help mitigate confusion, but the redundancy could still cause an agent to select the wrong one.

    Naming Consistency2/5

    All tools share the workforce_ prefix, but the action part is inconsistent: list_roles is verb_noun, as is a preposition, handoff is a noun, while delegate, specialize, consult, and discuss are verbs. This mixed pattern lacks the predictable verb_noun structure expected.

    Tool Count5/5

    Seven tools is well within the ideal range for a specialist context manager. Each tool serves a distinct purpose in the workflow, and the count feels appropriately scoped without excess or deficiency.

    Completeness5/5

    The tool set covers the full lifecycle: listing roles, delegating work, loading contexts, monitoring mid-task quality, switching between contexts, and running discussions. There are no obvious dead ends or missing operations for the domain it addresses.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources