jhonny-editor/code/docs/marketing/community-launch-kit.md

Premiere Pro MCP community launch kit

Status: prepared drafts only. Nothing in this file has been posted, sent, or scheduled.

Use this only when it helps the current conversation

• Check each community's self-promotion rules before posting.
• Answer the workflow question first. Link a guide only when it genuinely answers the follow-up.
• Never represent illustrated site assets as a live Premiere session.
• Do not claim every tool or host version will work. Direct readers to the read-only connection check and capability inspection.
• Do not say the local server changes the privacy terms of the AI client the reader chooses.
• Do not contact people from this document without an approved contact list and owner authorization.

Owned social draft

AI editing is most useful when it removes repeated Premiere work without hiding the edit.

Premiere Pro MCP is a free, MIT-licensed local bridge between a compatible AI client and supported Premiere workflows. Start with a read-only connection check, inspect the project, preview a bounded request, and verify the returned result before relying on it.

Practical setup and workflow guides: https://premiere-pro-mcp.com/blog/?utm_source=linkedin&utm_medium=organic_social&utm_campaign=premiere_workflow_guides

Technical-community draft

I maintain an open-source MCP server for supported Adobe Premiere Pro workflows. The goal is not autonomous editing. It is to make repeated work inspectable: check the connection, inspect a project, create a non-mutating plan where available, preview it, and verify the returned result.

The project is local-first and independent from Adobe's AI Assistant. This guide compares the workflows without claiming either is universally better:

https://premiere-pro-mcp.com/blog/adobe-premiere-ai-assistant-vs-mcp/?utm_source=community&utm_medium=organic_referral&utm_campaign=premiere_workflow_comparison

Useful feedback: installation friction, capability boundaries, and the first repeatable Premiere task a team would test.

Editorial-community reply pattern

1. Name the specific Premiere task the person is trying to repeat.
2. Share one concrete, non-promotional way to make it safer: define the target sequence, what must not change, and how the result will be checked.
3. If the person asks for a tool or implementation, disclose the project relationship and link the one relevant guide.
4. Invite correction or workflow details. Do not push a download.

Design-partner interview invitation draft

Subject: Could we map one repeatable Premiere workflow?

Hi [name],

I maintain Premiere Pro MCP, an open-source local bridge for reviewable Premiere workflows through compatible AI clients. I am looking to learn how post teams handle one repeated task such as project intake, cutdown preparation, or delivery checks.

This is a 30-minute research conversation, not a product-sale call. We will map the current steps, what must stay under editor control, and what evidence would make an automation trustworthy. We will not ask for project media, client footage, credentials, or confidential project names.

If it is useful, I can send the workflow questions in advance.

Thanks, Premiere Pro MCP contributors

Interview guide

• Which Premiere task repeats often enough to document?
• What triggers it, who owns it, and where does handoff fail?
• What input must an assistant see, and what must it never change?
• What output would prove the workflow succeeded?
• Which host versions and AI clients are involved?
• What would make setup too risky or too time-consuming?
• May we retain this feedback anonymously? Do not record customer claims or quotes without separate written approval.

Measurement

Use campaign links with the existing allowlisted UTM format:

• utm_source: channel or named partner
• utm_medium: organic_social, referral, or email
• utm_campaign: premiere_workflow_guides or another stable lowercase campaign ID
• utm_content: a stable creative ID when variants are tested

Primary success signal: a completed read-only connection check and an observable first workflow result. Likes, impressions, stars, and downloads are diagnostic only.