Skip to main content
Glama
akuratipullaiah

JSON MCP Server

by akuratipullaiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to JSON MCP Server

No user-submitted related servers found.

    Related Servers

    • Fetch JSONPath MCP

      ackness
      A
      license
      A
      quality
      B
      maintenance
      Enables efficient extraction of specific data from JSON APIs using JSONPath patterns, reducing token usage by up to 99% compared to fetching entire responses. Supports single and batch operations for both JSON extraction and raw text retrieval from URLs.
      4
      33 PyPI
      4
      MIT

    • JSON MCP Server

      GongRzhe
      A
      license
      C
      quality
      F
      maintenance
      A Model Context Protocol server implementation that enables LLMs to query and manipulate JSON data using JSONPath syntax with extended operations for filtering, sorting, transforming, and aggregating data.
      2
      36 npm
      90
      MIT

    • mcp-json

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides tools to validate, format, and query JSON strings via MCP. Enables AI agents to work with JSON data without needing keys or internet.
      12 npm
      MIT

    • MCP JSON Lens

      KaryawanSurga
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets agents and CLI users inspect the shape of large JSON and JSONL files and extract exactly the values they need using jq-like expressions, returning compact bounded results instead of flooding context.
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.9/5.0

    Scored across 2 tools

    Disambiguation3/5

    Both tools operate on JSON data to extract subsets, and 'filter' is essentially a restricted form of JSONPath querying, so an agent could reasonably pick either for a filtering need. The descriptions do differentiate them by mechanism (JSONPath syntax vs. conditions), which helps, but the boundary is fuzzy.

    Naming Consistency5/5

    Both names are single lowercase verbs (query, filter) following the exact same convention. There is no mixing of styles or verb forms.

    Tool Count3/5

    Two tools is thin for a server whose domain (JSON manipulation) typically involves parsing, validation, transformation, and mutation. It is defensible for a narrowly scoped read-only query server, but borderline.

    Completeness2/5

    The surface offers only read/extract operations; there is no parsing, validation, path construction, or any modification of JSON (set/merge/delete). Agents needing to inspect or transform JSON beyond querying and filtering will hit dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources