sf-log-analyzer
MCP server for Salesforce debug log analysis. Connect to any Salesforce org, set up log capture, scan logs for errors, and search log content — all from your AI-powered editor (Cursor, VS Code, etc.).
Quick Start
Add to your .cursor/mcp.json or .vscode/mcp.json:
{
"mcpServers": {
"sf-log-analyzer": {
"command": "uv",
"args": ["tool", "run", "--python", ">=3.10", "sf-log-analyzer"]
}
}
}
Requires uv installed. Works on macOS, Linux, and Windows. No other setup needed.
Tools (16 total)
Connection
- sf_list_orgs — List Salesforce CLI-authorized orgs
- sf_connect_org — Connect via CLI alias
- sf_connect — Connect via raw session ID (for subscriber/ISV orgs)
- sf_disconnect — Disconnect and clear cache
Log Capture Setup
- sf_list_users — List active users
- sf_list_debug_levels — List existing debug levels
- sf_create_debug_level — Create a new debug level
- sf_setup_logging — One-step: create debug level + trace flag
- sf_list_trace_flags — List active trace flags
- sf_create_trace_flag — Create a trace flag
- sf_delete_trace_flag — Delete a trace flag
Debug Log Analysis
- sf_list_logs — List debug logs (with filters)
- sf_get_log — Fetch full log body
- sf_scan_log — Scan a log for errors, exceptions, governor limits
- sf_scan_all_logs — Batch scan with summary
- sf_search_log — Full-text search within a log
Requirements
- Python 3.10+
- Salesforce CLI (
sf) for CLI-based connections (optional)
License
MIT
Metadata
Release files for sf-log-analyzer 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sf_log_analyzer-0.1.5.tar.gz | 12.8 kB | Without provenance | Details for sf_log_analyzer-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sf_log_analyzer-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for sf_log_analyzer-0.1.5-py3-none-any.whl |
Total release size: 27.3 kB
Release files / sf_log_analyzer-0.1.5.tar.gz
| Download URL | sf_log_analyzer-0.1.5.tar.gz |
|---|---|
| Size | 12.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8804ad99bf87a65b0e79835327d2b38a020f423e77361857921f865289d7ccd
|
|
BLAKE2b-256 checksum How to use checksums |
baf99b6baab036ab83588af0b691b98e64441674c70ca3f38bec9d910d87d425
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.9 {"installer":{"name":"uv","version":"0.10.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / sf_log_analyzer-0.1.5-py3-none-any.whl
| Download URL | sf_log_analyzer-0.1.5-py3-none-any.whl |
|---|---|
| Size | 14.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f79531ff80e52b45b7d075b3e78192e906a8187572abc7f77a1466d331e31b49
|
|
BLAKE2b-256 checksum How to use checksums |
f28186b422a54ec98ef640f88a0ae3244161b3d977e4eed78d1e089ad3a54510
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.9 {"installer":{"name":"uv","version":"0.10.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for sf-log-analyzer 0.1.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.