json-shaper-lite
Related Servers
Alternatives to json-shaper-lite
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceBidirectional CSV ↔️ JSON ↔️ Markdown transformer exposed as an HTTP-based MCP server, enabling format conversion through natural language.46 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables converting Markdown and HTML tables into structured JSON records with automatic column type inference and format normalization. It also offers supporting web-agent primitives such as DOM semantic pruning, form field auto-mapping, and execution trajectory evaluation, all via a zero-dependency MCP server.7MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to convert ASCII/OCR text dumps, aligned spacing, and CSV/TSV data into clean GitHub Flavored Markdown tables and typed JSON deterministically.7-
- AlicenseAqualityBmaintenanceLocal MCP server for plain Markdown notes: list, read, create and search notes, and manage their tasks and Kanban board (move cards, toggle tasks, set start and due dates).9103MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents and MCP clients to heuristically parse multi-column document dumps, aligned spacing, and CSV/TSV input, converting them into clean GitHub Flavored Markdown tables and typed JSON. Runs fully offline on the Python standard library with zero external dependencies, returning deterministic results without LLM round-trips.-
- AlicenseBqualityDmaintenanceLocal-first MCP server for Obsidian vaults with 66 tools for reading, writing, searching, and managing notes, tasks, graphs, and more. Works without Obsidian running and requires no plugins.66MIT
This server cannot be deployed
TDQS
Scored across 2 tools
The two tools are cleanly separated by input source: pasted text vs. a file on disk, and each description explicitly cross-references the other as the alternative. There is no realistic way to confuse them, and the shared format/output semantics reinforce rather than blur the boundary.
Both names follow the exact same shape_<source>_to_json pattern, differing only in the source noun (text vs. file). Verb, ordering and casing (snake_case) are perfectly consistent.
Two tools is on the thin side, but the server is explicitly scoped as 'lite' and the pair covers its stated purpose without filler. It sits at the borderline where the surface is minimal but not arbitrary.
Text and file inputs are both covered, with auto/kv/csv/markdown formats and a consistent output envelope, so common shaping workflows have no dead ends. Minor gaps exist (no reverse direction, no writing results back to a file, no JSON-to-table), but these are outside the declared narrow scope.