Skip to content

Expose IDE Rename tool via MCP for improved GenAI refactoring support #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yuriipelekh opened this issue May 22, 2025 · 0 comments
Open

Comments

@yuriipelekh
Copy link

Context:

When working with large files or complex codebases, GenAI copilots (such as GitHub Copilot, Cursor, or similar tools) struggle with reliable and accurate refactoring due to token limitations and a lack of semantic awareness. IDE-native refactoring tools like Rename rely on the Abstract Syntax Tree (AST) and are significantly more precise, supporting correct symbol resolution, scoping, and cross-file updates.

Currently, the JetBrains MCP server exposes some code insight and navigation capabilities, but essential mechanical refactoring tools like Rename are unavailable via MCP.

Problem:

GenAI copilots can't reliably perform symbol renaming at scale, often introducing subtle bugs.

Developers using Copilot or automated workflows in agentic IDEs must rely on fallback heuristics instead of structured, AST-backed refactorings.

Lack of access to internal rename/refactoring tools limits the effectiveness of GenAI-powered refactoring, especially in larger projects.

Proposed:

Expose the IDE Rename functionality via the MCP server. Ideally, this endpoint should:

Optionally, expose other refactoring tools (e.g., Extract Method, Inline Variable, Move Class) as separate MCP tools to provide a broader foundation for safe, AI-assisted refactoring.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant