Skip to main content
Glama
bitflight-devops

mcp-json-yaml-toml

by bitflight-devops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-json-yaml-toml

No user-submitted related servers found.

    Related Servers

    • json-md-studio

      kongtou-1
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that enables AI agents to securely read, write, search, and edit JSON and Markdown files through a gated permission-scoped interface with configurable access modes.
      MIT

    • peekmcp

      yulinlina
      A
      license
      Not graded
      quality
      C
      maintenance
      Zero-dependency MCP server and CLI for token-efficient inspection of local CSV/JSON/JSONL files, providing schema, samples, and paginated filtered queries to AI agents.
      MIT

    • daimonos

      beardfaceguy
      A
      license
      B
      quality
      A
      maintenance
      Agent-optimized MCP server that replaces built-in file, search, exec, and git tools with compact, structured JSON equivalents. Benchmarked 20–45% token savings for AI coding agents.
      20
      2
      MIT

    • localllm-MCP

      tsxk1san
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI to read, search, and edit local files securely without external data exposure, using local LLMs via Ollama and integrating with Open WebUI or Claude Desktop.
      -
    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.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools are distinct, but 'data' and 'data_query' both support reading data; agents may be unsure which to use for extraction queries. Descriptions help differentiate (data for CRUD, data_query for queries/transformations), but some overlap remains.

    Naming Consistency4/5

    The majority follow a consistent 'data_<verb>' pattern (convert, diff, merge, query, schema) and 'constraint_<verb>' pattern. However, the bare 'data' tool without a suffix breaks the pattern, creating a minor inconsistency.

    Tool Count5/5

    With 8 tools covering CRUD, format conversion, diff, merge, query, schema, and constraints, the count is well-scoped for the domain. Each tool serves a clear purpose without unnecessary bloat or undercoverage.

    Completeness5/5

    The tool surface provides full lifecycle support for JSON/YAML/TOML files: read, write, delete, format conversion, comparison, merging, querying, and schema operations. No obvious gaps for common use cases.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources