SAP Commerce MCP Server

Created By
Dunkansdka year ago
SAP Commerce (Hybris) MCP Server
Overview

What is SAP Commerce MCP Server?

SAP Commerce MCP Server is a Model Context Protocol server that integrates with SAP Commerce Cloud's OCC APIs, enabling natural language interactions with product data through Claude.

How to use SAP Commerce MCP Server?

To use the server, install the dependencies, build the project, and start the server. You can then interact with the server using natural language queries to search for products, check stock availability, and manage shopping carts.

Key features of SAP Commerce MCP Server?

  • Natural language product search and advanced filtering
  • Detailed product information and stock availability checks
  • Cart management and order status tracking
  • Real-time health monitoring and performance analytics
  • Personalized product recommendations and promotions

Use cases of SAP Commerce MCP Server?

  1. Searching for products using conversational queries.
  2. Managing shopping carts and checking out products.
  3. Monitoring service health and performance metrics.
  4. Accessing product reviews and ratings.

FAQ from SAP Commerce MCP Server?

  • Can I use natural language to search for products?

Yes! The server supports natural language queries for product searches.

  • How do I check product availability?

You can check stock levels by querying the product code.

  • Is there support for OAuth2 authentication?

Yes, the server supports OAuth2 for authenticated requests.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Dunkansdk
Star
0
Language
TypeScript
License
GPL-3.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago