MCP 서버로 실행되는 Eclipse IDE를 켭니다. 외부 LLM 클라이언트(Claude Code, Cursor, MCP-capable Agent)는 파일에서 저렴하게 재구성할 수 없는 IDE를 요청할 수 있습니다. 해결된 Java 모델, 빌더의 문제 마커, 디버거 및 라이브 작업대.

Vogella GmbH에 의해 구축 및 유지, 우리의 컨설팅 및 레거시 코드 및 코드 최적화에 대한 우리의 AI 기반 Java 정리 서비스.

서버는 ** 기본적으로 비활성화 **, 127.0.0.1]에서만 듣고 Bearer 토큰없이 모든 요청을 거부합니다. 대부분의 도구는 읽기 전용입니다. 무언가를 변경하는 모든 도구는 자체 설명에서 말한다, 그리고 그들은 기본적으로 건조 실행 할 수 있습니다.

설치

Eclipse에서 *Help > 새 소프트웨어 설치 *, 추가

그리고 Eclipse MCP Server 기능을 설치합니다. 이 사이트는 최신 빌드를 제공합니다. 이전 버전은 각 GitHub 릴리스에 첨부 된 저장소 zip으로 사용할 수 있습니다. Add > Archive.

건물

JDK 25 및 Maven 3.9 이상이 필요합니다.

p2 저장소는 update-site/com.vogella.eclipse.mcp.repository/target/repository에서 끝납니다.

Eclipse MCP Server

Turns a running Eclipse IDE into an MCP server, so that external LLM clients (Claude Code, Cursor, any MCP-capable agent) can ask the IDE for what they cannot cheaply reconstruct from files: the resolved Java model, the builder’s problem markers, the debugger and the live workbench.

Built and maintained by vogella GmbH, and used in our consulting and in our AI based Java cleanup services for legacy code and code optimization.

The server is disabled by default, listens on 127.0.0.1 only and rejects every request without the bearer token. Most tools are read-only; every tool that changes something says so in its own description, and those that can default to a dry run do.

Installing

In Eclipse, choose Help > Install New Software, add

https://vogellacompany.github.io/eclipse-mcp-server/

and install the Eclipse MCP Server feature. The site carries the newest build only; older versions are available as the repository zip attached to each GitHub release, through Add > Archive.

Building

Requires JDK 25 and Maven 3.9 or newer.

mvn clean verify

The p2 repository ends up in update-site/com.vogella.eclipse.mcp.repository/target/repository. To work on the code in Eclipse, import the projects with Search for nested projects enabled and set target-platform/com.vogella.eclipse.mcp.target/com.vogella.eclipse.mcp.target.target as the active target platform.

Every push to main publishes to the update site; pushing a v tag additionally creates a GitHub release with the repository zip.

Enabling the server

Preferences > General > MCP Server:

• Enable MCP server, off by default
• Port, 8642 by default
• Tool call timeout, 30 seconds by default
• UI thread wait, 25 seconds by default: how long a tool waits for a busy UI thread before it withdraws the request, capped by the tool call timeout

Changes apply immediately. The page also shows the URL, the bearer token and the discovery file, and can regenerate the token. By default, if the configured port is taken, the server stays down and the page says why. To let the operating system choose an available port at each start, add -Dcom.vogella.eclipse.mcp.server.ephemeralPort=true after -vmargs in eclipse.ini; the page then disables the port field, and the stored value applies again once the property is gone. The selected port is written to the workspace discovery file; clients must rediscover that endpoint after every restart.

In an RCP application

The server starts through a declarative service, so an RCP application needs org.apache.felix.scr and a workspace, but no org.eclipse.ui.startup.