Adobe Target MCP
An unofficial MCP server that enables natural language management of Adobe Target activities, offers, audiences, response tokens, and reporting through 33 integration tools.
README
Adobe Target MCP
An (Unofficial) Model Context Protocol Agent Framework for Adobe Target, enabling your favorite MCP Clients to create and manage Adobe Target activities, HTML & JSON offers, audiences, response tokens and activity reporting all through natrual language
MCP Standard Compliance: This project follows the open Model Context Protocol standard and works with any MCP-compatible client (Claude Desktop, Cursor, or other MCP clients). Configuration examples below use Claude Desktop/Code, but the same mcpServers format applies to all MCP clients.
Adobe Target API Documentation: https://developer.adobe.com/target/administer/admin-api/
Table of Contents
Core Capabilities
- Adobe Target Admin API Integration: Complete suite of 33 tools for managing A/B tests, Experience Targeting, offer creation (HTML/JSON), audiences, mboxes, properties, activity performance reports and response tokens
- Activity Reporting: Query results for live and past activities
- Response Token Managment: Create new resposne tokens and take inventory of existing ones
- Intelligent Offer Creation: Generate HTML offers, or JSON offers for headless/SPA implementations with structured data templates
- Audience Managment and Creation: List exisiting audiences in your AT property, or create new ones with natrual language
- DataLayer Event Generation: Automated conversion in HTML offers tracking for GTM, Adobe Launch, Tealium, Segment
Quick Start
Prerequisites
Before installing, ensure you have:
- Node.js 20+ - Required for ES modules support (Download)
- Chrome Browser - Required for the agent to see your webpage, analyze DOM elements, and preview changes live
- Adobe Target Account - With Admin API access
- MCP Client - Claude Desktop, Claude Code, Cursor, Windsurf or any MCP-compatible client
1. Clone the Repository
git clone https://github.com/scottehastings16/adobe-target-mcp.git
cd adobe-target-mcp
2. Install Dependencies
npm install
Dependencies installed:
@modelcontextprotocol/sdk@^1.0.4- MCP protocol implementationdotenv@^17.2.3- Environment variable management
3. Install Required MCP Servers
This agent requires two MCP servers working together:
a) Adobe Target MCP Agent (this project)
- Already installed with
npm install
b) Chrome DevTools MCP Server (REQUIRED)
- Provides live browser DOM access and page analysis
- Automatically installed via
npxwhen adobe-target-mcp is configured - Requires Chrome or Chromium browser
4. Configure Environment
Copy .env.example to .env and configure:
# Required - Adobe Target API credentials
TARGET_TENANT_ID=your-tenant-id
TARGET_API_KEY=your-api-key
TARGET_ACCESS_TOKEN=your-access-token
TARGET_WORKSPACE_ID=your-workspace-id
# Optional - Default values for activities
TARGET_DEFAULT_MBOXES=target-global-mbox
TARGET_DEFAULT_PRIORITY=5
# Optional - Success metrics defaults
TARGET_DEFAULT_METRIC_TYPE=engagement
TARGET_DEFAULT_ENGAGEMENT_METRIC=page_count
5. Configure MCP Client
Copy .claude.json.example to your MCP client's configuration file and update the paths and credentials.
For Claude Desktop/Code:
Windows: %APPDATA%\Claude\claude_desktop_config.json
Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json
For other MCP clients: Refer to your client's documentation for the MCP server configuration file location.
{
"mcpServers": {
"adobe-target": {
"command": "node",
"args": ["C:\\Users\\YourUsername\\adobe-target-mcp\\src\\index.js"],
"env": {}
},
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp"],
"env": {
"CHROME_PATH": "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe"
}
}
}
}
Platform-specific Chrome paths:
- Windows:
"C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe" - Mac:
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" - Linux:
"/usr/bin/google-chrome"or"/usr/bin/chromium"
Platform-specific path formats:
- Windows: Use backslashes with escaping:
"C:\\Users\\YourUsername\\adobe-target-mcp\\..." - Mac/Linux: Use forward slashes:
"/Users/yourname/adobe-target-mcp/..."
6. Start Using
Once configured, you can ask your AI assistant to:
- "Show me the results from the Paid Media Personalization activity"
- "Create a carousel under the hero image on my website www.example.com"
- "Show me what response tokens are avilable in my targt propert"
- "Generate a popup module for my page www.example.com, add a CTA and this image: example.com/image.png... add a CTA that links to the products page at this link example.com/products"
- "Create a JSON offer for feature flags"
- "List all active Target activities"
- "List avilable mboxes in my property"
- "Generate a conversion report for the Buy Now CTA Test"
- "Help me create a new response token"
- Update the "Buy Now" Offer with a new stlying using by configured brand colors
The agent will use its 33 tools to interact with Adobe Target on your behalf.
External MCP Servers
- chrome-devtools-mcp (auto-installed via npx)
- Purpose: Live browser control, DOM analysis, screenshots
- Installation: Automatic on first run via
npx -y chrome-devtools-mcp - Requirements: Chrome/Chromium browser
System Requirements
- Node.js: 20+ (ES modules support required)
- Adobe Target: Account with Admin API access
- Chrome Browser: Required for Chrome DevTools MCP integration
- MCP Client: Claude Desktop, Claude Code, or any MCP-compatible client
Project Structure
adobe-target-mcp/
├── src/
│ ├── index.js # Main MCP server entry point
│ ├── .env.example # Environment variable template
│ │
│ ├── config/
│ │ ├── tag-managers.json # Tag manager configurations (GTM, Adobe Launch, Tealium, Segment)
│ │ └── firing-conditions.json # Event firing logic (session, throttle, debounce, etc.)
│ │
│ ├── helpers/
│ │ ├── makeTargetRequest.js # Adobe Target API client wrapper
│ │ └── applyDefaults.js # Auto-fill default configuration values
│ │
│ ├── templates/
│ │ ├── README.md # Template system documentation
│ │ ├── html/ # HTML offer templates (10 templates)
│ │ │ ├── carousel.json
│ │ │ ├── hero-banner.json
│ │ │ ├── cta-button.json
│ │ │ ├── modal.json
│ │ │ ├── sticky-header.json
│ │ │ ├── countdown-timer.json
│ │ │ ├── form-field.json
│ │ │ ├── tabs.json
│ │ │ ├── accordion.json
│ │ │ └── notification-banner.json
│ │ └── json/ # JSON offer templates (9 templates)
│ │ ├── product-recommendations.json
│ │ ├── feature-flags.json
│ │ ├── hero-config.json
│ │ ├── pricing-data.json
│ │ ├── personalization-content.json
│ │ ├── navigation-menu.json
│ │ ├── form-config.json
│ │ ├── testimonials.json
│ │ └── ab-test-variant.json
│ │
│ └── tools/
│ ├── index.js # Tool registration
│ ├── activities/ # Activity management (5 tools)
│ │ ├── listActivities.js
│ │ ├── createABActivity.js
│ │ ├── getABActivity.js
│ │ ├── updateABActivity.js
│ │ └── updateActivityState.js
│ ├── offers/ # Offer management (5 tools)
│ │ ├── listOffers.js
│ │ ├── createOffer.js # PRIMARY TOOL - HTML offers
│ │ ├── createJsonOffer.js # JSON offers (SPAs, server-side, mobile)
│ │ ├── getOffer.js
│ │ └── updateOffer.js
│ ├── audiences/ # Audience management (2 tools)
│ │ ├── listAudiences.js
│ │ └── createAudience.js
│ ├── mboxes/ # Mbox resources (3 tools)
│ │ ├── listMboxes.js
│ │ ├── getMbox.js
│ │ └── listMboxProfileAttributes.js
│ ├── properties/ # Properties (1 tool)
│ │ └── listProperties.js
│ ├── reports/ # Reporting (6 tools)
│ │ ├── getABPerformanceReport.js
│ │ ├── getABOrdersReport.js
│ │ ├── getXTPerformanceReport.js
│ │ ├── getXTOrdersReport.js
│ │ ├── getAPTPerformanceReport.js
│ │ └── getActivityInsights.js
│ ├── response-tokens/ # Response tokens (2 tools)
│ │ ├── listResponseTokens.js
│ │ └── createResponseToken.js
│ ├── atjs/ # at.js settings (2 tools)
│ │ ├── getAtjsSettings.js
│ │ └── getAtjsVersions.js
│ ├── revisions/ # Activity revisions (2 tools)
│ │ ├── getRevisions.js
│ │ └── getEntityRevisions.js
│ ├── templates/ # Template management (1 tool)
│ │ └── listTemplates.js # Browse available templates
│ └── custom/ # DataLayer & preview tools (4 tools)
│ ├── generateDataLayerEvent.js
│ ├── createActivityFromModifications.js
│ ├── generatePreviewScript.js
│ └── getMockupAnalysisInstructions.js
│
├── package.json # Node.js dependencies
├── .env # Environment variables (create from .env.example)
└── README.md # This file
Available Tools
Activities (5 tools)
listActivities- List all Target activities with filteringcreateABActivity- Create A/B test (API-only, advanced use)getABActivity- Get activity details by IDupdateABActivity- Update activity configurationupdateActivityState- Activate, pause, or deactivate activities
Offers (5 tools)
listOffers- List all offers with filteringcreateOffer- PRIMARY TOOL - Create HTML offer (use for 95% of cases)createJsonOffer- Create JSON offer for SPAs, server-side, mobile apps, headlessgetOffer- Get offer details by IDupdateOffer- Update offer content
Audiences (2 tools)
listAudiences- List all audiencescreateAudience- Create new audience with rules
Mboxes (3 tools)
listMboxes- List all mboxesgetMbox- Get mbox detailslistMboxProfileAttributes- List profile attributes for mbox
Properties (1 tool)
listProperties- List Target properties
Reports (6 tools)
getABPerformanceReport- A/B test performance metricsgetABOrdersReport- A/B test order/revenue datagetXTPerformanceReport- Experience Targeting performancegetXTOrdersReport- Experience Targeting ordersgetAPTPerformanceReport- Automated Personalization performancegetActivityInsights- Activity insights and recommendations
Response Tokens (2 tools)
listResponseTokens- List all response tokenscreateResponseToken- Create custom response token
at.js Configuration (2 tools)
getAtjsSettings- Get at.js settingsgetAtjsVersions- List available at.js versions
Revisions (2 tools)
getRevisions- List all activity revisionsgetEntityRevisions- Get revisions for specific entity
Templates (1 tool)
listTemplates- Browse all available HTML & JSON templates
Custom Tools (4 tools)
generateDataLayerEvent- Generate conversion tracking code with tag manager supportcreateActivityFromModifications- Create Target activity from JavaScript modifications (advanced use, API limitations apply)generatePreviewScript- Generate preview script for Chrome DevTools MCP injectiongetMockupAnalysisInstructions- Get instructions for mockup analysis and experience generation workflow
License
MIT License - See LICENSE file
Links
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.