media-gen-mcp
MCP server that enables AI assistants to generate images and videos on demand using free-tier providers like Agnes AI, Cloudflare Workers AI, Hugging Face, and Google Gemini, with tools for creating media, polling async jobs, and listing providers.
README
media-gen-mcp
A personal MCP server that gives OpenCode the ability to generate images and videos mid-conversation — invoked as a tool, not a separate app — using free-tier AI media providers.
Built for generating visual assets and video clips for my own websites, apps, and projects, without paying for API access.
Providers
| Provider | Capabilities | Trust level | Status |
|---|---|---|---|
| Agnes AI | image, video | untrusted |
active |
| Cloudflare Workers AI | image | untrusted |
active |
| Hugging Face Inference API | image | untrusted |
active |
| Google Gemini | image | trusted |
unavailable — free-tier image generation quota is policy-set to 0 as of Aug 2026; requires a billed Google Cloud project. Implemented and ready — flip status: active in config.yaml once a working key exists |
trust_level determines how a provider's responses are handled: untrusted providers are unofficial/self-parsed and go through full schema validation before anything else happens; trusted providers use an official SDK assumed to already validate its own response shape. See ARCHITECTURE.md for the full reasoning.
Providers can each have multiple named accounts (e.g. multiple API keys for the same provider) — selectable explicitly per call, no auto-rotation. Some accounts need more than one secret: Cloudflare requires an account ID alongside its API token (account_id_env in config.yaml).
Setup
This repo isn't published to a public remote yet, so <repository-url> is a placeholder — substitute the URL you actually clone from, don't copy it verbatim. The explicit media-gen-mcp target keeps the following cd correct: a bare git clone defaults to a directory named after the repository, so cd media-gen-mcp only holds if the repo happens to be named media-gen-mcp.
git clone <repository-url> media-gen-mcp
cd media-gen-mcp
python -m venv .venv
.venv/bin/pip install -e .
Create a .env file in the project root with whichever providers you plan to use:
AGNES_API_KEY=...
CLOUDFLARE_API_TOKEN=...
CLOUDFLARE_ACCOUNT_ID=...
HUGGING_FACE_API_TOKEN=...
GEMINI_API_KEY=... # optional — provider is currently marked unavailable
config.yaml maps each of these to a named account per provider — see the file itself, or ARCHITECTURE.md's Config section, for the full schema (multiple accounts per provider, per-provider defaults, hardening limits).
Register with OpenCode
Add to ~/.config/opencode/opencode.json (global, so it's available from any project):
{
"mcp": {
"media-gen-mcp": {
"type": "local",
"command": [
"/absolute/path/to/media-gen-mcp/.venv/bin/python",
"/absolute/path/to/media-gen-mcp/server.py"
]
}
}
}
Both paths must be absolute. This is a global config spawned from whatever directory you happen to be working in when OpenCode starts — a relative path only happens to work if you're inside this repo, and silently breaks everywhere else.
Confirm it's connected:
opencode mcp list
Tools exposed
generate_image(prompt, provider?, account?, project_dir?, output_path?, ...)— generates an image, returns the saved file path.generate_video(prompt, provider?, account?, project_dir?, output_path?, ...)— starts an async video job (Agnes only), returns ajob_idto poll.check_video_job(job_id)— checks/advances a video job; downloads and saves the file once complete.list_providers()— reports configured providers, their status, capabilities, and accounts.
Where a file is saved follows this priority: an explicit output_path → under project_dir/ai-media/ if given → the configured default output directory otherwise.
Project docs
ARCHITECTURE.md— the full design: provider abstraction, trust-level validation, async video job handling, accounts, config schema, and the current state of the system.progress-tracker.md— current build status, the task list, and the incidents/lessons that shaped the decisions above.AGENTS.md— standing conventions for AI coding agents working on this codebase (testing discipline, hard rules, definition of done).
License
Released to the public domain under The Unlicense — see UNLICENSE.md. Free to copy, modify, and distribute; provided without warranty.
Status
Personal v1, built for a single user. Secrets live in a repo-adjacent .env; not currently packaged for distribution to other users or other machines (see ARCHITECTURE.md's "Future: distribution" note for what that would need). Deterministic image editing (background removal, overlays, compositing) is explicitly out of scope — this project only generates media.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。