repositories
Pack: repology · 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/repositories for the schema, then POST the same URL with its arguments for the data.
List all package repositories indexed by Repology (distros, BSDs, language ecosystems, etc.) with their names, family, and active/total package counts.
Example call
Arguments
{}
curl
curl -X POST https://gateway.pipeworx.io/repology/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"repositories","arguments":{}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('repositories', {});
Response shape
Always returns: items, count
| Field | Type | Description |
|---|---|---|
items | array | Array of repositories with stats and status |
count | integer | Number of items returned. |
Full JSON Schema
{
"type": "object",
"properties": {
"items": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Repository name"
},
"state": {
"type": "string",
"description": "Repository status"
},
"num_packages": {
"type": "number",
"description": "Number of packages in repository"
},
"num_problems": {
"type": "number",
"description": "Number of problems in repository"
},
"num_maintainers": {
"type": "number",
"description": "Number of maintainers in repository"
}
}
},
"description": "Array of repositories with stats and status"
},
"count": {
"type": "integer",
"description": "Number of items returned."
}
},
"required": [
"items",
"count"
]
}
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 repology pack
{
"mcpServers": {
"repology": {
"url": "https://gateway.pipeworx.io/repology/mcp"
}
}
}
See Getting Started for client-specific install steps.