Skip to main content
Glama

Related Servers

Alternatives to weeek-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to read and manage Weeek workspaces through the full public API, covering projects, boards, tasks, comments, time tracking, funnels, deals, contacts, and currencies. It defaults to read-only operation, supports configurable allow/deny filters and profiles, and exposes MCP resources and prompts for common workflows.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to navigate and modify Weeek projects, boards, tasks, assignees, comments, tags, and time tracking through the Weeek API, with actions attributed to the API token owner.
      13
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      MCP server for WEEEK Public API v1 enabling management of tasks, projects, boards, tags, custom fields, time tracking, and CRM entities.
      100
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that lets an agent work with the Weeek task manager: view boards, create, update and move tasks and subtasks, write and delete its own comments, attach and download files, and build time reports. It keeps project-specific boards, columns and conventions in a committed .weeek.json, and is read-only-safe, token-scoped, and limited to allowed attachment folders.
      11
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to manage Super Productivity tasks, projects, and tags via its Local REST API, including task creation, updates, starting, stopping, archiving, and reading status and Focus Mode state.
      16
      MIT

    TDQS

    B3.1/5.0

    Scored across 35 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes with detailed descriptions that cross-reference related tools. A few pairs could be confused (e.g., move_task vs add_task_to_project, manage_time_entry vs task_timer), but the descriptions generally clarify the boundaries.

    Naming Consistency4/5

    All tool names use a consistent snake_case with the weeek_ prefix and mostly follow a verb_noun pattern (list_, manage_, get_, create_, update_, delete_, add_, remove_, set_, move_, etc.). Minor deviations like 'whoami' and 'task_timer' break the pattern, and 'manage_' is used for multi-action tools, but overall the convention is predictable.

    Tool Count3/5

    With 35 tools, the surface is heavy for a single MCP server, exceeding the typical 3-15 range. However, the breadth of the task management domain (projects, tasks, boards, columns, comments, custom fields, tags, time tracking, attachments, members, assignments, portfolios) justifies many of them, though some consolidation could still reduce the count.

    Completeness4/5

    The tool set covers core CRUD and lifecycle operations for most entities: projects, tasks, boards, columns, comments, custom fields, tags, time entries, attachments, assignees, watchers, and portfolios. Notable gaps include no list operation for time entries or attachments (only create/get), and no direct read of a single project or board, but these are minor and workable around.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data