Skip to main content
Glama
Mav977

AutoMCP-SQL

by Mav977
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AutoMCP-SQL

No user-submitted related servers found.

    Related Servers

    • mcp-sqlite-tools-plus

      MauricioPerera
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to interact with local SQLite databases with full CRUD, schema introspection, foreign key relations, generated columns, and multi-format import/export (CSV, JSON, XLSX) through natural language.
      26
      10 npm
      MIT

    • SQLite MCP Server

      irpus1603
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLM agents to perform complete database operations on SQLite databases, including creating tables, executing queries, and managing data through CRUD operations with schema inspection capabilities.
      25 npm
      MIT

    • Manual SQLite MCP Server

      CM004
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables direct interaction with a SQLite database through custom-mapped tools for creating and retrieving items. It provides structured, AI-optimized responses and manual control over database operations without requiring external API dependencies.
      -

    • Finance MCP Server

      PavelKosik
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns a personal-finance SQLite database into typed, schema-validated tools that an AI assistant can call directly, letting you manage accounts, transactions, budgets, debts, investments, tax estimates, and goals through natural language.
      33 npm
      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

    A4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool is uniquely named with a verb (get, create, update, delete) and a specific table (users, products, orders). There is no overlap because every combination of action and table is distinct and clearly indicated by the name.

    Naming Consistency5/5

    All tool names follow the same verb_noun pattern using snake_case (e.g., get_users, update_products). This is perfectly consistent across the entire set, making the tools predictable and easy to navigate.

    Tool Count5/5

    With 12 tools, the count is well-scoped for a CRUD API covering three tables (users, products, orders). Each tool serves a clear purpose, and there is no bloat or redundancy.

    Completeness5/5

    Each of the three tables has complete CRUD coverage: get (read with optional filters), create (insert), update, and delete. This covers all standard lifecycle operations for a SQL-based server, leaving no obvious dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources