Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-jsonplaceholder fetch all posts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
JSONPlaceholder MCP — wraps JSONPlaceholder fake REST API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tool | Description |
| Fetch all fake blog posts for testing and prototyping. Returns post ID, user ID, title, and body text. |
| Fetch a single fake blog post by ID (e.g., "1"). Returns post ID, user ID, title, and body text. |
| Fetch all fake users for testing. Returns name, username, email, address, phone, website, and company details. |
| Fetch comments for a specific post by post ID (e.g., "1"). Returns comment ID, commenter name, email, and body text. |
Related MCP server: MCP-SERVER
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"jsonplaceholder": {
"url": "https://gateway.pipeworx.io/jsonplaceholder/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/jsonplaceholder/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/jsonplaceholder_get_posts \
-H 'Content-Type: application/json' \
-d '{"limit":10}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/jsonplaceholder_get_posts. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"jsonplaceholder": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-jsonplaceholder"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-jsonplaceholderIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Jsonplaceholder data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
ZenQuotes MCP — wraps ZenQuotes API (free, no auth) with a dummyjson
Rick and Morty MCP — wraps the Rick and Morty API (free, no auth)
Hosted MCP endpoint with realistic fake data for prototyping agents. 12 tools, no setup.