Deadline MCP Server
Provides AI access to a Thinkbox Deadline 10 render farm via its Web Service REST API, exposing 18 tools for farm status, job management, and monitoring through MCP.
README
Deadline MCP Server
AI access to a Thinkbox Deadline 10 render farm via its Web Service REST API, exposed as Model Context Protocol tools. Works with Hermes, Claude, and any MCP-compatible client.
- 18 tools — 9 read + 9 write (see Tools)
- Self-contained — own venv, no host dependencies beyond Python 3.10+
- Env-configured — no secrets in the repo
Requirements
| Requirement | Detail |
|---|---|
| Python | 3.10+ |
| Deadline Web Service | deadlinewebservice running, default port 8081 |
| Network | The target machine must reach the Web Service (same host, LAN, or tailnet) |
| Credentials | A Deadline user account (username + password — not email) |
Install
git clone https://github.com/officefiction/deadline-mcp-server.git
cd deadline-mcp-server
./install.sh
install.sh creates a venv/, installs mcp + httpx, and self-tests the tool registry. Expected output ends with:
tools (18): deadline_complete_job, deadline_delete_job, ...
Version pin: the server targets the MCP 1.x Python SDK (
mcp>=1.28,<2). MCP 2.x movedFastMCP— do not upgrade past 2.x without testing.
Configure
cp .env.example .env
# edit .env:
# DEADLINE_WS_URL=http://localhost:8081 (or your host)
# DEADLINE_WS_USER=<deadline username>
# DEADLINE_WS_PASS=<deadline password>
chmod 600 .env
| Variable | Required | Default | Description |
|---|---|---|---|
DEADLINE_WS_URL |
no | http://localhost:8081 |
Base URL of the Deadline Web Service |
DEADLINE_WS_USER |
yes | — | Deadline user account (not email) |
DEADLINE_WS_PASS |
yes | — | Deadline account password |
DEADLINE_MCP_READONLY |
no | false |
true = read-only tools only (no job mutations) |
Register in Hermes
Add this block to ~/.hermes/config.yaml (path must match where you cloned):
mcp_servers:
deadline:
command: "/opt/deadline-mcp-server/venv/bin/python"
args: ["/opt/deadline-mcp-server/server.py"]
env:
DEADLINE_WS_URL: "${DEADLINE_WS_URL}"
DEADLINE_WS_USER: "${DEADLINE_WS_USER}"
DEADLINE_WS_PASS: "${DEADLINE_WS_PASS}"
enabled: true
timeout: 120
connect_timeout: 60
Then put the three DEADLINE_WS_* values in the profile's .env (chmod 600), restart the gateway, and verify:
hermes mcp test deadline # expect 18 tools discovered
Register in other MCP clients
Point any MCP client at the stdio server:
{
"command": "/opt/deadline-mcp-server/venv/bin/python",
"args": ["/opt/deadline-mcp-server/server.py"],
"env": {
"DEADLINE_WS_URL": "http://localhost:8081",
"DEADLINE_WS_USER": "...",
"DEADLINE_WS_PASS": "..."
}
}
Tools
Read (always available)
| Tool | Description |
|---|---|
deadline_farm_status |
Overall farm snapshot: workers, jobs by state, groups, pools |
deadline_list_jobs |
List jobs, filter by state / user |
deadline_get_job |
One job by ID |
deadline_job_tasks |
Tasks (chunks) of a job, per-task status |
deadline_job_reports |
Job reports / render logs |
deadline_list_workers |
Farm workers (slaves) with status + heartbeat |
deadline_list_users |
Repository users |
deadline_list_groups |
Worker groups |
deadline_list_pools |
Job pools |
Write (disabled with DEADLINE_MCP_READONLY=true)
| Tool | Description |
|---|---|
deadline_suspend_job |
Stop new tasks from starting |
deadline_resume_job |
Resume a suspended job |
deadline_requeue_job |
Re-run a job's tasks |
deadline_complete_job |
Mark a job completed |
deadline_fail_job |
Mark a job failed |
deadline_pend_job |
Hold a job until released |
deadline_release_pending_job |
Release a pended job to the queue |
deadline_set_job_priority |
Change a job's priority |
deadline_delete_job |
Delete a job |
Job states
| State | Meaning |
|---|---|
| 0 | Unknown |
| 1 | Active |
| 2 | Suspended |
| 3 | Completed |
| 4 | Failed |
| 5 | Deleted |
| 6 | Pending |
Architecture
MCP client (Hermes / Claude / ...)
│ stdio (JSON-RPC)
▼
server.py (FastMCP, mcp<2)
│ HTTP Basic auth
▼
Deadline Web Service (deadlinewebservice, :8081)
│ REST
▼
Deadline repository (render farm)
Key API facts (this server handles them automatically):
- Workers are served under
/api/slaves(not/api/workers) - Job state lives in the top-level
Statfield - Auth is a Deadline user account — the Web Service returns
401without it
Development
# Regenerate/refresh docs against the live tool registry
python3 scripts/deadline_mcp_docs.py --outline # (internal tooling, not in this repo)
License
Internal tooling for the Office Fiction project. MIT.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。