Skip to main content
Glama
MSPbotsAI

adobe-admin-console-mcp

by MSPbotsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AUTH_MODENoAuthentication mode: 'env' or 'gateway'gateway
ADOBE_ORG_IDNoAdobe organization ID, e.g. 1234567890ABCDEF@AdobeOrg
MCP_HTTP_HOSTNoHTTP server bind address0.0.0.0
MCP_HTTP_PORTNoHTTP server port8080
MCP_TRANSPORTNoTransport: 'stdio' or 'http'stdio
ADOBE_BASE_URLNoUMAPI base URLhttps://usermanagement.adobe.io/v2/usermanagement
ADOBE_CLIENT_IDNoAdobe Developer Console Project Client ID
ADOBE_CLIENT_SECRETNoAdobe Developer Console Project Client Secret

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
adobe_list_usersA

List users in the Adobe organization.

    Rate limit: 25 requests/min per client, 100/min globally.

    Args:
        page: Page number to fetch, zero-indexed (default: 0). Check the
            response's "lastPage" field to know whether to fetch the next page.
adobe_get_userA

Get a single user's details, including current group/product profile memberships.

    Rate limit: 25 requests/min per client, 100/min globally.

    Args:
        email: The user's email address (or Adobe username string).
adobe_list_product_profilesA

List product profiles available for license assignment (e.g. Acrobat Pro/Standard).

    Adobe's API returns all groups (user groups and product profiles together);
    this tool filters the response down to entries where type == "PRODUCT_PROFILE",
    since Adobe has no dedicated "list product profiles only" endpoint.

    Rate limit: 5 requests/min per client, 100/min globally.

    Args:
        page: Page number to fetch, zero-indexed (default: 0).
adobe_assign_licenseA

Assign a license by adding a user to a product profile (e.g. an Acrobat Pro profile).

    Rate limit: 10 requests/min per client, 100/min globally.

    Args:
        email: The user's email address to grant the license to.
        product_profile: The exact product profile name (see adobe_list_product_profiles).
adobe_remove_licenseA

Revoke a license by removing a user from a product profile.

    Rate limit: 10 requests/min per client, 100/min globally.

    Args:
        email: The user's email address to revoke the license from.
        product_profile: The exact product profile name (see adobe_list_product_profiles).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.3/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: listing users, getting user details, listing product profiles, assigning licenses, and removing licenses. There is no overlap or ambiguity in their intended functions.

Naming Consistency5/5

All tool names follow a consistent 'adobe_' prefix with a verb_noun pattern: list_users, get_user, list_product_profiles, assign_license, remove_license. The naming is uniform and predictable.

Tool Count5/5

With 5 tools, the server is well-scoped for its purpose of managing Adobe admin console users and licenses. Each tool serves a necessary function, and the count is within the ideal 3-15 range.

Completeness4/5

The tool set covers the core license management lifecycle: read users, read profiles, assign and revoke licenses. Minor gaps exist such as no user creation or deletion, but these may be outside the server's intended scope, so the coverage is nearly complete.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources