catalog-api-mcp-server

Created By
davidlbla year ago
Overview

what is catalog-api-mcp-server?

The catalog-api-mcp-server is a tool designed to validate or manage the status of P&C (presumably Products and Catalogs) through a local MCP (Microservices Communication Protocol) server.

how to use catalog-api-mcp-server?

To use the catalog-api-mcp-server, you need to activate the MCP agent in Visual Studio Code (VSC) and configure the settings.json file with the appropriate server commands. After starting the MCP server, you can interact with the configured tools to query information from the MCP.

key features of catalog-api-mcp-server?

  • Local server setup for managing P&C status
  • Integration with Visual Studio Code for easy configuration
  • Ability to query information based on defined tools

use cases of catalog-api-mcp-server?

  1. Validating the status of product catalogs in a local environment.
  2. Managing product information through a microservices architecture.
  3. Testing and debugging catalog-related services in development.

FAQ from catalog-api-mcp-server?

  • What is the purpose of the catalog-api-mcp-server?

It is used to validate and manage the status of products and catalogs through a local MCP server.

  • How do I configure the server?

You need to add specific configurations in the settings.json file in VSC and start the MCP server.

  • Can I use this tool for production environments?

This tool is primarily designed for development and testing purposes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
davidlbl
Star
0
Language
Java
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