@pipeworx/replicate
Replicate MCP — run open models (Flux, Llama, Whisper, etc.) and manage predictions. Free trial credits on signup.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Agenten stärken
Der eigene Befehl des Herausgebers. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
npx -y @pipeworx/[email protected]Claude Code hat keinen Installationslink für einen lokalen Befehl. Kopieren Sie den Befehl unten und führen Sie ihn in einem Terminal aus.
claude mcp add pipeworx-mcp-replicate -- npx -y @pipeworx/mcp-replicate@0.2.1In einem Terminal ausführen.
{ "mcpServers": { "pipeworx-mcp-replicate": { "command": "npx", "args": [ "-y", "@pipeworx/[email protected]" ] } }}claude_desktop_config.json
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenPLATFORM_REPLICATE_KEY. BYO: ?_apiKey=….list_models(cursor?) — list public modelsmodel(owner, name) — model detailmodel_versions(owner, name) — list versionsmodel_version(owner, name, version_id) — version detailsearch_models(query) — model searchcollections() — model collectionscollection(slug) — collection detailcreate_prediction(version, input, webhook?, webhook_events_filter?, stream?) — kick off a model runprediction(id) — single prediction (poll for completion)list_predictions(cursor?) — recent predictionscancel_prediction(id) — cancel a running predictionlist_deployments(cursor?) — your deploymentsdeployment(owner, name) — deployment detailcreate_deployment_prediction(owner, name, input, webhook?, webhook_events_filter?, stream?) — run via a deployment (faster cold starts)account() — your accounthardware() — available hardware typescreate_prediction returns immediately with the prediction in starting or processing state. Poll prediction(id) until status is succeeded or failed, OR pass a webhook URL to be notified.stream=true and use the returned urls.stream SSE endpoint.https://api.replicate.com/v1
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"replicate": {
"url": "https://gateway.pipeworx.io/replicate/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/replicate/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 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/replicate_list_models \
-H 'Content-Type: application/json' \
-d '{}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/replicate_list_models. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"replicate": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-replicate"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-replicate
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
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 Replicate data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
{ "mcpServers": { "pipeworx-mcp-replicate": { "command": "npx", "args": [ "-y", "@pipeworx/[email protected]" ] } }}Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
@pipeworx/mcp Replicate läuft lokal über stdio.
Zuletzt geprüft: 2026-11-16. Replicate MCP.