Skip to main content
Glama
Orphnet

@orphnet/d1-eloquent-mcp

by Orphnet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @orphnet/d1-eloquent-mcp

No user-submitted related servers found.

    Related Servers

    • MCP NodeServer

      Bing-Xuan-Lu
      A
      license
      Not graded
      quality
      B
      maintenance
      A Node.js MCP server that gives Claude Code direct access to file operations, database queries, PHP execution, SFTP deployment, and over 60 specialized tools for development and debugging.
      1
      MIT
    • Semantic D1 MCP by semanticintent

      Semantic D1 MCPofficial

      semanticintent
      A
      license
      A
      quality
      D
      maintenance
      Enables AI-assisted analysis and optimization of Cloudflare D1 databases through comprehensive schema introspection, relationship mapping, validation, and optimization recommendations. Demonstrates semantic intent patterns with hexagonal architecture for maintainable database development workflows.
      4
      3
      MIT

    • machine-bridge-mcp

      YuLeiFuYun
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables remote MCP clients to access local filesystem and shell commands by deploying a Cloudflare Worker relay and a local daemon, providing tools like read/write files, exec commands, git status, etc.
      588 npm
      1
      MIT

    • local-model

      alkrcaaa
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients like Claude Code to delegate coding tasks to a local model through a configurable coding-agent CLI backed by any OpenAI-compatible endpoint, with tools for health checks, task execution, and context-aware file modifications.
      -
    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

    A3.6/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (list vs read vs make vs run vs validate). Even closely related tools like validate_model and validate_all are clearly differentiated by scope (single vs all). There is no ambiguity in purpose.

    Naming Consistency4/5

    The overwhelming majority use verb_noun snake_case (list_*, make_*, run_*, read_*). The only deviation is migration_status, which uses noun_noun instead of a verb prefix, but this is a minor inconsistency that does not hinder readability.

    Tool Count3/5

    At 24 tools, the set falls in the 16-25 range that feels heavy. While each tool serves a distinct purpose in the D1/Eloquent workflow, the high number may be overwhelming and includes some conveniences (like make_resource) that could be assembled from others.

    Completeness5/5

    The tool set covers the full lifecycle: listing/reading artifacts, scaffolding (model, migration, seeder, factory, pivot), running migrations/seeds/rollbacks, schema inspection, validation, and even raw SQL queries. No significant gaps are apparent for the stated scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources