Sublime Text MCP server

Sublime-MCP: Universal AI Agent Connector for Sublime Text

Gives any MCP-speaking AI agent real control over a running Sublime Text 4 instance: run registered ST commands, read/write views and selections, inspect tabs and project state, and eval_python in Sublime's plugin host for anything the typed tools don't cover.

Controlling another installed Sublime package (a debugger, a language server, anything else) doesn't need its own dedicated MCP server — getpackagemcpinfo plus evalpython/run_command covers it directly. See skills/package-skill-generator to turn a one-time investigation into a small, reusable skill file instead.

Toolset

Seven workflow tools are advertised by default. discover_tools searches the complete internal catalog of 238 typed Sublime capabilities, and batch invokes discovered capabilities without flooding the model's initial tool context.

Agent how-to: AGENTGUIDE.md (also served live by gethelp). Release history: CHANGELOG.md.

Ports

sublime-mcp serves MCP streamable HTTP at /mcp, legacy MCP SSE at /sse, and a plain HTTP bridge. The bundled Node/Python proxies use sublime-mcp's HTTP bridge only. Defaults:

The settings file takes "mcpport" and "httpport" keys; edit your copy under Packages/User/ (Preferences > Package Settings) to override the defaults above — no env vars needed.

SSE URL form: http://127.0.0.1:/sse. The bundled Node/Python proxies talk to sublime-mcp's HTTP bridge, not SSE; override with SUBLIMEMCPBASE (e.g. http://127.0.0.1:9500).

Security

Both servers are loopback-only (127.0.0.1) by default and have no authentication — one of the tools they expose (eval_python) is arbitrary code execution in Sublime's own process, so treat this server as equivalent in trust level to your own login session. All of the following are keys in MCP Commander.sublime-settings:

127.0.0.1, making both servers reachable from every other device on your network, still with no authentication. Only turn this on for a specific reason a client can't reach 127.0.0.1 directly (e.g. a WSL client when WSL's networking mode doesn't forward localhost to the Windows host).

• allowlanaccess (default false) — binds 0.0.0.0 instead of

Authorization: Bearer header on every request. This is the one control that works regardless of bind address, since loopback-only doesn't protect against another process, or another user on a shared/multi-user machine, reaching 127.0.0.1 on the same host. Generate a real random value yourself; don't use a short or guessable string. Not every MCP client UI exposes custom headers — check yours supports one before relying on this. If you connect through the bundled Node/Python proxy instead of a direct SSE/HTTP URL, set the same value as SUBLIMEMCPTOKEN in the proxy process's environment.

• authtoken** (default unset) — requires a matching

and hide from discovery entirely, e.g. ["evalpython", "runcommand"] to remove the two tools with the broadest reach while keeping the rest of the server usable.

• disabledtools** (default []) — a list of tool names to refuse

There is no cross-origin access at all: the real tool-call endpoints send no Access-Control-Allow-Origin header, so a webpage's JavaScript running in a browser cannot reach them even if it's running on the same machine.

Installation

1. Install the Sublime Text plugin

Shortened. The full README is on GitHub.