VS Code extension that exposes Universe Editor's tool surface to GitHub Copilot
Chat (Agent mode) and any other VS Code MCP-aware client through the
Model Context Protocol.
The extension bundles a stdio MCP server which forwards each tool call to the
running Universe Editor over its existing EditorHttpService channel
(http://127.0.0.1:8886).
Requirements
VS Code 1.101+ (the version that introduced mcpServerDefinitionProviders).
A running Universe Editor on the local machine. The extension does not start
the editor.
Provided MCP tools
ue_list_tools — list every Universe Editor tool, with optional name /
category filters and a summary-only mode.
ue_create_session — create a tool-call session bound to an editor object
(defaults to whichever object is currently active in the editor).
ue_call_tool — call a Universe Editor tool inside a session.
ue_get_session / ue_close_session — inspect / close a managed session.
Settings
Setting
Default
Notes
universeEditorMcp.editorHttpPort
8886
Editor HTTP port. The editor itself hard-codes 8886 in many places — change only if you know what you are doing.
universeEditorMcp.timeoutMs
60000
How long to wait for a tool response before timing out.
Changing either setting causes VS Code to re-resolve the MCP server.
Local development
cd extension
npm install
npm run build # bundles ../src into out/bridge.mjs and compiles extension.ts
code --extensionDevelopmentPath=.
In the launched window, open Copilot Chat in Agent mode and the
universe-editor server should appear under MCP: List Servers.
Packaging
cd extension
npm run package # produces universe-editor-mcp-<version>.vsix
The resulting .vsix contains only out/ plus this README — no node_modules
tree, because the bridge is bundled by esbuild.
