João Henrique
b541f502ba
- Adicionado estrutura completa do projeto - Configurado MCP server para Premiere Pro - Adicionado documentação e skills - Configurado Gitignore para o projeto
2.2 KiB
Executable File
2.2 KiB
Executable File
MCP for Adobe Premiere Pro Marketing Assets
The approved launch set lives in landing/public/marketing/. Use the original v1 assets for public product marketing.
| Asset | Intended use | Dimensions |
|---|---|---|
premiere-pro-mcp-mark-v1.png |
Navigation, app icon, avatar, and organization logo | 1254 × 1254 PNG with transparency |
premiere-pro-mcp-campaign-hero-v1.png |
Landing hero, launch articles, and wide campaign placements | 1672 × 941 PNG |
premiere-pro-mcp-social-square-v1.png |
Open Graph, X, LinkedIn, GitHub, and directory social creative | 1254 × 1254 PNG |
premiere-pro-mcp-workflow-v1.png |
Architecture explanation, documentation, and launch posts | 1672 × 941 PNG |
Approved positioning
Lead with the outcome and local-first architecture:
Connect a compatible AI assistant to Adobe Premiere Pro with structured tools for project inspection, supported editing workflows, diagnostics, and export.
Supporting proof:
- Free and MIT licensed
- Recommended local-first setup
- 349 registered core tools; 347 in the default profile
- 93 additional capability-gated tools with an authenticated compatible UXP host
- Windows and macOS packaging for supported Premiere versions
Claim boundaries
- Do not call an illustrated or simulated animation a live Premiere recording.
- Do not claim a static compatibility matrix proves a successful host operation.
- Do not say the project is affiliated with or endorsed by Adobe.
- Do not use the Adobe Premiere
Prtile as the project logo. - Do not claim customer adoption, successful installations, or tool outcomes without current evidence.
- Qualify UXP as capability-gated and keep CEP as the default production bridge until the documented release boundary changes.
Distribution checklist
For each launch placement, record the destination and use lowercase UTM values:
utm_source=<directory-or-community>
utm_medium=<social|directory|referral|email>
utm_campaign=premiere_pro_mcp_<release-or-theme>
utm_content=<asset-or-cta>
Link to https://premiere-pro-mcp.com/ as the canonical product page. Link directly to the current GitHub release only when the placement is specifically about release artifacts.