sublime-mcp
Related Servers
Alternatives to sublime-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceRemote-control Unity Editor from any AI IDE via file-based IPC — 62 tools, zero dependencies6523Apache 2.0
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to Nuke for compositing tasks via natural language.15MIT
- AlicenseBqualityDmaintenanceConnects OpenSpec specification system to AI coding assistants, enabling automated spec-driven development workflows.1130 npm2MIT
- AlicenseBqualityBmaintenanceConnects a compatible AI assistant to a running Blender session so it can build, arrange, edit and validate 3D scenes using reusable ready-made actions instead of writing new Python for common operations. It keeps a persistent local bridge open for grouped actions and offers built-in scene checks for floating objects, orientation and clearance problems.93MIT

Elgato MCP Serverofficial
AlicenseAqualityBmaintenanceBridges AI assistants with Elgato apps via IPC, enabling dynamic tool discovery and notification forwarding.11,618 npm15MIT
glade-mcpofficial
AlicenseNot gradedqualityAmaintenanceConnect any MCP-compatible AI client (Claude Code, Cursor, Windsurf) to Unity or Godot. 300+ granular tools, an editor aware system prompt, game design document project context, script semantic search, and skill calibration.202MIT
TDQS
Scored across 59 tools
Many tools have overlapping purposes (e.g., get_file_content, get_view_content, get_view_chars), and while descriptions are detailed, an agent might struggle to choose the correct one for a given scenario. Some tools like eval_python and run_command are distinct but others blur boundaries.
The naming convention is largely consistent with verb_noun snake_case (e.g., add_folder, get_open_files, set_syntax). A few deviate slightly (send_to_view, eval_python) but these are still clear and follow the overall pattern.
59 tools is excessive for a single MCP server. While Sublime Text operations can be many, this count overwhelms an agent with choices, many of which are overly specific (e.g., get_view_phantoms, get_line_count). A more focused set would improve usability.
The tool surface covers a wide range of editor actions (file management, editing, search, project, settings, terminal), but notable gaps exist: no create_file, rename_file, or delete_file tools. Basic file lifecycle operations are incomplete.