Some feedback (from claude itself lol)

[creatorrr]

Thanks for continuing to work on this repo. I think this has tremendous potential! :)

Here's some "feedback" from claude itself. Thought it might be useful:

⎿ Critical Assessment of LSP MCP Server

After testing the LSP MCP tools, here's my critical assessment:

Strengths:

1. Real-time diagnostics - Immediately useful for catching import and type errors
2. Symbol navigation - Definition lookup works well for jumping to implementations
3. Call hierarchy - Callers/callees provide good code flow understanding
4. Type information - Hover gives quick type hints

Significant Limitations:

1. Token limit issues - The references tool often exceeds token limits for common symbols (e.g., "generate" returned 43K+ tokens)
2. No filtering/pagination - Can't limit scope when searching references
3. Basic hover info - Only shows type, no docstrings or signatures
4. Limited compared to existing tools - Grep/Glob are often more practical

Comparison with Existing Tools:

LSP definition vs Grep/Read:

• LSP: Precise symbol resolution
• Grep/Read: More flexible, works with any text pattern

LSP references vs Grep:

• LSP: Semantic understanding but hits token limits
• Grep: Faster, more predictable, supports filtering

LSP diagnostics vs Running tests/linters:

• LSP: Instant feedback without execution
• Tests: Actual runtime validation

Verdict: Moderately Useful but Needs Improvements

The LSP tools are helpful supplements but don't replace existing tools. Key improvements needed:

1. Add pagination/filtering to references
2. Include docstrings in hover
3. Support scope limiting (e.g., "references in /tests only")
4. Better token management

[creatorrr]

If these sound useful and aligned with what you were thinking, will try to create a PR

[creatorrr]

After extensive testing, here's my honest assessment:

✅ What Works Well:

1. Symbol Renaming - The rename_symbol tool is genuinely excellent! It renamed health to vitality across all occurrences correctly. This is better than find-and-replace.
2. Definition Lookup - Works reliably for finding where symbols are defined, showing full implementation.
3. Editing with Line Numbers - The edit_file tool with line-based editing is cleaner than string-based Edit tool for some use cases.
4. Type Information - Hover provides quick type hints (though limited).

❌ Major Issues:

1. References Don't Work Properly - Animal.eat references returned nothing, while grep found the usage immediately. The references tool seems unreliable.
2. No Cross-File Intelligence - Diagnostics missed the import error in animals.py (imports from base not .base).
3. Token Limit Problems - Common symbols like generate exceed limits, making the tool unusable for real codebases.
4. Limited Hover Info - Only shows type, no docstrings or signatures.
5. Callers/Callees Inconsistent - Often returns empty results when there are actual calls.

📊 Direct Comparisons:

Task	LSP Tool	Existing Tool	Winner
Find definition	mcp__lsp__definition	Grep with pattern	Tie - Both work well
Find usages	mcp__lsp__references	Grep with pattern	Grep - More reliable
Rename symbol	mcp__lsp__rename_symbol	Edit with replace_all	LSP - Semantic awareness
Check errors	mcp__lsp__diagnostics	Bash with linter	Bash - Catches more issues
Edit file	mcp__lsp__edit_file	Edit tool	Tie - Different use cases

🎯 Final Verdict: LIMITED USEFULNESS

Rating: 4/10

The LSP MCP server is not ready for production use. While rename_symbol is genuinely useful and definition works well, the core features like references and diagnostics are unreliable. For
most tasks, existing tools (Grep, Edit, Bash) are more dependable.

Recommendations:

1. Fix the references tool - it's broken
2. Add filtering/pagination for large results
3. Include docstrings in hover
4. Make diagnostics actually catch import errors
5. Add scope limiting options

Should you use it? Only for symbol renaming. For everything else, stick with Grep, Read, and Edit.