segment_source_destinations
Pack: segment · 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/segment_source_destinations for the schema, then POST the same URL with its arguments for the data.
Return bounded destinations connected to one Segment source with connection IDs, destination definitions, settings, and enabled state. Answers where a source sends its customer data.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
source_id | string | yes | Segment source ID |
Example call
Arguments
{
"_apiKey": "your-segment-public-api-token",
"source_id": "qQEHquLrjRDN9j1ByrChyn",
"limit": 25
}
curl
curl -X POST https://gateway.pipeworx.io/segment/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"segment_source_destinations","arguments":{"_apiKey":"your-segment-public-api-token","source_id":"qQEHquLrjRDN9j1ByrChyn","limit":25}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('segment_source_destinations', {
"_apiKey": "your-segment-public-api-token",
"source_id": "qQEHquLrjRDN9j1ByrChyn",
"limit": 25
});
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 segment pack
{
"mcpServers": {
"segment": {
"url": "https://gateway.pipeworx.io/segment/mcp"
}
}
}
See Getting Started for client-specific install steps.