Skip to main content
Glama
YOLKINS

weeek-mcp

Official
by YOLKINS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to weeek-mcp

No user-submitted related servers found.

    Related Servers

    • 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

      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.
      57 npm
      MIT

    • Personal OS MCP

      likalg
      F
      license
      A
      quality
      B
      maintenance
      MCP server for Personal OS API that enables managing tasks, notes, projects, collections, reviews, and more through typed tools over stdio.
      66
      -

    • todoist-mcp

      kevlasher
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-stdio MCP server for a single personal Todoist account with env-gated read-only mode and prompt-injection mitigations.
      273 npm
      MIT

    • TodoServer

      loki495
      A
      license
      Not graded
      quality
      B
      maintenance
      A host-local stdio MCP server that lets AI agents read and create tasks, comment, and run a full claim/heartbeat/release/complete lifecycle with automatic process identification, all through local-first actions that sync to a task workspace without exposing a GitHub token.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: ping is transport-only, weeek_get_me is token verification, list vs. get variants are explicitly separated by summary vs. full detail, and each resource (projects, tasks, members, tags, boards, columns) has its own dedicated tool. No two tools overlap in what they return or act on.

    Naming Consistency5/5

    All weeek_* tools follow a consistent verb_noun snake_case pattern (list_projects, get_task, list_board_columns). The only exception is ping, which is a standard health-check convention and does not disrupt the pattern.

    Tool Count5/5

    10 tools is well within the ideal range for a focused MCP server. Each tool covers a distinct read operation for core Weeek resources, and there is no redundancy or bloat.

    Completeness2/5

    The server is strictly read-only: it offers list/get for projects and tasks, plus list-only for members, tags, boards, and columns, but provides no create, update, or delete operations. This severely limits real-world workflows that require modifying tasks or projects, and there are no get-by-id variants for members/tags/boards/columns.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources