You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: