list_packs
Pack: pipeworx-catalog · Endpoint: https://gateway.pipeworx.io/pipeworx-catalog/mcp
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/list_packs for the schema, then POST the same URL with its arguments for the data.
Browse all available Pipeworx packs. Returns pack names, categories, tool counts, and gateway URLs. Use to discover data sources or explore what’s available.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
category | string | no | Free-text filter matched against pack slugs, descriptions, and tool names/descriptions — not a fixed taxonomy (e.g. “weather”, “pesticide”, “sec filings”). Omit to list everything. |
Example call
Arguments
{}
curl
curl -X POST https://gateway.pipeworx.io/pipeworx-catalog/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_packs","arguments":{}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('list_packs', {});
More examples
{
"category": "Finance"
}
Response shape
Always returns: total_packs, gateway, packs
| Field | Type | Description |
|---|---|---|
total_packs | number | |
gateway | string | Gateway base URL |
packs | array |
Full JSON Schema
{
"type": "object",
"description": "The catalog of MCP packs this gateway serves.",
"properties": {
"total_packs": {
"type": "number"
},
"gateway": {
"type": "string",
"description": "Gateway base URL"
},
"packs": {
"type": "array",
"items": {
"type": "object",
"properties": {
"slug": {
"type": "string"
},
"name": {
"type": "string"
},
"description": {
"type": "string"
},
"tool_count": {
"type": "number"
},
"gateway_url": {
"type": "string"
}
},
"required": [
"slug",
"name",
"gateway_url"
]
}
}
},
"required": [
"total_packs",
"gateway",
"packs"
]
}
Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"pipeworx-catalog": {
"url": "https://gateway.pipeworx.io/pipeworx-catalog/mcp"
}
}
}
See Getting Started for client-specific install steps.