Adobe Target MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for SSE / Streamable HTTP modes (default 3001) | 3001 |
| ADOBE_TENANT | Yes | Adobe Target tenant subdomain | |
| MCP_LOG_FILE | No | File path for logs in stdio mode | |
| ADOBE_API_KEY | Yes | API key sent as X-Api-Key (same value as the client ID) | |
| ADOBE_CLIENT_ID | Yes | Client ID from your Adobe Developer Console project | |
| MCP_TOOL_LOGGING | No | Set to 'true' to enable verbose per-tool logging | |
| ADOBE_CLIENT_SECRET | Yes | Client secret from your Adobe Developer Console project |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_activitiesC | List activities from Adobe Target. API key and tenant are loaded from environment variables automatically. |
| update_activity_nameA | Update the name of an activity in Adobe Target. API key and tenant are loaded from environment variables automatically. |
| get_activity_by_idA | Get an Adobe Target activity by ID. Supports both AB and XT activity types. API key and tenant are loaded from environment variables automatically. |
| create_ab_activityB | Create an AB activity in Adobe Target. |
| update_activityA | Update an Adobe Target activity by injecting new HTML/JS code into a named experience. API key and tenant are loaded from environment variables automatically. Handles: deep-clone of payload, creating new option slots (optionLocalId=0), orphan pruning, offerContent deduplication (prevents UniqueElements AT error), and supports both AB and XT activity types. |
| update_activity_selectorA | Update one or more location selectors in an Adobe Target activity. Use this when the activity's primary location selector (e.g. "BODY > *:eq(0)") does not match the intended CSS injection target (e.g. "#business"). Returns a list of available location names if the specified name is not found. API key and tenant are loaded from environment variables automatically. Supports both AB and XT activity types. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct action: listing, getting by ID, creating AB activities, updating the name, injecting HTML/JS code, or modifying selectors. No two tools overlap in purpose.
All tools follow a consistent verb_noun pattern in snake_case (e.g., list_activities, update_activity_name, create_ab_activity). No mixing of conventions.
With 6 tools, the set is well-scoped for an Adobe Target MCP server. It provides core operations without being excessive or sparse.
The set covers create, read, and update operations, but notably lacks a delete activity tool. This creates a gap in basic lifecycle management.