Back to Browse

Mediawork MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://mcp.mediawork.io/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (2 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: 3 highly-trusted packages.

10 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-mediawork-mediawork": {
      "url": "https://mcp.mediawork.io/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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.

Reviews

No reviews yet

Be the first to review this server!