Mediawork MCP Server
Provides read-only access to Mediawork's public directory of post-production and distribution vendors, FAQ, blog, and subscription plans through standardized MCP tools for searching and fetching records.
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
| Tool | What it does |
|---|---|
search |
One query across the directory, FAQ and blog, returning {id, title, url} |
fetch |
Read one record in full, by an id from search |
search_facilities |
The vendor directory, filtered by service and place |
get_facility |
A vendor's full public profile |
list_services |
The service taxonomy, for resolving a filter |
list_places |
Cities, states and countries with vendors in them |
search_faq |
Published FAQ entries |
list_blog_posts / get_blog_post |
The blog |
get_plans |
Subscription 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.
Develop
The Next.js app is in deploy/. Conventions and the traps worth knowing are in
AGENTS.md.
cd deploy
nvm use 24
pnpm install
pnpm dev # http://localhost:3004/mcp
pnpm check # types + lint
pnpm test:unit # Vitest — pure logic, no network
pnpm test # Playwright smoke spec against a real MCP client
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.