Adobe Target MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Adobe Target MCPlist my live A/B activities"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Adobe Target MCP
A Model Context Protocol server for Adobe Target. Lets AI assistants manage A/B and Experience Targeting activities through the Adobe Target Admin API, with automatic Adobe IMS OAuth token handling (fetch, cache, refresh).
Quickstart
Via Claude Code:
claude mcp add adobe-target \
-e ADOBE_CLIENT_ID=your-client-id \
-e ADOBE_API_KEY=your-client-id \
-e ADOBE_CLIENT_SECRET=your-client-secret \
-e ADOBE_TENANT=your-tenant \
-- npx -y @upendra_sengar/adobe-target-mcpRelated MCP server: AEM MCP Server
Requirements
Node.js >= 18
An Adobe Developer Console project with:
The Adobe Target API enabled
OAuth Server-to-Server credentials (client ID + client secret)
Your Adobe Target tenant name (the subdomain in
mc.adobe.io/<tenant>/target/...)
Configuration
All configuration is passed as environment variables — no keys are ever stored in this package.
Variable | Required | Description |
| ✅ | Client ID from your Adobe Developer Console project |
| ✅ | API key sent as |
| ✅ | Client secret from your Adobe Developer Console project |
| ✅ | Adobe Target tenant subdomain |
| — | Port for SSE / Streamable HTTP modes (default |
| — |
|
| — | File path for logs in stdio mode |
For local development you can copy .env.example to .env instead.
Installation
These clients all use the same mcpServers format:
{
"mcpServers": {
"adobe-target": {
"command": "npx",
"args": ["-y", "@upendra_sengar/adobe-target-mcp"],
"env": {
"ADOBE_CLIENT_ID": "your-client-id",
"ADOBE_API_KEY": "your-client-id",
"ADOBE_CLIENT_SECRET": "your-client-secret",
"ADOBE_TENANT": "your-tenant"
}
}
}
}Add to your workspace .vscode/mcp.json:
{
"servers": {
"adobe-target": {
"command": "npx",
"args": ["-y", "@upendra_sengar/adobe-target-mcp"],
"env": {
"ADOBE_CLIENT_ID": "your-client-id",
"ADOBE_API_KEY": "your-client-id",
"ADOBE_CLIENT_SECRET": "your-client-secret",
"ADOBE_TENANT": "your-tenant"
}
}
}
}Transports
Mode | Command | Use case |
stdio (default) |
| Local MCP clients (Claude Desktop, Cursor, …) |
Streamable HTTP |
| Remote / shared deployments ( |
SSE |
| Legacy SSE clients ( |
HTTP modes listen on PORT (default 3001).
Tools
Tool | Description |
| List activities with filters (state, name, type, priority) and pagination |
| Get full details of an A/B activity |
| Create a new A/B activity |
| Update an existing activity |
| Rename an activity |
| Update the DOM selector of an activity's experience location |
Authentication flow
The server exchanges your client credentials for an Adobe IMS access token (ims-na1.adobelogin.com), caches it, and refreshes it automatically 5 minutes before expiry. Tokens are held in memory only — nothing is written to disk.
Docker
docker build -t adobe-target-mcp .
docker run -i --rm \
-e ADOBE_CLIENT_ID=your-client-id \
-e ADOBE_API_KEY=your-client-id \
-e ADOBE_CLIENT_SECRET=your-client-secret \
-e ADOBE_TENANT=your-tenant \
adobe-target-mcpLicense
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Upendrasengar/adobe-target-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server