Skip to main content
Glama
yusuferenkt

MCP JSON Database Server

by yusuferenkt

Related Servers

Alternatives to MCP JSON Database Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      A customer and product management MCP server using SQLite. It enables Claude Desktop users to manage client and product data through natural language interactions.
      9
      1
      -
    • A
      license
      A
      quality
      C
      maintenance
      A Node.js MCP server that enables Claude Desktop to securely run read-only SQL queries against MariaDB/MySQL and Microsoft SQL Server databases using OAuth 2.0 PKCE authentication. It provides short-lived, per-user credentials that never touch disk, allowing secure database access through natural language interactions.
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that connects Claude Desktop to a MongoDB database, enabling listing, finding, adding, and deleting users via natural language.
      21 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server built with the mcp-framework for developing and managing custom tools. It provides a structured foundation for building and integrating modular components like data processors and API clients into Claude Desktop.
      11 npm
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Task and project management MCP server with OAuth for Claude Desktop, Cursor bridge, semantic search, staged write approval
      14 npm
      MIT

    TDQS

    B3/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools have distinct purposes, but some overlap exists: get_audit_logs_by_category and get_audit_logs_by_date both retrieve audit logs with different filters, which could cause confusion if not carefully described. However, tools generally target clear resources like users, call transcripts, or authentication, making them mostly distinguishable.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout, such as add_user, delete_user, get_user_by_id, and update_user. This predictability aids in understanding and usage, with no deviations in style or convention across the set.

    Tool Count3/5

    With 21 tools, the count feels heavy for a JSON database server, suggesting potential over-scoping. While it covers user management, call transcripts, and audit logs, the number may overwhelm agents and could be streamlined without losing functionality.

    Completeness5/5

    The tool set provides comprehensive coverage for its inferred domains: user management (CRUD operations, authentication), call transcripts (add, get, list, search, update), and audit logs (various retrieval methods). No obvious gaps exist, supporting complete workflows from login to data management.