sfcc-logs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sfcc_logfileA | Get SFCC last Log file records. If logFileName is not provided list all available log files. If provided, return the last "count" lines from the file. |
| clean_sfcc_logfileA | Clean/reset a specific SFCC log file by overwriting it with a clean message. |
| get_latest_errorB | Retrieve the latest Error logs from the active appserver.Tails the newest error log file. |
| get_latest_warnB | Retrieve the latest Warning logs from the active appserver.Tails the newest warn log file. |
| get_latest_infoA | Retrieve the latest Info logs from the active appserver.Tails the newest info log file. |
| get_latest_debugB | Retrieve the latest Debug logs from the active appserver.Tails the newest debug log file. |
| summarize_logsB | Retrieve a statistical audit overview of all log files generated on a specific date (clutter categories, active volume, newest active items). |
| search_logsC | Searches across multiple log files matching logLevel/date for a specific text pattern. |
| get_latest_job_log_filesB | Lists active background cron job log files (starting with job- prefix) newest first. |
| search_job_logs_by_nameB | Filters background job logs strictly by a specific job ID/name (e.g. (CatalogImport). |
| get_job_log_entriesB | Retrieve trailing log entries inside a specific job log, optionally filtered by severity. |
| search_job_logsC | Searches for a text pattern strictly inside background job logs. |
| get_job_execution_summaryB | Parses standard SFCC job steps boundries inside the newest job log file, returning a structured steps executioin audit timeline and step statuses (OK/ERROR/RUNNING). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct log operation or type (error, warn, info, debug, job, general). Descriptions clearly differentiate overlapping aspects like search_job_logs vs search_logs.
All tools follow a verb_noun pattern with consistent use of get_, search_, clean_, summarize_. No mixing of conventions.
13 tools is well-scoped for a log management server, covering reading by severity, searching, summarizing, clearing, and job-specific operations without excess.
The toolset covers all major log operations: retrieval by severity, search, summary, file listing, clearing, and job log details. No obvious gaps for the domain.