Databases

mediawork.io

Provides access to a database of post-production facilities, vendors, and related information.

1 endpoint10 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://mcp.mediawork.io/mcp

No auth detected

MCP server metadata

Name: mediawork
Version: 0.1.0

Capabilities

tools.listChanged

Server instructions

Read-only access to everything Mediawork publishes: the vendor directory of post-production facilities, distribution vendors and freelance creatives; the FAQ; the blog; and subscription plans and pricing. Directory questions usually chain: list_services or list_places to resolve a filter, then search_facilities, then get_facility for the full profile. Every result carries a www.mediawork.io URL — cite it.

Known tools 10

list_services

The service categories vendors on Mediawork offer, such as Editorial, Sound Post or Visual Effects.

Potential side effects

list_places

Cities, states and countries that have at least one vendor listed, with a count of how many.

Inferred read-only

search_facilities

Search publicly listed post-production facilities, distribution vendors and creative companies.

Potential side effects

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, and addresses.

Inferred read-only

search_faq

Mediawork's published FAQ, grouped by category.

Inferred read-only

list_blog_posts

Published posts from the Mediawork blog, newest first.

Inferred read-only

get_blog_post

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

Potential side effects

get_plans

Mediawork's subscription plans: what each includes, and its prices.

Inferred read-only

search

Search everything Mediawork publishes — vendor directory listings, FAQ entries and blog posts — and return matching records as {id, title, url}.

Inferred read-only

fetch

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

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mediawork]
url = "https://mcp.mediawork.io/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: mediawork
Remote MCP URL: https://mcp.mediawork.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "mediawork",
  "transport": "streamable-http",
  "url": "https://mcp.mediawork.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for mediawork.io was fetched 2026-07-31T16:04:37.863Z and is being refreshed.

Trust status Trusted

mediawork.io is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.