pulsemcp Safe content atomic mcp-remote

Adobe Creative Suite

This MCP server provides AI-driven automation for Adobe Creative Suite applications including Photoshop, Premiere Pro, and InDesign through a multi-component architecture consisting of Python MCP servers, a Node.js proxy server, and UXP plugins that communicate via WebSocket connections. Built by Mike Chambers using Python with FastMCP, Socket.IO for real-time communication, and Adobe's UXP framework for plugin development, it enables AI assistants to perform complex creative workflows including layer manipulation, filter application, selection tools, adjustment layers, video editing with transitions and effects, and document creation across Adobe applications. The implementation bridges the gap between AI language models and professional creative software by translating natural language commands into Adobe API calls, making it valuable for automated design workflows, AI-assisted content creation, tutorial generation, and scenarios where creative professionals need conversational interfaces to complex Adobe functionality.

Cognium trust score

50%

Tier

Unverified

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

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: media
Source: PulseMCP
Repository: github.com/mikechambers/adb-mcp
Author type: human
Updated: 2026-04-29

View source Find related skills

MCP

Resolve Adobe Creative Suite 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"