Skip to main content
Glama
Sign In
@bldbl/mcp

@bldbl/mcp

by chunkydotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @bldbl/mcp

No user-submitted related servers found.

    Related Servers

    • bldr

      tek-cat
      A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight build daemon that exposes project build flows as MCP tools, enabling AI assistants to drive builds, check status, and react to results.
      MIT

    • Taskade MCP Server

      kCampbell926
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects MCP clients such as Claude, Cursor, VS Code, and Windsurf to workspaces so users can list and manage projects, tasks, folders, and AI agents through natural language. It also includes an OpenAPI codegen package that generates MCP tools from any OpenAPI spec, not just the hosted API.
      1,958 npm
      MIT

    • Autodesk Build MCP Server

      SamuraiBuddha
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server implementation for Autodesk Construction Cloud Build that enables AI assistants to manage construction issues, RFIs, submittals, photos, forms, and costs through natural language.
      -

    • MCP Python Toolbox

      gianlucamazza
      A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to perform Python development tasks through file operations, code analysis, project management, and safe code execution.
      9
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    C2/5.0

    Scored across 7 tools

    Disambiguation4/5

    The tools have distinct purposes with minimal overlap: 'complete_task' and 'start_task' are clearly different lifecycle stages, while 'get_next_task', 'get_project_context', and 'update_progress' serve unique informational or update functions. However, 'create_discussion' might be ambiguous in relation to task management, as it could overlap with task-related communication.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as 'complete_task', 'create_discussion', and 'get_next_task'. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a task or project management server. It covers core operations like starting, completing, and tracking tasks, along with auxiliary functions like health checks and discussions, without being overly sparse or bloated.

    Completeness3/5

    The tool set covers basic task lifecycle (start, complete, progress update) and project context, but lacks obvious operations like listing tasks, updating task details, or deleting tasks. This creates minor gaps that agents might need to work around, though core workflows are partially supported.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources