mcpField
M
Mediawork

Mediawork

Remote
mediawork.ioBusiness & Marketing0Updated 1w ago

About Mediawork

Mediawork is a read-only MCP server for searching its public vendor directory, FAQ, blog, and subscription plans. Dedicated filters help clients find post-production and distribution vendors by service and location, with canonical source URLs.

Key features

  1. 01Search the directory, FAQ, and blog
  2. 02Filter vendors by service and location
  3. 03Read public vendor profiles
  4. 04Look up service types and places
  5. 05Retrieve blog posts and plans

Use cases

  1. 01Find vendors for a service or location
  2. 02Look up published Mediawork FAQs
  3. 03Review blog posts and subscription plans

MCP support

The server offers read-only access over Streamable HTTP without authentication. It exposes search, vendor-directory, FAQ, blog, and plan tools to MCP clients.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.mediawork.io/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

10
ParameterTypeRequiredDescription
localestringNoTwo-letter language code (en, fr, es, pt, it, de, nl, pl, th, hi, ko, ja). Defaults to English.

Details

From the project 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:

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

Anything that takes a JSON config:

{
    "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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.