Creative Community Orchestrator

From the right plan to the right creative action — powered by WebMCP.

Inspiration

Adobe's community is full of creators asking practical questions:

Which Creative Cloud plan is right for me?
Will Premiere Pro run on my machine?
Which app or feature should I use for this?
How do I solve this creative problem?

Creators often know what they want to accomplish, but not which plan, product, capability, or workflow will get them there.

Creative software is particularly challenging for agents because the right answer often depends on structured context that is easy to miss when interpreting webpages: region, student eligibility, plan contents, product-specific system requirements, checkout destinations, and capabilities inside individual applications.

An agent might return US pricing to a student in India, retrieve generic Creative Cloud requirements when asked about Premiere Pro, or suggest manual editing techniques without discovering that Photoshop has a specific capability — Harmonize — designed for the problem.

The agent understands what the creator wants, but it cannot always reliably discover what the creative ecosystem can offer.

That inspired Creative Community Orchestrator: use WebMCP to make the creative ecosystem structured and discoverable to agents, helping creators move from intent to the right action faster.

What it does

Creative Community Orchestrator connects a creator's intent and context to the right plan, product, capability, workflow, and action.

A design student in India can ask:

"I need Photoshop, Illustrator and occasional video editing. Which plan should I get?"

The agent can use her needs, region, and eligibility to find a relevant plan and regional offer, check product-specific compatibility, and guide her to the appropriate checkout path.

The same approach extends to creation:

"Clean up these jewelry photos, give them a premium campaign look, and create an Instagram post and launch flyer."

The agent can discover capabilities the creator may not know exist and connect them into a workflow:

Firefly → Photoshop + Harmonize → Adobe Express

The creator describes the outcome. The agent discovers the path.

This reduces searching, conflicting information, and dead ends — creating a more direct path from intent → confidence → action.

How we built it

We built Creative Community Orchestrator as a human-browsable website for exploring creative goals, workflows, capabilities, products, and plans.

Using WebMCP, we expose key capabilities as structured semantic tools for external agents, including:

Plan recommendation and regional pricing
Product-specific compatibility
Checkout navigation
Creative capability discovery
Cross-product workflow composition

The tools accept structured context such as region, eligibility, product needs, device context, and creative goals, and return structured results agents can use in subsequent steps.

This lets an external agent move from:

intent → tool discovery → verified information → capability discovery → workflow → action

without relying on brittle DOM interpretation or requiring creators to understand the structure of the creative ecosystem.

The website remains fully usable by people through its normal interface, while WebMCP gives agents a structured interface to the same ecosystem.

Creators use the UI. Agents use WebMCP. Both access the same creative ecosystem.

Challenges we ran into

One of the biggest challenges was turning a fragmented creative journey into structured context an agent could reliably use.

Plan recommendations depend on region, eligibility, required apps, pricing, and compatibility, while creative questions require mapping natural-language intent to the right capability.

Capability discovery was especially interesting. Users rarely ask for features by name. Someone might say, "the lighting on this object doesn't match the scene," and the agent needs to connect that problem to Photoshop Harmonize.

Another challenge was deciding what should become a WebMCP tool. Instead of exposing every button or UI interaction, we focused on meaningful creator intents: recommend a plan, check compatibility, discover a capability, find the correct purchase path, and compose a workflow.

We also wanted the website to remain useful to humans while becoming understandable to agents, without turning the experience into another chatbot.

Accomplishments that we're proud of

We're proud that the project demonstrates WebMCP across a connected creator journey:

Plan discovery → Regional pricing → Compatibility → Checkout → Capability discovery → Creative workflow

The agent can move beyond recommending broad products and discover specific capabilities such as Harmonize based on the creator's actual problem.

For a creative workflow, the collaboration can look like:

Firefly → create the campaign treatment
Photoshop + Harmonize → refine the composition and resolve the lighting mismatch
Adobe Express → create the Instagram post and launch flyer

Meera doesn't need to know beforehand which plan fits her needs, that Harmonize exists, which application contains it, or how multiple creative products can work together.

At the same time, the experience remains fully human-browsable while exposing the same ecosystem to external agents.

What we learned

Our biggest learning was that the agentic web isn't only about helping agents perform actions — it's also about helping them discover what actions are possible.

Creators think in outcomes: "Which plan fits me?", "Will this run on my machine?", "Make this composition look natural," or "Turn this into a campaign."

They shouldn't need to know the exact plan, product, feature name, or navigation path first.

Previously, creators had to translate their needs into the product ecosystem themselves:

research plans → compare prices → check requirements → discover products → find features → assemble a workflow

With WebMCP, that responsibility can be shared:

Creators provide intent, context, and creative judgment. Agents discover, verify, recommend, and orchestrate.

WebMCP becomes the bridge between creator intent and product capability.

What's next for Creative Community Orchestrator

Next, we want to expand Creative Community Orchestrator into an agent-accessible support layer across the creator journey.

That includes troubleshooting: a creator could say, "My Premiere Pro export looks washed out," and the agent could discover relevant product-specific guidance instead of returning generic results.

We also want to connect feature discovery directly to feature access. If the agent discovers that Harmonize is the right capability, it should take the creator to the exact feature, product experience, or relevant page where they can learn more or start using it.

Our vision expands the journey to:

Choose → Verify → Discover → Troubleshoot → Navigate → Create

So creators can stay focused on what they want to accomplish, while agents reliably discover how the creative ecosystem can help them get there.

People describe what they want to accomplish. Agents discover what's possible and help them act on it.

From creative intent to creative action — with WebMCP.