A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
objekts Production Desk is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
AI/VFX, CGI, motion & animation production preflight by objekts: locks, continuity, PoCs, estimates.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http objekts-production-desk-mcp https://mcp.objekts.ai/mcp
# 2 — ask your agent for something these tools do
# diagnose_production, estimate_production, create_upload_session and 4 more
objekts Production Desk costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
OBAll 1 server
objekts1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http objekts-production-desk-mcp https://mcp.objekts.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 fac
| Parameter | Type | Required | Notes |
|---|---|---|---|
| objective | string | yes | — |
| deliverables | array | yes | — |
| assets | array | no | — |
| elementRoutes | array | no | — |
| versions | array | no | — |
| changes | array | no | — |
| unknowns | array | no | — |
| readiness | object | yes | — |
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 SCENAR
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mode | string | yes | ROM for an early range; SCOPED_ESTIMATE for a defined scope; BUDGET_FIT to compare scope with a target budget; DEADLINE_FIT to evaluate schedule pressure. |
| scopeType | string | yes | WHOLE_PRODUCTION prices the complete requested finished deliverable; BOUNDED_SHOT_POST prices only named shots, scenes, VFX, or post tasks. |
| scopeDecision | string | yes | USER_EXPLICIT when the requested object is clear; SCENARIO for an explicitly labeled hypothetical; INFERRED only when scope is genuinely ambiguous, in which case no price is returned until clarified. |
| scopeEvidence | string | yes | Short evidence for the scope choice. For USER_EXPLICIT, copy a brief verbatim phrase from the user's request that identifies the priced object. |
| runtimeSeconds | yes | Final master runtime in seconds when known; null only when genuinely unknown. | |
| scopeBasis | string | yes | One concise sentence stating exactly what the estimate includes and excludes from the priced object. |
| units | array | yes | Production line items that drive the estimate. Include every material discipline/unit being priced; each item explains quantity, complexity, locks, continuity, and basis. |
| includeDepartments | array | no | Optional whitelist of departments to include when the requested estimate intentionally covers only selected disciplines. |
| deadlineDays | no | Calendar days available until delivery when known; null or omit when no deadline is supplied. | |
| targetBudgetMin | no | Lower bound of the user's target budget in RUB for BUDGET_FIT; omit when no budget floor exists. | |
| targetBudgetMax | no | Upper bound of the user's target budget in RUB for BUDGET_FIT; omit when no target ceiling is supplied. | |
| externalBidItems | array | no | Known cost exposures that require third-party bids; these remain outside the automated production range. |
| assumptions | array | no | Explicit factual assumptions used to make the estimate possible; do not invent client facts. |
| exclusions | array | no | Work explicitly outside this estimate, especially live-action, rights, media, extra versions, or unrequested disciplines. |
| versioning | object | no | Version/adaptation workload beyond the master deliverable; distinguish simple exports from recomposition and new production. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| confirmed | boolean | yes | — |
| filename | string | yes | — |
| mediaType | string | yes | — |
| sizeBytes | integer | yes | — |
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 us
| Parameter | Type | Required | Notes |
|---|---|---|---|
| confirmed | boolean | yes | — |
| contact | object | yes | — |
| brief | object | yes | — |
| selectedAssetIds | array | no | — |
| files | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| submissionId | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| confirmed | boolean | yes | — |
| submissionId | string | yes | — |
| answers | object | no | — |
| briefPatch | object | no | — |
| addedAssetIds | array | no | — |
| files | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| confirmed | boolean | yes | — |
| submissionId | string | yes | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install objekts Production Desk or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.3.
0.1.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish objekts Production Desk can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.