Eclipse MCP Server

Turns a running Eclipse IDE into an MCP server, so that external LLM clients such as Claude Code or Cursor can ask the IDE for information they cannot cheaply reconstruct from files alone.

An agent with a shell already has files, grep and git. What it does not have is the resolved Java model, the problem markers of the incremental builder, the Error Log and the file you are currently looking at. Those are the capabilities exposed here.

The server finds references with the JDT search engine, splitting field accesses into reads and writes so that a field written but never read is visible as dead. It returns type hierarchies and the source of types from jars with a source attachment. It reports the compilation errors of the workspace, and the entries of the Error Log including the full stack traces of UI freezes, which never become problem markers. It reads preferences and reports which scope each value comes from. It reports the active editor with its cursor and selection, so that a model can resolve "this method".

A few tools change something, and each says so in its own description: organize imports, format, run a build, open and close projects, write preferences within an allowlist, and set the execution environment of plug-in projects together with the matching compiler settings. There is no general file writing, no refactoring, no terminal and no debugger control.

The server is disabled by default. It binds to the loopback interface only, checks the Host header, and rejects every request that does not carry a bearer token. Enable it under Preferences > General > MCP Server, which also shows the URL and token to configure a client with.

Sources, documentation and issue tracker: https://github.com/vogellacompany/eclipse-mcp-server

For help and support: info@vogella.com