Skip to main content
Glama
jimpick

MCP JSON Document Collection Server

by jimpick
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to MCP JSON Document Collection Server

No user-submitted related servers found.

    Related Servers

    • database-mcp-server

      cenmiao
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for unified database access and management, supporting multiple databases with CRUD operations, transactions, metadata queries, and built-in security features.
      9 npm
      1
      MIT
    • MCP TapData Server by tapdata

      MCP TapData Serverofficial

      tapdata
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables Large Language Models to access and interact with database connections, including viewing schemas and performing CRUD operations on connected databases.
      -

    • Firestore Advanced MCP

      diez7lm
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables large language models like Claude to perform comprehensive interactions with Firebase Firestore databases, supporting full CRUD operations, complex queries, and advanced features like transactions and TTL management.
      49 npm
      4
      MIT

    • Database MCP Server

      georgi-terziyski
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides tools for connecting to and interacting with various database systems (SQLite, PostgreSQL, MySQL/MariaDB, SQL Server) through a unified interface.
      3
      -

    • SQLite MCP Server

      isaacgounton
      A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server that enables SQL operations (SELECT, INSERT, UPDATE, DELETE) and table management through a standardized interface with SQLite databases.
      7
      57 npm
      1
      ISC
    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

    B3.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. Database-level operations (create, delete, list) are separate from document-level operations (load, save, delete, query), and the cloud sync tool stands alone. The descriptions reinforce these boundaries, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with clear, descriptive names. The naming convention is uniform across all eight tools, using snake_case consistently. This predictability helps agents understand and select tools efficiently.

    Tool Count5/5

    With 8 tools, the count is well-scoped for managing JSON document databases and documents. It covers core operations without being overwhelming, and each tool serves a distinct, necessary function in the domain. This aligns with typical server tool counts of 3-15.

    Completeness4/5

    The tool set provides strong coverage for CRUD operations on both databases and documents, including querying. A minor gap exists in lacking an update operation for documents (e.g., update_json_doc_in_db), but agents can work around this by using save_json_doc_to_db as a replacement. Overall, it supports core workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources