jsonplaceholder-mcp
Related Servers
Alternatives to jsonplaceholder-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceWraps the JSONPlaceholder fake REST API to enable testing and prototyping with CRUD operations on posts, comments, and other resources via MCP.3 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables interaction with the JSONPlaceholder REST API for managing posts, comments, and users through MCP tools.-
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that teaches how to expose documentation as a resource and safe operations as tools, using JSONPlaceholder as the data source.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that provides tools to read JSON files and query data using jsonPath expressions.-
- AlicenseBqualityDmaintenanceAn MCP server that retrieves product data from the DummyJSON API, supporting filtering by various parameters like ID, title, category, brand, price and rating.18 npmISC
- AlicenseAqualityAmaintenanceAn MCP server that returns random JSON things — people, words, values, coordinates, and an always-empty list.4MIT
TDQS
Scored across 7 tools
Each tool targets a distinct resource and action: get_posts, get_users, get_comments, get_todos, create_post, update_post, delete_post. There is no overlap in purpose or behavior, and the descriptions make the boundaries clear.
All tool names follow a consistent verb_noun pattern: get_ for reads and create_/update_/delete_ for mutations. The pattern is uniform and predictable across the entire set.
With 7 tools, the server is well-scoped for a JSONPlaceholder demo. Each tool covers a core operation without unnecessary bloat, fitting comfortably in the ideal 3-15 tool range.
Posts have full CRUD coverage (get, create, update, delete), but users, comments, and todos are read-only. This leaves obvious gaps for mutating those resources, though the core post workflow is complete.