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

    • User Context MCP Server

      HappyMonkeyAI
      A
      license
      Not graded
      quality
      D
      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
    • CRMy by crmy-ai

      CRMyofficial

      crmy-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with operational customer context, including typed revenue objects, persistent state, scoped tools, and human-in-the-loop handoffs through MCP, REST, and CLI.
      0
      12
      Apache 2.0

    • ContextAtlas

      codefromkarl
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents to retrieve and manage code context with hybrid search, project memory, and observability via MCP tools.
      29
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources