Skip to main content
Glama

SFCC Development MCP Server

by taurgis
log-handler.ts1 kB
import { AbstractLogToolHandler } from './abstract-log-tool-handler.js'; import { HandlerContext } from './base-handler.js'; import { GenericToolSpec } from './base-handler.js'; import { ToolArguments } from './base-handler.js'; import { LOG_TOOL_CONFIG } from '../../tool-configs/log-tool-config.js'; import { LOG_TOOL_NAMES_SET, LogToolName } from '../../utils/log-tool-constants.js'; /** * Handler for standard log tools using config-driven dispatch * Handles log reading, searching, and analysis operations */ export class LogToolHandler extends AbstractLogToolHandler<LogToolName> { constructor(context: HandlerContext, subLoggerName: string) { super(context, subLoggerName); } canHandle(toolName: string): boolean { return LOG_TOOL_NAMES_SET.has(toolName as LogToolName); } protected getToolNameSet(): Set<LogToolName> { return LOG_TOOL_NAMES_SET; } protected getToolConfig(): Record<string, GenericToolSpec<ToolArguments, any>> { return LOG_TOOL_CONFIG; } }

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taurgis/sfcc-dev-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server