MyEclipse MCP Server

1. Prerequisites

The MCP server requires a valid Spring + AI or higher license. If you have a Pro or Std license, you can try this capability for free for 30 days using our upgrade trial offering within the product.

If you have the GitHub Copilot plugin installed, it will automatically be configured with the MyEclipse MCP server, with the tools directly accessible from the chat/agent once approved. If you do not have this plugin installed and/or wish to use the MCP server with another tool, please see the section below for configuration instructions.

2. Configuration

The MCP server preference page can be found at Preferences > MyEclipse > AI > Model Context Protocol (MCP). The MCP server is enabled by default if you have the right license level and the GitHub Copilot plugin installed. If you have a lower license level, you will be offered an upgrade trial when enabling the server. The port at which the server listens can be customized and a bearer token is required for additional security, though this can be turned off. Due to lifecycle limitations, changes to the MCP configuration, including enabling or disabling the server only take effect after restarting MyEclipse.

Approving the MyEclipse MCP Server

For use with GitHub Copilot in the IDE, the MyEclipse MCP server must be approved for use. You can do this in two ways.

• Click the “GitHub Copilot approval required” link on the above preference page.
• Open Preferences > GitHub > Model Context Protocol (MCP) page, click, “Edit MCP Servers from Plug-ins”.

Click Approve in the resulting dialog. After approval, all tools are enabled by default but they can be individually enabled and disabled in the tools dialog.

Configuration in Other Tools

The MyEclipse MCP server is available at

http://localhost:<port>/mcp

with bearer token authentication. To enable access from other tools, use the above URL.

Here are a couple of configuration examples that will help you set it up in any tool.

VS Code

"myeclipse-server": {
 "type": "http",
 "url": "http://localhost:50555/mcp",
 "headers": {
  "Authorization": "Bearer <TOKEN>"
 }
}

Claude Desktop

"myeclipse-server": {
 "command": "npx",
 "args": [
  "mcp-remote",
  "http://localhost:50555/mcp",
  "--header",
  "Authorization:${AUTH_TOKEN}"
 ],
 "env": {
  "AUTH_TOKEN": "Bearer <TOKEN>"
 }
}

3. Available MCP Tools

General Usage Guidelines
The server exposes a broad set of IDE and workspace automation tools. While the tools are listed here by name, use the details below simply as a list of all the current capabilities of the MyEclipse MCP server. Continue to interact with your AI agent as before and it should pick the right tool automatically, sometimes chaining multiple tool calls together. You do not need to be exact with names, for instance project names or server names could be loosely specified and the agent may use other tool calls to figure out the intended resource if desired.

Database Tools

list_database_profiles
Lists configured database connection profiles.

execute_sql_query
Executes SQL queries against configured databases.
Capabilities include:

• Running ad hoc queries
• Refining follow-up queries conversationally
• Opening database connections automatically
• Creating:
  • Views
  • Tables
  • Stored procedures
  • Database functions (where supported)

Results are shown both in MyEclipse result views and chat.

Application Server Tools

list_appservers
Lists Jakarta EE application servers configured in the workspace.

deploy_undeploy_application
Deploys or undeploys projects to application servers.

list_deployments
Lists deployments associated with a server.

start_stop_appserver
Starts or stops app servers in:

• Run mode
• Debug mode
• Profile mode

Project & Workspace Tools

list_projects
Lists workspace projects.

get_project_structure
Returns a text-based project tree structure.

Supports depth-based traversal and helps AI tools quickly identify source organization and project structure.

import_project
Imports existing projects from a directory and creates Eclipse project metadata if needed.

Git Tools

list_configured_git_repositories
Lists Git repositories configured in Eclipse.

scan_directory_for_git_repositories
Scans directories for Git repositories.

import_git_repository
Imports repositories from:

• Local directories
• Remote Git URLs

Supports automatic cloning into configured Git locations.

list_git_files / list_remote_git_files
Lists files in local or remote repositories to help AI agents analyze repository structure efficiently.

Maven Tools

maven_search
Searches Maven Central by keyword, similar to typing a term into the basic Maven Central search box.

maven_get_artifact_versions
Returns a sorted list of all available versions for a specific Maven artifact identified by groupId and artifactId.

maven_search_by_groupid / maven_search_by_artifactid
Returns all artifacts under a given Maven groupId or artifactId, showing the most recently released version for each artifact.

maven_search_by_coordinates
Performs an advanced coordinate search on Maven Central. You can supply any combination of:

• groupId
• artifactId
• version
• packaging
• classifier

All provided parameters are combined with AND logic.

Example use

• Search for com.google.inject:guice:7.0.0
• Search for jackson-databind sources artifacts

maven_search_by_classname
Finds Maven artifacts that contain a class with the given short class name. This is useful when you know a class name but not which library provides it.

maven_search_by_fqcn
Finds Maven artifacts that contain the specified fully-qualified class name. This is more precise than short-class-name search and returns results down to the artifact version.

maven_search_by_sha1
Identifies a Maven artifact by the SHA-1 checksum of its JAR file. This is useful for auditing unknown JARs on the classpath or verifying artifact integrity.

maven_get_pom
Downloads and returns the POM file content for a specific Maven artifact version from the Central Repository.

maven_get_latest_version
Convenience tool that returns only the latest released version string for a given Maven groupId + artifactId. This is useful for quick dependency-upgrade checks.

Console Tools

console_output
Provides access to the currently focused console output.

Example use cases:

• Stack trace analysis
• Breakpoint placement assistance
• Runtime debugging workflows

Eclipse Information Tools

eclipse_version
Returns:

• Running Eclipse product
• Product version
• Eclipse platform version