Filtrix AI MCP
Generate marketing images and short videos from your coding agent via Filtrix without leaving the MCP toolchain.
Overview
Filtrix AI MCP is a Build-phase MCP server that lets agents generate images and videos via Filtrix using a Bearer-authenticated streamable HTTP remote.
What is this MCP server?
- Remote MCP at https://mcp.filtrix.ai/ with required Bearer Authorization header
- Image and video generation exposed to agents through MCP (portal: https://agent.filtrix.ai/)
- Catalog version 0.1.0; website https://www.filtrix.ai/
- Secret MCP_API_KEY passed as Bearer token in client MCP headers
- Streamable-http transport for hosted agent clients
- 1 required secret header: Authorization (Bearer MCP_API_KEY)
- 1 streamable-http remote at https://mcp.filtrix.ai/
What problem does it solve?
You waste context switching between your agent and a separate image or video tool whenever you need launch visuals.
Who is it for?
Solo builders who want Claude or Cursor to draft visuals and short videos while iterating on product and marketing pages.
Skip if: Teams that require fully offline generation, fine-grained local GPU pipelines, or no third-party media API keys.
What do I get? / Deliverables
After adding the MCP remote and API key, your agent can request Filtrix-generated media as part of build and content workflows.
- Configured Filtrix MCP remote with secret header
- Agent-callable image and video generation through Filtrix
Recommended MCP Servers
Journey fit
How it compares
Hosted image/video generation MCP, not an in-repo design skill or screenshot browser automation tool.
Common Questions / FAQ
Who is Filtrix AI MCP for?
Builders and marketers using AI coding agents who want Filtrix image and video generation available as an MCP tool with an API key.
When should I use Filtrix AI MCP?
Use it while building or polishing launch assets when the agent should generate or refresh images and videos without manual export steps.
How do I add Filtrix AI to my agent?
Register https://mcp.filtrix.ai/ as a remote MCP server, set the Authorization header to Bearer plus your MCP_API_KEY from Filtrix, then enable the server in your client.