Blog posts by Vaibhav

Introducing the Optimizely MCP Server: AI That Speaks Commerce Part-II

Fri, 29 May 2026 16:57:24 GMT

— Part 2 · Build Update · B2B Commerce

From conversation to completed transaction.

Part 1 gave AI the ability to speak commerce. The latest release of the Optimizely MCP Server lets it complete commerce the entire B2B buyer journey, from first question to placed order, now runs inside a chat.

● 34 tools live 6 functional domains Claude · ChatGPT · Copilots Optimizely / Insite B2B Commerce

34 tools

Standardized commerce actions any AI can call

↑ from 8 in Part 1

~2,600 ops

Underlying Insite API operations reachable via meta-discovery

3 OpenAPI specs indexed

1 protocol

One MCP surface serves every AI assistant & copilot

No per-channel rebuild

Watch the Optimizely MCP Server in action — live demo with Microsoft-Copilot

— What changed

Eight tools became thirty-four. Browsing became buying.

The first release proved AI could understand a B2B catalog. This one closes the loop: authenticate the buyer, manage the cart, take payment, submit the order, track it afterward and even plug into the procurement systems enterprises already buy through.

Part 1 — May 2026

AI that speaks commerce

Catalog search & product detail
Pricing & inventory lookups
Read-only discovery
8 tools, browse-focused

→

Part 2 — This release

AI that acts within commerce

Full cart lifecycle & conversational checkout
Passwordless OTP login & BillTo / ShipTo switching
Order submission, status & history
PunchOut procurement + meta-discovery over 2,600 ops

— The buyer journey, end-to-end

Every step a buyer takes — now a tool the AI can call.

A single request like “order ten cases of SKU-9988 and check out with my saved card” fans out into this sequence. Each stop carries real business value.

01 Discover search_insite_products Fewer clicks to find. Contract pricing, stock & images surface in chat.	02 Build cart add_insite_product_to_cart No lost context. Cart persists across turns automatically.	03 Authenticate verify_insite_otp_login Passwordless & safe. Email OTP — the AI never sees a password.
04 Pay set_payment Out of PCI scope. No card number.	05 Submit submit_insite_order Order in seconds. Validated, placed, order number read back.	06 Track get_insite_order_status Fewer support calls. Status & tracking on demand.

— The tool catalog

Six domains. One job each. Real value behind every group.

Tools are grouped by what a buyer is trying to do, and every group can be switched on or off individually through an admin allow-list, so exposure expands only as fast as trust does.

🔎

META · 8

API Discovery & Introspection

The agent's table of contents over ~2,600 operations.

list_apislist_tagssearch_endpointsdescribe_endpointcall_endpointmcp_diagnosediscover_live_openapiresolve_commerce_endpoint

VALUE Future-proof. Anything the curated tools don't cover stays reachable, including custom storefront endpoints discovered live, with no redeploy.

🗂️	CATALOG + CHATGPT · 4

Product Search & Detail

Native B2B-rich tools + ChatGPT-shaped aliases.

search_insite_productsget_insite_product_detailssearchfetch

VALUE Works with any AI. The same search logic ships in OpenAI's data-app shape and the native MCP shape, Claude, ChatGPT, or a custom copilot, no rebuild.

🛒

CART · 8

Full Shopping-Cart Lifecycle

Add, update, remove, clear, inspect promotions.

view_insite_cartadd_insite_product_to_cartupdate_insite_cartdelete_insite_cart_lineclear_insite_cartinspect_insite_promotionsview_cartadd_to_cart

VALUE Anonymous to check out. Buyers build a cart with zero friction; the agent only asks for login when an order is actually placed.

✅

ORDER · 4

Checkout, Status & History

Two-step pay-and-submit, plus tracking after.

set_credit_card_paymentsubmit_insite_orderget_insite_order_statusview_insite_order_history

VALUE Hours to seconds. Reorders, status checks, and history that used to mean a support ticket now resolve inside the conversation.

🔐	AUTH / SESSION · 6

Secure B2B Identity

OTP login, token management, account switching.

request_insite_login_otpverify_insite_otp_loginlogout_insite_userchange_insite_customerget_oauth_tokenrequest_insite_oauth_token

VALUE Built for real B2B. Passwordless login by design, and one buyer can switch between multiple BillTo / ShipTo accounts mid-conversation.

🔗	PUNCHOUT · 4

Procurement-System Buyer Flow

cXML PunchOut into the systems buyers already use.

start_insite_punchout_sessionview_insite_punchout_sessionsubmit_insite_punchout_requisitioncancel_insite_punchout

VALUE Meet enterprise where it buys. Ariba, Coupa, JAGGAER & Oracle buyers punch out, build a requisition by chat, and return it pre-populated.

— Spotlight · New in this release

Passwordless login the AI can't abuse.

Letting an assistant place orders means letting it act as the buyer, so authentication had to be safe by construction. The new OTP backend makes the AI a courier for a code, never a holder of a password.

📧

STEP 01

Request

The AI calls request_insite_login_otp. A one-time code is emailed straight to the buyer.

📨

STEP 02

Buyer receives

The code lands in the buyer's inbox — out of band. The assistant never sees it generated.

🔑

STEP 03

Verify

Buyer reads the code back; verify_insite_otp_login exchanges it for a session token.

🔒

STEP 04

Act as buyer

Every later tool call runs as the authenticated user — with their pricing, history & permissions.

● No password grant exposed

The password-login path exists in code but is deliberately never registered — an assistant cannot prompt for or transmit a raw password.

● Per-session isolation

Every MCP client gets its own cookie jar & token cache, keyed by an opaque session GUID. Login state never leaks between users.

● No raw card data

Payment accepts a Spreedly token only. The agent never receives a primary account number — keeping it out of PCI scope.

The future of B2B commerce isn't a better checkout. It's no checkout screen at all, just intent, understood, and executed.

— Multi-channel reach

Build it once. Every assistant can use it.

Because the agent speaks one open standard, JSON-RPC 2.0 over MCP, the same backend serves every host on the market. ChatGPT connectors even get tools shaped to OpenAI's exact contract, with no separate codebase.

◆

Claude

Desktop / claude.ai

◇

ChatGPT

search · fetch · cart

◈

Copilots

Enterprise bots

▣

Spire SSR

Storefront agent

⬡

Procurement

PunchOut buyers

— Under the hood

Five clean layers, one job each.

AI hosts on the left, the live Optimizely / Insite backend on the right — and a thin, isolated agent in between that never stores customer payment data itself.

Fig. 1 — MCP Agent high-level architecture: clients → transport & protocol → 34-tool catalog → services & specs → Optimizely / Insite backend.

— Why it matters

The business case, in four lines.

Faster time-to-order

The catalog, cart and checkout that already power the website become AI-callable on day one, no rebuild, no rip-and-replace.

Fewer support escalations

Order status, reorders, and history resolve in conversation instead of routing to a human rep.

Multi-channel by default

One MCP surface reaches Claude, ChatGPT, internal copilots, and procurement systems engineering effort is spent once.

Controlled, low-risk rollout

An admin allow-list governs exactly which tools are live; new tools default to off, so trust is earned domain by domain.

Bring transaction-grade AI to your commerce stack.

Connect Optimizely to Claude, ChatGPT and your own copilots in minutes. One protocol, 34 tools, the full B2B journey no custom integration required.

Read Part 1

Introducing the Optimizely MCP Server: AI That Speaks Commerce Part-I

Tue, 12 May 2026 13:39:59 GMT

MCP AI Commerce B2B Claude ChatGPT OpenAI Optimizely Insite Commerce

Introducing the Optimizely MCP Server: AI That Speaks Commerce

We've connected Optimizely's B2B commerce engine directly to AI assistants, so your teams can search, transact, and manage orders through natural conversation.

Watch the Optimizely MCP Server in action — live demo with OpenAI

Watch the Optimizely MCP Server in action — live demo with Claude

The Why

Commerce Should Respond to Intent, Not Clicks

For years, B2B buyers have navigated complex catalogs, pricing tiers, and procurement workflows through rigid interfaces designed for a pre-AI world. Thousands of clicks to find a product. Dozens of fields to complete an order. Hours lost to processes that should take seconds.

We built the Optimizely MCP Server to change that. By connecting Optimizely's industry-leading commerce platform to AI assistants via the Model Context Protocol (MCP), we're giving buyers, sales reps, and procurement teams the ability to search, transact, and manage the entire commerce journey through natural language, the way humans actually think and communicate.

"The future of B2B commerce isn't a better UI. It's no UI at all just intent understood and executed instantly."

What Is MCP?

The Protocol That Connects AI to Real Systems

The Model Context Protocol (MCP) is an open standard that allows AI models like ChatGPT and Claude to connect securely to external tools and data sources. Think of it as a universal adapter: instead of custom integrations for every AI platform, one MCP server exposes your commerce capabilities as structured tools any compliant AI can invoke.

Optimizely's MCP Server exposes the full power of the Insite/Optimizely Commerce platform catalog search, cart management, order submission, promotions, pricing, and more as a set of AI-callable tools. The result: an AI assistant that doesn't just answer questions about your catalog, but actually acts within it.

How It Works

User speaks intent

A buyer or rep types a natural language request "Find me a telescopic boom lift for a rental construction site."

AI interprets & selects tools

ChatGPT and Claude understand the request and call the appropriate MCP tools searching the catalog, fetching pricing, checking inventory.

Commerce engine executes

The MCP Server routes the call to Optimizely's live APIs returning real products, real prices, real availability.

AI presents & acts

Results surface in conversation. The buyer can compare, add to cart, apply promotions, and submit the order all without leaving the chat.

Capabilities

Eight Tools. One Seamless Commerce Experience.

Today's release of the Optimizely MCP Server ships with eight core capabilities, covering the complete buyer journey from discovery to checkout.

🔍

Product Catalog Search

Natural language queries against the full Optimizely product catalog with facets, pricing, and images.

Live

👤

Customer & Order Lookup

Instant retrieval of customer records, order history, and account status for authenticated sessions.

Live

💲

Pricing Queries

Real-time unit pricing, break pricing, VAT calculation, and customer-specific tier pricing.

Live

📦

Inventory Availability

Live stock levels, backorder status, and warehouse availability across all configured locations.

Live

🔗

Punchout & Session Ops

Full support for PunchOut session initiation, requisition returns, and procurement system handoffs.

Live

🛒

Cart Management

Add items, update quantities, apply PO numbers, set payment methods, and submit orders all conversationally.

Live

🎟️

Promotion Inspection

Check applied and available promotions on a cart or product in real time before order submission.

Live

📄

CMS & Content Sync

Surface CMS-managed content product descriptions, banners, landing pages through AI-driven queries.

Coming Soon

Impact

Measurable Outcomes from Day One

Early pilots with enterprise B2B customers across manufacturing, construction equipment, and industrial supply showed significant improvements in time-to-order and reduction in support escalations when AI-assisted commerce was introduced.

What's Next

The Roadmap Ahead

This is just the beginning. We're actively expanding the MCP Server's surface area to include CMS content synchronization, personalized recommendation tools, multi-cart workflows, and approval chain automation for enterprise procurement scenarios.

We're also working closely with the teams at Anthropic, OpenAI, and other leading AI providers to ensure the Optimizely MCP Server remains at the cutting edge of what's possible when AI meets commerce infrastructure.

If you're an Optimizely customer and want early access, reach out to your account team. If you're an AI platform or integration partner interested in building on top of our MCP Server, we'd love to talk.

Ready to bring AI to your commerce stack?

Connect Optimizely to OpenAI, Claude, and your preferred AI assistant in minutes. No custom integration required.

Read Part 2

Accelerate Optimizely DAM Adoption: Unlocking Business Value with Metadata Bulk Import

Mon, 27 Apr 2026 14:37:29 GMT

Accelerating Optimizely DAM Adoption

How a Metadata-Driven Bulk Import Utility Unlocks Real Business Value

Executive Summary

For enterprises running Optimizely CMS 12 or 13, Digital Asset Management (DAM) is no longer optional; it is the strategic backbone of content operations. Yet the single biggest obstacle to DAM adoption is not technology; it is the sheer friction of getting thousands of existing assets off shared drives and into a governed, metadata-enriched repository.

The ImportAssetToOptiDam NuGet utility directly eliminates that friction. Built on .NET 8 and integrated with the Optimizely CMP API, it transforms a simple Excel spreadsheet and a folder of images into a fully tagged, SEO-enriched, governance-ready DAM library, automatically, overnight if required.

Why this matters to leadership

Every day, assets sit outside the DAM, your teams duplicate effort, miss SEO opportunities, and expose the business to brand and compliance risk. This utility compresses a weeks-long DAM migration into hours.

The Business Problem: DAM Adoption Stalls at the Front Door

In virtually every Optimizely enterprise engagement, the pattern is the same. The platform is configured, the taxonomy is designed, the workflows are approved—and then momentum halts. Marketing teams are sitting on thousands of product images structured in a spreadsheet, and the only path to get them into the DAM is manual, one-by-one UI uploads.

The downstream cost is substantial:

Editor productivity consumed by asset housekeeping instead of content creation
Inconsistent metadata and tags undermining search and personalization engines
CMS pages pointing to unmanaged file shares, creating governance blind spots
SEO performance degraded by missing alt-text and uncategorized assets

For a CTO or Senior Architect, this is an integration gap, not a training problem. The solution is a reliable, repeatable, automated ingestion pipeline—exactly what this utility provides.

What the Utility Does: A Five-Step Pipeline

Read Excel — Parses each row for asset metadata: title, description, alt text, tags, and custom DAM fields
Match Files — Maps each row to the corresponding image in the local Images folder
Authenticate — Obtains an OAuth 2.0 token from Optimizely CMP using Client ID and Client Secret
Upload & Enrich — Pushes the binary to DAM and immediately applies all structured metadata
Report — Writes an output Excel containing the published DAM URL for every asset

Architectural Value: Why This Is the Right Design

Decoupled Ingestion Architecture

From an enterprise architecture standpoint, the utility enforces a clean separation of concerns that makes it extensible and platform-agnostic. The Excel sheet acts as the control plane, the Images folder is the binary payload, and the Optimizely CMP API is the integration boundary.

Metadata-First: SEO and Governance by Design

Assets are not just uploaded—they arrive in the DAM already enriched. Every image carries structured attributes, alt text, tags, and custom field values defined in the Excel template before a single API call is made.

OAuth 2.0 Security — No Human in the Loop

The utility integrates directly with the Optimizely CMP OAuth 2.0 token endpoint. No user session is required, no browser interaction, no shared credentials. The application authenticates using Client ID and Client Secret, making it suitable for unattended batch execution or CI/CD pipelines.

Getting Started: Five Minutes to First Import

NuGet Package:

https://www.nuget.org/packages/ImportAssetToOptiDam
Version 1.0.0 | Targets .NET 8.0+

Installation Steps:

Install the package:
dotnet add package ImportAssetToOptiDam --version 1.0.0
Configure appsettings.json with CMP BaseUrl, ClientId, and ClientSecret
Place the Excel file in ExcelSheet folder and images in Images folder, then run the console app

The output Excel (in the Output folder) contains published DAM URLs for all assets—ready for CMS or downstream systems.

⚠ Beta Release — Validate in Lower Environments

ImportAssetToOptiDam is currently in Beta. Validate in DEV and UAT environments before production use. Verify metadata mapping, duplicate handling, and file mismatches against your DAM taxonomy.

Strategic Fit: Where This Accelerates Your Roadmap

CMS 11 to CMS 12/13 migration — bulk migration with enriched metadata
DAM onboarding — reduces weeks of manual effort
Commerce asset refresh — sync seasonal catalogs efficiently
Partner ingestion — external teams can contribute without CMP UI access
Headless DXP — generates reusable DAM URLs for any frontend

Start your DAM adoption journey today:
https://www.nuget.org/packages/ImportAssetToOptiDam

Accelerating Optimizely CMS Upgrades with Intelligent Automation

Mon, 13 Apr 2026 10:47:29 GMT

Upgrading an Optimizely (formerly EPiServer) CMS solution has traditionally been a high-risk, resource-intensive endeavor. Transitioning from CMS 11 to modern versions (CMS 12/13) requires a fundamental shift from .NET Framework to .NET Core/8/10, involving hundreds of breaking API changes and structural re-architecting.

OptiUpgrade Assistant by Royal Cyber Inc. is a purpose-built automation platform that transforms this multi-week manual process into a single-session automated workflow. By automating up to 31 migration steps and fixing over 220 categories of build errors, the tool reduces migration time by approximately 60–70%.

The Business Challenge: The Cost of Manual Migration

Manual upgrades are expensive, not just in developer hours, but in project risk and delayed time-to-market. A typical medium-complexity migration faces:

Runtime Complexity: Moving from Windows-only .NET Framework to modern, cross-platform .NET 8/10.
API Breaking Changes: Over 220 distinct patterns that invalidate legacy code.
Manual Effort: A standard migration for a medium project typically consumes 11–19 days of senior engineering time just for the initial build-ready state.

Migration Activity	Manual Effort	With OptiUpgrade	Time Saved
Project Structure & Conversion	2–3 Days	< 5 Minute	~80%
NuGet Package Resolution	1–2 Days	< 10 Minute	~70%
Breaking API Fixes (220+ patterns)	5–10 Days	< 50 Minutes	~65%
Issue Identification & Reporting	2–3 Days	Instant	~95%
TOTAL (Medium Project)	11–19 Days	< 1 Day	~60–70%

Key Business Benefits

1. Massive Cost Reduction

By automating the mechanical aspects of the upgrade, organizations can reallocate senior talent to high-value feature development rather than repetitive code refactoring.

Small Projects: Save 8–12 days.
Medium Projects: Save 18–37 days.
Large Enterprise Projects: Save 50–80+ days.

2. Risk Mitigation & Non-Destructive Workflow

The tool operates on a "Safety First" principle. It never modifies the original codebase. Instead, it creates a complete workspace copy and applies transformations there. This ensures:

Zero Regression Risk: The original production-ready code remains untouched.
Reversibility: Migrations can be discarded and re-run without complex rollback procedures.
Auditability: Every automated fix is annotated with // TODO comments and logged in a comprehensive report.

3. Future-Proofing (CMS 12 & CMS 13)

OptiUpgrade Assistant is not a one-time fix. It supports the entire modern Optimizely roadmap:

CMS 11 → 12: Full .NET 8 transition and API modernization.
CMS 12 → 13: Transition to .NET 10 and the new Optimizely Graph search platform.

Quantified ROI Example

For a medium-complexity project (~80,000 lines of code), the shift from manual to automated migration delivers a 70% reduction in total estimated cost.

OptiUpgrade Assistant removes the primary barrier to platform modernization: the prohibitive cost and risk of the upgrade itself. By providing a systematic, automated, and non-destructive path to the latest Optimizely versions, it enables businesses to leverage modern cloud-native features, improved performance, and the latest security standards in a fraction of the time.

OptiUpgrade Assistant in Action

The following screenshots highlight the end-to-end workflow of the OptiUpgrade Assistant, from selecting a CMS 11 solution to executing automated migration and reviewing detailed reports. The tool provides full visibility into each migration step, ensuring accuracy, transparency, and confidence throughout the upgrade process.

With real-time analysis, automated fixes, and comprehensive reporting, teams can seamlessly transition from CMS 11 to CMS 12 while significantly reducing manual effort and risk.

Integrating Commerce Search v3 (Vertex AI) with Optimizely Configured Commerce

Sat, 27 Sep 2025 18:26:13 GMT

Introduction

This blog provides a technical guide for integrating Commerce Search v3, which leverages Google Cloud's Vertex AI Search, into an Optimizely Configured Commerce environment.

This integration is engineered to significantly enhance the product discovery process for B2B e-commerce platforms.

By utilizing advanced, e-commerce-specific search technologies, organizations can simplify the B2B purchasing journey and improve conversion rates.

The Strategic Advantage of Vertex AI Search

Opting for Google Vertex AI Search over traditional solutions like Elasticsearch provides several key architectural and operational advantages.

Advanced Semantic Understanding: The system leverages Google's sophisticated natural language models to comprehend user intent, context, and semantics, which leads to more accurate and relevant search results.
Self-Learning Ranking Models: It automatically refines search relevance over time by learning from user behavior patterns. This minimizes the need for continuous manual tuning and rule configuration.
Reduction in "No Results" Queries: Through intelligent query expansion and robust synonym matching, the platform effectively reduces the frequency of zero-result queries, thereby improving user engagement and conversion rates.
Automated Dynamic Faceting: The system automatically identifies and presents the most relevant filters and facets based on the specific search context. This enhances product discoverability without requiring manual facet configuration.
Native Vector Search Capabilities: It has built-in support for vector-based retrieval for modern semantic and generative AI applications.
Reduced Maintenance Overhead: As a fully managed Google Cloud service, Vertex AI Search eliminates the operational burden of manual infrastructure management, updates, and scaling that is typically associated with self-hosted search solutions.
Ecosystem Integration: It offers seamless integration with the Google Cloud ecosystem, including services like BigQuery and other Vertex AI models, for a comprehensive, AI-driven experience.
Enterprise-Grade Infrastructure: The platform is built on Google Cloud's secure, compliant, and highly available infrastructure, making it suitable for large-scale enterprise applications.

For more information refer this URL: - Commerce Search v3 overview

Implementation Framework

A successful implementation requires meeting initial prerequisites and following a structured deployment process.

Prerequisites

Platform Version: Your environment must be on Optimizely Configured Commerce version 5.2.2506.1899+sts or a subsequent release.
Language Tagging: All languages utilized must be configured with a language tag.

Authentication: Optimizely ID SSO is mandatory for accessing the Google Vertex AI settings.

Implementation Steps

Commerce Search v3 is considered fully functional upon completion of the following sequence:

Advanced Configuration and Personalization

Post-implementation, you can customize search behavior via the Admin Console under Marketing > Commerce Search v3.

Understanding Serving Controls and Configs

The architecture's customization capabilities are cantered around Serving Controls and Serving Configs.

A Serving Config is a serving entity that defines the rules and behavior for search results, such as boosting, filtering, and query expansion. It can also associate a model for recommendations.
A Serving Control is a rule that determines the conditions under which a specific Serving Config is applied. The condition triggers the control, and an action takes place.

A Serving Config, while capable of existing independently, is only activated when it is referenced by a Serving Control. Conversely, a Serving Control is non-functional unless it is linked to a valid Serving Config.

This modular architecture allows for precise, dynamic personalization of the user experience at runtime without altering core backend logic.

Configuration Example: Product Boosting

To prioritize specific products for a given search query, you can create a serving control.

Navigate to Marketing → Search → Commerce Search v3 → Serving Controls → Create Control.
Define the Trigger: Set the Control Type to Boost/Bury Controls and specify the trigger condition. For example, enter 'lid' in the Partial match query terms field to activate the rule on searches for that term.

Define the Action: In the Rule section, specify the products to be boosted using their GUIDs. The rule expression supports operators including >, <, >=, <=, =, and:.
E.g.id: ANY ("8dfe59b4-8c19-4ed2-b3a6-b2f700a9000d", "fa329f4c-f530-46a9-a53e-b2f700a4728e", "34eba131-5d28-407d-becb-b2f700ae4064")

Associate Control with Config: Add the newly created serving control to the relevant serving configuration. This action ensures that when a user searches for 'lid', the products with the specified IDs are boosted in the search results.

Operational Considerations

Serving Config ID: Ensure the correct Service Config ID is specified in the Admin Console settings at Administration > Settings > Search > Serving Config ID. If a custom ID is being used, it must be correctly entered here.

Indexing and Synchronization: Any updates made to a Serving Config, or a Serving Control require indexing to be reflected on the live website. After initiating indexing, it may take approximately 20–25 minutes for the changes to fully sync with GCP and become visible to users. The system checks for matching serving controls at runtime and applies the associated logic.

Result on the storefront:
The products with IDs “2A126080”, “302NR04021”, “2FG26070” are prioritized to appear at the top of the search results.

AI-Powered Search & Natural Language Processing (NLP)

When a shopper enters a search like:

"printer under $100"
"eco-friendly office supplies"
"fastest laser printer"

Vertex AI’s LLM (Large Language Model) does the following:
Semantic Search – Understands intent beyond keywords (e.g., "under $100" = price filter).
Synonym & Misspelling Handling – Recognizes "printer" even if typed as "printr".
Contextual Ranking – Prioritizes products matching both relevance and business rules (e.g., promotions, stock availability).

Example:
In the demo, a search for "printer under $100" dynamically filters printers priced ≤$100

Limitations of Commerce Search v3:

Please read this link: Limitations-of-Commerce-Search-v3

Optimizely Consulting & DXP Services | CMS, Commerce, AI

Optimizely is an open, extensible platform providing consistent Digital Touch Points. With the need for going digital increases, so does the demand for a consistent buying experience. Connect content, data, and commerce platforms, enabling access to a seamless buying experience and better back-end connectivity for customers. Leverage Optimizely’s tools to accelerate KPI growth and enhance ...

Blog posts by Vaibhav

Introducing the Optimizely MCP Server: AI That Speaks Commerce Part-II

From conversation to completed transaction.

Eight tools became thirty-four. Browsing became buying.

AI that speaks commerce

AI that acts within commerce

Every step a buyer takes — now a tool the AI can call.

Discover

Build cart

Authenticate

Pay

Submit

Track

Six domains. One job each. Real value behind every group.

API Discovery & Introspection

Product Search & Detail

Full Shopping-Cart Lifecycle

Checkout, Status & History

Secure B2B Identity

Procurement-System Buyer Flow

Passwordless login the AI can't abuse.

Request

Buyer receives

Verify

Act as buyer

● No password grant exposed

● Per-session isolation

● No raw card data

Build it once. Every assistant can use it.

Claude

ChatGPT

Copilots

Spire SSR

Procurement

Five clean layers, one job each.

The business case, in four lines.

Faster time-to-order

Fewer support escalations

Multi-channel by default

Controlled, low-risk rollout

Bring transaction-grade AI to your commerce stack.

Introducing the Optimizely MCP Server: AI That Speaks Commerce Part-I

Introducing the Optimizely MCP Server: AI That Speaks Commerce

Commerce Should Respond to Intent, Not Clicks

The Protocol That Connects AI to Real Systems

How It Works

User speaks intent

AI interprets & selects tools

Commerce engine executes

AI presents & acts

Eight Tools. One Seamless Commerce Experience.

Product Catalog Search

Customer & Order Lookup

Pricing Queries

Inventory Availability

Punchout & Session Ops

Cart Management

Promotion Inspection

CMS & Content Sync

Measurable Outcomes from Day One

The Roadmap Ahead

Ready to bring AI to your commerce stack?

Accelerate Optimizely DAM Adoption: Unlocking Business Value with Metadata Bulk Import

Accelerating Optimizely DAM Adoption

How a Metadata-Driven Bulk Import Utility Unlocks Real Business Value

Executive Summary

Why this matters to leadership

The Business Problem: DAM Adoption Stalls at the Front Door

What the Utility Does: A Five-Step Pipeline

Architectural Value: Why This Is the Right Design

Decoupled Ingestion Architecture

Metadata-First: SEO and Governance by Design

OAuth 2.0 Security — No Human in the Loop

Getting Started: Five Minutes to First Import

Strategic Fit: Where This Accelerates Your Roadmap

Accelerating Optimizely CMS Upgrades with Intelligent Automation

The Business Challenge: The Cost of Manual Migration

Key Business Benefits

1. Massive Cost Reduction

2. Risk Mitigation & Non-Destructive Workflow