{
  "markdown": "# Sublime-MCP: Universal AI Agent Connector for Sublime Text\n\nGives any MCP-speaking AI agent real control over a running Sublime Text 4\ninstance: run registered ST commands, read/write views and selections, inspect\ntabs and project state, and `eval_python` in Sublime's plugin host for anything\nthe typed tools don't cover.\n\nTwo optional companion plugins extend this:\n\n- **debugger-mcp** — Debugger package DAP tools (breakpoints, stepping,\n  variables, call stacks) over MCP\n- **lsp-mcp** — LSP tools (definition, references, diagnostics, rename, hover)\n  over MCP\n\n## Toolset\n\nSeven workflow tools are advertised by default. `discover_tools` searches the\ncomplete internal catalog of 222 typed Sublime capabilities, and `batch` invokes\ndiscovered capabilities without flooding the model's initial tool context.\ndebugger-mcp and lsp-mcp use the same focused pattern: each advertises seven\nworkflow tools by default, with `debugger_discover_tools` / `lsp_discover_tools`\nand prefixed batch tools providing access to the complete catalogs (104 and\n125 tools respectively).\n\nAgent how-to: [docs/AGENT_GUIDE.md](docs/AGENT_GUIDE.md) (also served live by\n`get_help`). Workflow across all three MCPs: [docs/agents.md](docs/agents.md).\nRelease history: [CHANGELOG.md](CHANGELOG.md).\n\n## Ports\n\nEach plugin serves **MCP streamable HTTP** at `/mcp`, legacy **MCP SSE** at\n`/sse`, and a **plain HTTP bridge**.\nThe bundled Node/Python proxies use sublime-mcp's HTTP bridge only. Defaults:\n\n| Plugin        | MCP SSE                         | HTTP bridge                     | Settings file                        |\n| ------------- | ------------------------------- | ------------------------------- | ------------------------------------- |\n| sublime-mcp   | 9502 (Win) / 9503 (macOS/Linux) | 9500 (Win) / 9501 (macOS/Linux) | `sublime-mcp.sublime-settings`        |\n| debugger-mcp  | 9505                            | 9515                            | `debugger-mcp.sublime-settings`       |\n| lsp-mcp       | 9506                            | 9516                            | `lsp-mcp.sublime-settings`            |\n\nEach settings file takes `\"mcp_port\"` and `\"http_port\"` keys; edit your copy\nunder `Packages/User/` (Preferences > Package Settings) to override the\ndefaults above — no env vars needed.\n\nSSE URL form: `http://127.0.0.1:<sse-port>/sse`. The bundled Node/Python\nproxies talk to sublime-mcp's **HTTP bridge**, not SSE; override with\n`SUBLIME_MCP_BASE` (e.g. `http://127.0.0.1:9500`).\n\n## Installation\n\n### 1. Clone\n\n```bash\ngit clone https://github.com/dpc00/sublime-mcp.git\ncd sublime-mcp\n```\n\n### 2. Install the Sublime Text plugin\n\nSymlink `packages/st-plugin` into ST's `Packages/` directory as `sublime-mcp`.\n\n**Windows (Command Prompt):**\n```cmd\nmklink /J \"%APPDATA%\\Sublime Text\\Packages\\sublime-mcp\" \"C:\\path\\to\\sublime-mcp\\packages\\st-plugin\"\n```\n\n**macOS:**\n```bash\nln -s \"$(pwd)/packages/st-plugin\" \"$HOME/Library/Application Support/Sublime Text/Packages/sublime-mcp\"\n```\n\n**Linux:**\n```bash\nln -s \"$(pwd)/packages/st-plugin\" \"$HOME/.config/sublime-text/Packages/sublime-mcp\"\n```\n\n### 3. Optional companion plugins\n\nSame pattern: symlink `packages/debugger-mcp` and/or `packages/lsp-mcp` into\n`Packages/` under those names.\n\n**Windows:**\n```cmd\nmklink /J \"%APPDATA%\\Sublime Text\\Packages\\debugger-mcp\" \"C:\\path\\to\\sublime-mcp\\packages\\debugger-mcp\"\nmklink /J \"%APPDATA%\\Sublime Text\\Packages\\lsp-mcp\" \"C:\\path\\to\\sublime-mcp\\packages\\lsp-mcp\"\n```\n\n**macOS:**\n```bash\nln -s \"$(pwd)/packages/debugger-mcp\" \"$HOME/Library/Application Support/Sublime Text/Packages/debugger-mcp\"\nln -s \"$(pwd)/packages/lsp-mcp\" \"$HOME/Library/Application Support/Sublime Text/Packages/lsp-mcp\"\n```\n\n**Linux:**\n```bash\nln -s \"$(pwd)/packages/debugger-mcp\" \"$HOME/.config/sublime-text/Packages/debugger-mcp\"\nln -s \"$(pwd)/packages/lsp-mcp\" \"$HOME/.config/sublime-text/Packages/lsp-mcp\"\n```\n\nRestart Sublime Text after linking so the plugins load.\n\n### 4. Configure your agent\n\n**Node:**\n```bash\ncd packages/node-proxy\nnpm install .\nnpx sublime-mcp\n```\n\n**Python:**\n```bash\ncd packages/python-proxy\npip install .\nsublime-mcp\n```\n\nFor Codex, use its native streamable-HTTP configuration; no `mcp-remote`\nwrapper is required:\n\n```toml\n[mcp_servers.sublime-mcp]\ntype = \"http\"\nurl = \"http://127.0.0.1:9502/mcp\"\n\n[mcp_servers.debugger-mcp]\ntype = \"http\"\nurl = \"http://127.0.0.1:9505/mcp\"\n\n[mcp_servers.lsp-mcp]\ntype = \"http\"\nurl = \"http://127.0.0.1:9506/mcp\"\n```\n\nRestart or open a new Codex session after changing MCP configuration. Verify\nthe entire path before debugging agent behavior:\n\n```bash\nnpx sublime-mcp doctor\nnpx sublime-mcp doctor --all\n```\n\nThe first command checks sublime-mcp. `--all` also checks debugger-mcp and\nlsp-mcp. The report separately checks each HTTP bridge, MCP handshake, and\nfocused tool catalog. From Sublime's Command Palette,\n`MCP Commander: Connection Doctor` shows the main server-side state.\n\nOther MCP clients may use the legacy SSE URL (Windows example):\n\n```json\n{\n  \"mcpServers\": {\n    \"sublime-mcp\": { \"type\": \"sse\", \"url\": \"http://127.0.0.1:9502/sse\" }\n  }\n}\n```\n\nEach plugin's MCP server starts automatically when ST loads it. To stop or\nrestart sublime-mcp's, run \"MCP Commander: Server Status\" from the Command\nPalette. Check View > Show Console for startup confirmation.\n\n## Agent skill\n\nInstallable Codex skills are in `skills/sublime-mcp`,\n`skills/sublime-debugger`, and `skills/sublime-lsp`. Copy the desired\ndirectories to your Codex skills directory or install them through your normal\nskill workflow.\n",
  "bytes": 5546,
  "sha": "caf3f881262de96acaca6d7e0fa62cbca082b58c0a5531030b4b8a6b20a80aa4",
  "repo_slug": "dpc00/sublime-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_dpc00_sublime_mcp_80e96b52/readme"
}