pulsemcp verified Safe content atomic mcp-remote

Premiere Pro

This TypeScript-based implementation bridges AI assistants to Adobe Premiere Pro through a WebSocket connection to a CEP (Common Extensibility Platform) extension panel. The architecture uses file-based IPC where the Node.js MCP server writes ExtendScript commands that are executed by the CEP panel running inside Premiere Pro. With over 170 tools organized across 14 modules including project management, sequence operations, timeline editing, effects and transitions, markers, audio control, graphics and captions, export functionality, and AI-powered voiceover generation through ElevenLabs integration, it enables comprehensive video editing automation. The implementation includes support for Windows through a batch installer, configurable settings, and detailed documentation covering installation and usage.

Cognium trust score

92%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: media
Source: PulseMCP
Repository: github.com/antipaster/adobe-premiere-pro-mcp
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve Premiere Pro from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"