Skip to main content
Glama
Sign In
ModelBound

ModelBound

Official
by ModelBound
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ModelBound

No user-submitted related servers found.

    Related Servers

    • cursor-agent-bridge

      cybas
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that lets Claude Code or any MCP client delegate coding tasks to the local Cursor Agent CLI, with persistent per-workspace sessions and tools for diffing and pushing changes.
      12 npm
      MIT

    • SkillPort

      gotalab
      A
      license
      Not graded
      quality
      C
      maintenance
      A management toolkit for AI agent skills that provides an MCP server for search-first skill discovery and on-demand loading. It enables users to validate, organize, and serve standardized skills to MCP-compatible clients like Cursor and GitHub Copilot.
      584 PyPI
      420
      MIT

    • Agent Harness Kit

      WaelBos1796
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a provider-agnostic MCP server that gives AI coding agents a shared workflow for drafting specs, claiming tracked tasks, logging actions and handoffs, and gating completion on health-check evidence. It also bundles read-only skills for triage, review, consultation, and product guidance across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.
      29 npm
      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.9/5.0

    Scored across 51 tools

    Disambiguation3/5

    Most tools target distinct actions, but several check/safety tools overlap heavily (skills.checks, skills.flightCheck, check_harness, skill.findings all 'check a skill' with subtly different scopes), and test tools (skill.test, eval.run, skill.benchmark, skill.testRuns) blur together. Detailed descriptions help, but selection still requires careful reading.

    Naming Consistency2/5

    Mix of dot-namespaced and flat snake_case tools (check_harness, report_run) with no unified scheme, and even the namespaces are inconsistent (skills. vs skill.). Method casing is also mixed, e.g. skill.report_outcome (snake) alongside skills.reviewRequest (camelCase).

    Tool Count2/5

    51 tools is heavy for a skill-management server and clearly exceeds the 25+ 'too many' threshold. Multiple families (review, checks, tests, optimization) contain near-duplicate capabilities that inflate the surface beyond what the core purpose requires.

    Completeness4/5

    Broad lifecycle coverage: scaffold/create, read/write, cloud push/pull/list, versioning/diff, review workflow, testing, eval, optimization, and outcome reporting are all present. Only minor gaps remain, and agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources