
Wraps loripsum.net to generate placeholder text on demand, no authentication required. Part of the Pipeworx gateway ecosystem that bundles 673+ data sources behind a single MCP endpoint. You can add it standalone or connect to the full gateway for broader access. Includes an ask_pipeworx tool that lets you make natural language requests instead of calling specific functions. Useful when you need programmatic access to Lorem Ipsum generation in your AI workflows, though the source documentation doesn't detail which specific operations or parameters are exposed. Runs over streamable HTTP, so no local process needed.
Lorem MCP — placeholder text, generated locally.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
generate_paragraphs | Generate placeholder text paragraphs for mockups and layout testing. Returns plain text without formatting. |
generate_with_options | Generate formatted placeholder text with headers, code blocks, and lists (HTML). Specify which elements to include: headers, code blocks, unordered lists, ordered lists. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"lorem": {
"url": "https://gateway.pipeworx.io/lorem/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/lorem/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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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 Lorem data" })
The gateway picks the right tool and fills the arguments automatically.
MIT