Replicate Anywhere
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAX_POLL_TIME | No | Maximum time (ms) to wait for predictions before returning async status | 300000 |
| REPLICATE_API_TOKEN | Yes | Your Replicate API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-modelsA | IMPORTANT: This tool MUST be called FIRST before asking any clarifying questions about model names. When a user mentions ANY model name (exact, fuzzy, or incomplete like "flux", "stable diffusion", "nano banana pro"), immediately search for it. Do NOT ask the user to confirm model names - search first, then pick the best match from results based on name similarity and run count. Only ask for clarification if the search returns zero results. |
| get-model-infoA | Get detailed information about a specific Replicate model including its input parameters schema. Call this AFTER search-models to get parameter details for the best matching model before running it. |
| run-modelA | Run a prediction on any Replicate model. WORKFLOW: If the user provides a fuzzy model name, first call search-models to find the exact model identifier, then call get-model-info to understand required parameters, then call this tool. |
| list-modelsA | List public models on Replicate. Use search-models instead when the user mentions a specific model name - this tool is only for browsing all available models without a specific query. |
| check-predictionA | Check the status of a running prediction. Use this if a previous run-model call returned a prediction_id with status "processing". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct role in the model-running workflow: search vs browse, get info, run, and check status. There is no overlap between search-models and list-models because the former is for specific queries and the latter for browsing.
All tool names use a consistent verb_noun pattern in snake_case: search-models, get-model-info, run-model, list-models, check-prediction. This makes the API predictable and easy to navigate.
With 5 tools, the server is well-scoped for its purpose of running Replicate models. Each tool covers a necessary step in the workflow without unnecessary bloat.
The core lifecycle of searching, inspecting, running, and checking predictions is fully covered. A minor gap is the lack of a cancel-prediction tool, but this is not essential for the primary workflow.