Mediawork MCP server

• Registry nameio.mediawork/mediaworkverified in the MCP registry

The registry name sits under mediawork.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools10
• Server calls itselfmediawork
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 141 ms.

• Its tools do none of the product's use cases we checked: Turn client enquiries into quotes and awarded jobs; Schedule crews, rooms and resources across facilities; Track actual costs against quotes and bill them.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• What an agent can do with it0 of 3 use cases
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer478 ms
• Space in an agent's context≈ 1,407 tokensthe definitions of all its tools (10), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 10 of 10

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_services

  The service categories vendors on Mediawork offer, such as Editorial, Sound Post or Visual Effects. Each has a uuid — pass it as `service` to search_facilities to filter the directory to vendors offering that service. Call this first when…

• list_places

  Cities, states and countries that have at least one vendor listed, with a count of how many. Use a place `slug` as the `place` argument to search_facilities.

• search_facilities

  Search publicly listed post-production facilities, distribution vendors and creative companies. Filter by free text, by place slug (from list_places) and by service uuid (from list_services). To find vendors somewhere, prefer `place`; a…

• get_facility

  The full public profile for one vendor: services offered, creatives on the team and what each of them does, production types, rooms and spaces, equipment by make and model, and addresses. Takes the `companySlug` and `facilitySlug` pair…

• search_faq

  Mediawork's published FAQ, grouped by category. With a query, returns matching questions and their answers; without one, returns every question so you can pick which to search for.

• list_blog_posts

  Published posts from the Mediawork blog, newest first. Use get_blog_post with a returned `slug` to read one in full.

• get_blog_post

  The full body of one published blog post, as markdown.

• get_plans

  Mediawork's subscription plans: what each includes, and its prices, plus `comparison`, a feature-by-feature table of every plan. Prices are published in several currencies — pass `currency` to return just one.

• search

  Search everything Mediawork publishes — vendor directory listings, FAQ entries and blog posts — and return matching records as {id, title, url}. Pass an `id` to `fetch` to read one in full. If your client supports them, the dedicated…

• fetch

  Retrieve the full contents of one record by the `id` returned from `search`.