Shared core
The shared core package provides infrastructure used by the Adobe app servers: safe argument normalization and script literals, path policy, script execution, structured results, MCP server construction, annotations and static script auditing.
What this implementation covers
safe string/number/enum/path conversion; execution adapters; structured result parsing; failure detection; alias normalization; MCP tools/list and tools/call; annotation metadata; static API audits.
For feature-level detail and evidence, see the Capability Atlas.
Connection and requirements
How it reaches the app
A JavaScript library dependency, not a standalone MCP server and not a user-facing CLI.
What you need
Node.js 18+ when used by the packages. App runtimes are determined by the consuming server.
Package: adobe-mcp-core. Add it as a local stdio MCP server using CLI & client configuration.
API and content conventions
For contributors and integrators. The core README documents exports, executor options, error/result shape and tests. It does not provide Adobe app tools directly.
Discover the running package’s exact tool names and JSON input schemas through MCP tools/list. If the server provides help, use it to inspect a tool or category. Schemas from a different package version may not match.
Target and units: Core helpers are called by consuming packages; behavior such as application backend, paths and protocol is configured at the app-server layer.
CLI and configuration
This package is launched as a persistent MCP process, not as a conventional one-shot CLI. Relevant settings documented by the package include:
No standalone CLI configuration. Refer to each consuming package for environment variables and runtime behavior.
Variable names and defaults are package-specific; consult the package README before changing them. File-operation permissions and bridge tokens should be configured in the client’s environment, not embedded in prompts or checked into source.
claude mcp add core -- npx -y adobe-mcp-coreFor client-neutral JSON configuration and source-checkout commands, see CLI & configuration.
Full reference
The repository README is maintained alongside this implementation and covers exact setup, tool families, package-specific behavior, limitations, security and development status.