How Wix scaled AI-native work to 5,000 employees with Willow
Read More
Enterprise Connectors
Adobe Admin logo. Adobe Admin MCP server connector.

Adobe Admin MCP Server

List Adobe Admin Console users and product profiles, and remove a user from a product profile or the organization. Uses OAuth Server-to-Server. UMAPI is limited to about 25 requests per minute.

ToolsTools
5
✓Enterprise-grade security
✓SSO & authentication ready
✓Full governance & audit logs

What is the Adobe Admin MCP Server?

The Adobe Admin MCP server gives AI agents structured, permission-aware access to Adobe Admin through the Model Context Protocol. With 5 pre-built actions, agents can read, create, and update Adobe Admin data on behalf of authorized users.

Willow ships the Adobe Admin MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Adobe Admin is being used by every AI agent in your stack.

Tools

Tool

List Users

List Adobe Admin Console users (email, status, type, and product-profile groups). Page is 0-based. Only active users are returned. Limited to about 25 requests per minute.
Tool

Get User

Retrieve one Adobe Admin Console user by email (or username). Only active users are returned. Limited to about 25 requests per minute.
Tool

List Groups

List user groups and product profiles (name, type, product, license quota). Use groupName of a PRODUCT_PROFILE when removing product access. Limited to about 5 requests per minute.
Tool

Remove Product Profile

Remove a user from one product profile or user group by exact Admin Console group name. This is how UMAPI removes product access. Does not delete the Adobe account. Limited to about 25 requests per minute.
Tool

Remove From Organization

Remove the user from the Adobe organization and all of its product profiles and user groups. Does not delete an Adobe ID (those are owned by the user). Set delete_account true only for org-owned Enterprise/Federated accounts — that permanently deletes directory assets.
Customize tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

ReviewEdit descriptions
ConfigureChange arguments
ApproveSelect tools
Create NewAdd tool

Set Up Your Adobe Admin MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "willow-adobe-admin": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/adobe-admin"
    }
  }
}

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "willow-adobe-admin": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/adobe-admin"
    }
  }
}

Claude Code

CLI
claude mcp add willow-adobe-admin --transport http https://<org>.mcp-s.com/mcp/mcp/adobe-admin

n8n

HTTP Request Node
{
  "url": "https://<org>.mcp-s.com/mcp/mcp/adobe-admin",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Adobe Admin

Willow adds the layer Adobe Admin and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Adobe Admin MCP Server FAQ

What is the Adobe Admin MCP server?

The Adobe Admin MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Adobe Admin data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Adobe Admin MCP server different from the official one?

The official Adobe Admin MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Adobe Admin MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Adobe Admin MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Adobe Admin, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Adobe Admin actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Adobe Admin MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Adobe Admin MCP locally, you'll see it.

What does the Adobe Admin MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Adobe Admin MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.

Compare Willow MCP Gateway

See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.

Your agents are already in the wild.

Give them a Basecamp. Go from AI chaos to AI work, in minutes.