# Objekts Production Desk MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.objekts.mcp%2Fproduction-desk
Registry id: `mcp-registry/ai.objekts.mcp/production-desk`
Status: live (checked 2026-10-26T23:26:18.827Z)

## Measurements (30 days)

- Uptime: 99.84%
- Checks: 3928
- Outages (90 days): 3

## Install

```json
{
  "mcpServers": {
    "objekts-production-desk-mcp-server": {
      "type": "http",
      "url": "https://mcp.objekts.ai/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http objekts-production-desk-mcp-server https://mcp.objekts.ai/mcp
```

## Tools (7)

- `create_upload_session`: Use this only when the user explicitly wants an original production file delivered to objekts and the current host cannot pass that original file natively. It c
- `delete_production_brief`: Use this only when the user explicitly asks to delete a production submission from objekts storage. This removes the stored submission record and is destructive
- `diagnose_production`: Use the objekts Production Desk production-diagnosis engine for production-heavy visual work before proposing execution. It checks reference authority, hard loc
- `estimate_production`: Return a directional RUB production range and timeline only when the user explicitly asks about price, cost, budget, quote, or budget fit. This tool is read-onl
- `get_production_brief_status`: Use this when the user wants the current human-review status, producer questions or available human estimate for a production brief previously submitted to obje
- `submit_production_brief`: Use this only after the user explicitly confirms that the prepared production brief, one reply channel (email or Telegram), and selected files should be sent to
- `update_production_brief`: Use this only after the user explicitly confirms that clarifications, scope updates, newly supplied asset references or attached production files should be sent

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
