MCP server for Sublime Text 4. Lets AI coding agents read and control a running ST instance.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
discover_toolsSearch advanced Sublime capabilities. Invoke a result through batch.Search advanced Sublime capabilities. Invoke a result through batch.
No input schema was published for this tool.
project_searchSearch project files with Sublime Text's native Find in Files engine and return structured matches.Search project files with Sublime Text's native Find in Files engine and return structured matches.
No input schema was published for this tool.
2 of 2 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for Sublime Text 4. Lets AI coding agents read and control a running ST instance.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.