Skip to main content
Glama
AliNagy

godspeed-mcp

by AliNagy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to godspeed-mcp

No user-submitted related servers found.

    Related Servers

    • tasks-mcp

      linximengji
      F
      license
      Not graded
      quality
      B
      maintenance
      A lightweight task management MCP server that enables CRUD operations on tasks stored in a single JSON file, including listing, creating, updating progress, and setting priorities.
      215 npm
      -

    • Local Task Manager MCP Server

      akbarshaik2243
      F
      license
      B
      quality
      C
      maintenance
      A task manager MCP server that enables creating, reading, updating, and deleting tasks persisted in a local JSON file.
      4
      -

    • ContextForge MCP Lab

      dotdigitize
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP-style server for managing task records and seeded documents through controlled tool functions, using SQLite and JSON seed data.
      MIT

    • Todoist MCP Server

      mikemc
      A
      license
      A
      quality
      D
      maintenance
      A Python server that enables Claude to interact with Todoist's task management API, allowing users to create, manage, and organize tasks directly through Claude's interface.
      17
      9
      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

    C2.2/5.0

    Scored across 11 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Tools target specific actions on tasks or task lists (e.g., createTask vs. updateTask, getTask vs. listTasks, completeTask vs. uncompleteTask), making it easy for an agent to select the correct one.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout, using camelCase uniformly. All names are descriptive and predictable (e.g., createTask, deleteTask, getTaskLists), with no deviations in style or convention.

    Tool Count5/5

    With 11 tools, the count is well-scoped for a task management domain. Each tool earns its place by covering essential CRUD and lifecycle operations for tasks and task lists, avoiding bloat or thin coverage.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for the task management domain. It includes creation, retrieval, updating, deletion, listing, and state management (complete/uncomplete) for both tasks and task lists, with no obvious gaps or dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources