Skip to main content
Glama
atlantdak

worksection-mcp

by atlantdak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to worksection-mcp

No user-submitted related servers found.

    Related Servers

    • crewmeister-api

      BelStark
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to interact with the Crewmeister API over local stdio, covering operations for members, teams, time tracking, salary exports, and related platform resources.
      Apache 2.0

    • tasks-mcp

      prachwal
      A
      license
      B
      quality
      A
      maintenance
      Enables MCP clients to manage a project-local tracker by exposing sprint, task, and subtask operations as tools over stdio.
      19
      117 PyPI
      MIT
    • weeek-mcp by YOLKINS

      weeek-mcpofficial

      YOLKINS
      A
      license
      A
      quality
      B
      maintenance
      Local, read-only-by-default MCP server for Weeek that connects AI clients to your workspace over stdio, enabling listing projects, tasks, boards, members, and tags with opt-in write tools for task management.
      10
      64 npm
      MIT

    • AI Site Manager MCP

      nkd3v
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to connect to a WordPress site with a scoped API key and manage posts, pages, custom post types, taxonomies, comments, media, approved settings, plugins, and themes. It runs locally over stdio and requires the companion WordPress plugin to be installed and activated.
      42
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.1/5.0

    Scored across 53 tools

    Disambiguation3/5

    The read surface is dense: get_tasks, get_all_tasks, get_tasks_by_status, get_tasks_by_priority, get_overdue_tasks, and search_tasks all return task lists with overlapping filters/grouping, and get_costs/get_time_report plus auth_status/health_check/validate_configuration occupy similar niches. Descriptions are detailed enough to separate them, but an agent can easily pick the wrong variant.

    Naming Consistency4/5

    The vast majority use a clear verb_noun pattern (get_*, create_*, update_*), with state changes as verb_noun (complete_task, reopen_task, archive_project). Minor deviations like post_comment instead of create_comment, add_costs instead of create_cost, and noun-style auth_status/health_check keep it from a perfect 5.

    Tool Count1/5

    53 tools is far above the 3-15 well-scoped range and even above the 25+ 'too many' threshold; it is an extreme count for an MCP server. Many variants could be consolidated (e.g., task listing/grouping/search).

    Completeness4/5

    The surface covers the main Worksection workflow: projects, tasks, subtasks, comments, tags, files, time/costs, timers, members, and activity. The main gap is the lack of delete operations (tasks, projects, comments, files) and no ability to move a task between projects, but these are workable rather than blocking.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources