@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.
接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
npx -y @pipeworx/[email protected]Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
claude mcp add pipeworx-mcp-replicate -- npx -y @pipeworx/mcp-replicate@0.2.1在終端機中執行。
{ "mcpServers": { "pipeworx-mcp-replicate": { "command": "npx", "args": [ "-y", "@pipeworx/[email protected]" ] } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
PLATFORM_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]" ] } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
@pipeworx/mcp Replicate 透過 stdio 在本機執行。
上次檢查時間:2026-11-16。 Replicate MCP.