Mediawork

io.mediaworkPublished by mediawork.ioOfficial publisherv0.1.1Updated Oct 28, 2026

Search Mediawork's directory of post-production and distribution vendors, plus FAQ and plans.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Read-only access to Mediawork's public directory of post-production and distribution vendors, plus its FAQ, blog and subscription plans.

What you can do
  • Search everything Mediawork publishes and fetch a record in full by id
  • Browse the vendor directory by service category and place, then read a vendor's full profile with services, creatives, rooms and equipment
  • Look up the service taxonomy and the places that have listed vendors
  • Search the published FAQ, with or without a query
  • List blog posts newest first and read a single post as markdown
  • Retrieve subscription plans, their prices in a chosen currency, and a feature comparison
When to use it
Useful when someone is researching post-production, distribution or creative vendors by location or service, or wants Mediawork's published FAQ, blog content and pricing while planning a project.
Requirements
A remote Streamable HTTP endpoint; no authentication, sign-up, API key or environment variables are needed on the client side. Network access to the Mediawork endpoint is required.
Before you install
Read-only by design: it exposes only publicly published directory, FAQ, blog and plan data, with no write path. Queries and lookups are sent to Mediawork's servers, and returned records carry canonical mediawork.io URLs.

Installation

In SourceWeft

  1. Open Mediawork in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.mediawork%2Fmediawork/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mediawork": {
      "type": "http",
      "url": "https://mcp.mediawork.io/mcp"
    }
  }
}

README

Mediawork MCP server

Read-only Model Context Protocol access to everything Mediawork publishes publicly: the directory of post-production and distribution vendors, the FAQ, the blog, and subscription plans.

Connector URL: https://mcp.mediawork.io/mcp — Streamable HTTP, no authentication, no sign-up.

Listed in the official MCP Registry as io.mediawork/mediawork.

Connect it

Claude Code:

sh
claude mcp add --transport http mediawork https://mcp.mediawork.io/mcp

Anything that takes a JSON config:

json
{    "mcpServers": {        "mediawork": {            "type": "http",            "url": "https://mcp.mediawork.io/mcp"        }    }}

Tools

ToolWhat it does
searchOne query across the directory, FAQ and blog, returning {id, title, url}
fetchRead one record in full, by an id from search
search_facilitiesThe vendor directory, filtered by service and place
get_facilityA vendor's full public profile
list_servicesThe service taxonomy, for resolving a filter
list_placesCities, states and countries with vendors in them
search_faqPublished FAQ entries
list_blog_posts / get_blog_postThe blog
get_plansSubscription plans and pricing

search + fetch are the generic pair some clients require; the dedicated tools give richer, filterable results where a client can use them.

Directory questions usually chain: list_services or list_places to resolve a filter, then search_facilities, then get_facility. Every result carries its canonical www.mediawork.io URL so an agent can cite the source.

Read-only, structurally

The deployment holds exactly one environment variable, APP_API_URL, and every byte it serves comes from https://app.mediawork.io/api/www/* — the same public contract the marketing site consumes. There are no database credentials and no write path, so "read-only" is a property of the deployment's shape rather than a promise in a comment.

Contributing

Setup, the test commands and the house conventions are in CONTRIBUTING.md.

Licence

MIT © Screen Arts Limited.

Source: README.md at commit cf0b938

Tools

10

list_services

List service categories

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 a question is about a kind of work.

Parameterslocale

list_places

List directory 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.

Parameterslocale

search_facilities

Search the vendor directory

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 `query` naming a place is treated as one anyway, and the response reports it as `resolvedPlace`. Results are paginated; when `hasMore` is true, call again with the returned `nextOffset`.

Parametersplacequerylocaleoffsetservice

get_facility

Get a vendor profile

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 returned by search_facilities.

ParameterslocalecompanySlugrequiredfacilitySlugrequired

search_faq

Search the Mediawork 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.

Parametersquerylocale

list_blog_posts

List blog posts

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

Parameterslocale

get_blog_post

Read a blog post

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

Parametersslugrequiredlocale

get_plans

Get subscription plans and pricing

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.

Parameterslocalecurrency

fetch

Fetch a Mediawork record

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

Parametersidrequired

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts