pipeworx_story
Pack: pipeworx-faq · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/pipeworx_story for the schema, then POST the same URL with its arguments for the data.
What Pipeworx is building and why: the vision, roadmap direction, where the catalog is deepest, a free keyless call that works right now, and where the project stands. Each section is labelled live, building or direction and dated, with its public source. Omit question for the whole story. Answers questions like “what is Pipeworx building toward?”, “where is this going?”, “why should I use Pipeworx?”. Example: pipeworx_story({ question: “what is pipeworx building?” })
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
question | string | no | Optional question about Pipeworx’s direction or purpose, e.g. “what is pipeworx building toward?”. Omit for the whole story. |
audience | string | no | Optional hint that reorders sections: agent, developer, investor, partner or press. Never changes the copy. |
Example call
Arguments
{
"question": "what is pipeworx building toward?"
}
curl
curl -X POST https://gateway.pipeworx.io/pipeworx-faq/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"pipeworx_story","arguments":{"question":"what is pipeworx building toward?"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('pipeworx_story', {
"question": "what is pipeworx building toward?"
});
More examples
{
"question": "is pipeworx funded? can I invest?",
"audience": "investor"
}
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the pipeworx-faq pack
{
"mcpServers": {
"pipeworx-faq": {
"url": "https://gateway.pipeworx.io/pipeworx-faq/mcp"
}
}
}
See Getting Started for client-specific install steps.