Skip to main content
Glama
IlyaIvanchikov

weeek-mcp-smart

by IlyaIvanchikov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to weeek-mcp-smart

No user-submitted related servers found.

    Related Servers

    • weeek-mcp

      MaxViksna
      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
      35 npm
      MIT

    • Weeek MCP Server

      AlekMel
      F
      license
      Not graded
      quality
      D
      maintenance
      Full-featured MCP server integrating all 71 endpoints of the Weeek API as MCP tools for AI clients, enabling task, project, and workspace management via natural language.
      3
      -
    • 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
      35 npm
      MIT

    • weeek-mcp

      prod-broke-again
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for the Weeek Public API. Use it from Cursor or Claude Code to browse projects, search tasks, read attachments, and (with a browser session) load task comments.
      35 npm
      MIT

    • workspace-board-mcp

      FURYER
      F
      license
      A
      quality
      C
      maintenance
      MCP server for workspace kanban boards, enabling board operations like get, add, update, move, delete cards and columns.
      8
      -
    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 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: version, project listing, member listing, task CRUD, batch creation, deletion, completion, moving, and file attachment. Even create_task vs create_tasks are clearly separated by singular/plural and batch semantics. No two tools appear to overlap in purpose.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_projects, create_task, update_task, delete_task, complete_task, move_task, attach_file). The single deviation is weeek_version, which uses a noun instead of get_version, but this is minor and understandable for a status endpoint.

    Tool Count5/5

    12 tools is well within the ideal 3-15 range and each tool serves a distinct, necessary function for the WEEEK task management domain. The count feels appropriately scoped without unnecessary duplication or bloat.

    Completeness4/5

    The toolset thoroughly covers the task lifecycle: create (single/batch), get/list, update (title/due), complete/reopen, move, delete, and file attachment, plus member lookup for assignment. Minor gaps include no project creation or explicit column listing, but these can be worked around via the create_task/move_task name-or-id parameters and are likely outside the server's intended scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources