@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 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
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인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
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.
실행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]" ] } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
@pipeworx/mcp Replicate은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-11-16. Replicate MCP.