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 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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