# objekts Production Desk [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/peach420fuzz/objekts-production-desk  
**GitHub Stars:** 0  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/objekts-production-desk

## Description
Production planning, feasibility and directional estimates for commercial visual work, built and operated by objekts, with optional explicit human review.

## Tools
Capabilities this server exposes over MCP:

- **diagnose_production** — Use the objekts Production Desk production-diagnosis engine for production-heavy visual work before proposing execution. It checks reference authority, hard locks, truth-layer routing, asset fitness, continuity, versioning, revision impact, readiness and the highest-value proof-of-concept. It does not estimate price, collect contact data, upload files or send anything externally. Populate only facts available from the user's current request/files; mark unknowns explicitly instead of inventing production facts. After the call, use visibleVerdict as the complete default answer: do not add a generic checklist or extra recommendations unless the user explicitly asks for a broader audit.
- **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-only, non-binding, and never collects contact details or submits a brief. Choose WHOLE_PRODUCTION for a finished deliverable and BOUNDED_SHOT_POST for named shots/scenes/post work; use INFERRED when that scope is genuinely ambiguous, or SCENARIO for a clearly labeled hypothetical. For production diagnosis without pricing, use diagnose_production instead.
- **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 creates a short-lived private upload URL. Do not use it merely to analyze files that are already available in the conversation.
- **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 objekts for human production review. A contactless human-review submission is not allowed because the producer must be able to answer the user. When the host already has the files, pass them through the files field instead of making the user upload them again. Do not use it for local analysis, estimation, or when the user has said not to send anything.
- **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 objekts. It does not modify the submission.
- **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 to an existing objekts human review. When ChatGPT already has a requested file, pass it through the files field rather than creating a second upload. Do not use it to change a brief that exists only in the current conversation.
- **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.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

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

## Documentation

## What objekts Production Desk does

objekts Production Desk, also identified as KOUNT by objekts, brings an AI-native visual-production preflight and planning workflow into MCP-compatible agent clients. It is intended for commercial visual work involving generative video, AI/VFX, CGI or 3D, motion, animation, compositing and related production units. Physical live-action shoots are outside the stated scope.

The service examines whether a proposed production is sufficiently defined to move toward execution. Its review covers reference authority, fixed visual requirements, truth-layer routing, asset fitness, continuity, versioning, revision impact, readiness and the most useful proof of concept. It does not generate images or video, and it is not an autonomous production agency.

## How it works

The hosted MCP endpoint is available at `https://mcp.objekts.ai/mcp`. Agents call specialized tools over MCP and should use facts from the active request or available files rather than inventing production details. Unknowns are marked as unknown during diagnosis.

Diagnosis and pricing are separate paths. `diagnose_production` is for production readiness and execution risk. `estimate_production` is reserved for explicit questions about price, cost, budget, quote or budget fit. It returns a non-binding directional RUB range and timeline. A finished deliverable should use whole-production scope; named shots, scenes or post work should use bounded-shot/post scope. Ambiguous scope can be inferred, while hypothetical planning can be labeled as a scenario.

The service translates conventional production language into AI/VFX, CGI, motion and compositing work units rather than crew, location or shoot-day costs. The diagnosis result's `visibleVerdict` is intended to be treated as the complete default response unless the user asks for a broader audit.

## Setup and configuration

Connect an MCP client to the remote endpoint:

```text
https://mcp.objekts.ai/mcp
```

An installation and test flow is provided at `https://mcp.objekts.ai/install`, with a live test at `https://mcp.objekts.ai/test`. The service supports MCP protocol version 2025-11-25. Clients that require protocol version 2026-07-28 receive an HTTP 400 response, so protocol fallback or a compatible client configuration may be necessary.

The repository also documents imports for Yandex AI Studio and project-level configurations for Yandex SourceCraft Code Assistant and Alibaba Qwen Code. Those configurations preserve confirmation for actions beyond read-only diagnosis.

## Tools and capabilities

- `diagnose_production` checks references, locks, asset fitness, continuity, versioning, revision impact, readiness and proof-of-concept priority.
- `estimate_production` returns a directional, read-only RUB range and timeline when the user explicitly requests pricing or budget guidance.
- `create_upload_session` creates a short-lived private upload URL when the host cannot pass an original production file natively.
- `submit_production_brief` sends a prepared brief and selected files to objekts for human review after the user confirms the brief, files and one reply channel: email or Telegram.
- `get_production_brief_status` retrieves the status of a previously submitted brief, including producer questions or an available human estimate.
- `update_production_brief` sends confirmed clarifications, scope changes, asset references or files to an existing human review.
- `delete_production_brief` removes a stored submission record after the user explicitly requests the destructive action.

Files already available to the host should be passed directly through the relevant file field instead of triggering a second upload. Upload sessions are for delivery of original files, not for analyzing files already present in the conversation.

## Limitations and notes

Pricing is directional and non-binding. The service does not collect contact details during diagnosis or estimation, upload files automatically, send external messages without confirmation, or submit contactless human-review requests. A producer must have either an email or Telegram reply channel before a brief is submitted.

The backend is hosted remotely; the public repository contains integration manifests, skills and documentation rather than evidence that the backend is open source. The human-review workflow is separate from the read-only preflight path, and submitting a brief does not imply automatic acceptance by the studio.

_Full upstream README: https://allmcps.com/mcp/objekts-production-desk/readme_

