EvaFarm — GPU render nodes
ru.evafarmstorev1.0.0Updated Oct 8, 2026
Render farm GPU nodes: live availability, installed DCC apps and engines, per-minute cost.
Overview
AI-generated overview
Lets an assistant check a GPU render farm's live node availability, installed DCC apps and engines, and per-minute cost.
- What it does
- This remote MCP server exposes a GPU render farm to an assistant. According to its registry description, it reports live availability of render nodes, which DCC applications and render engines are installed, and the per-minute cost. No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Consider it when you want an assistant to look up render farm capacity, check whether a specific application or engine is available, or compare per-minute pricing before submitting rendering work.
- Requirements
- It is a remote streamable HTTP endpoint at the provider's site; nothing needs to be installed locally. The manifest declares no authentication, no environment variables and no headers, but the provider may still require an account or credentials in practice.
Before you install
The manifest declares no authentication, so it is unclear what data or actions the endpoint exposes; verify with the provider before connecting. Rendering is typically billed per minute, so check pricing and any spending limits. No tool list is published, so confirm what the server can actually do.
Installation
In SourceWeft
- Open EvaFarm — GPU render nodes in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"evafarm": {
"type": "http",
"url": "https://evafarmstore.ru/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 8, 2026

