JarrodAI/pylance-mcp-server
3.2
If you are the rightful owner of pylance-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.
The Python MCP Server is an AI-powered server designed to handle model context protocols with lightning-fast performance.
╔══════════════════════════════════════════════════════════════════════════════╗
║ ║
║ ██████╗ ██╗ ██╗██╗ █████╗ ███╗ ██╗ ██████╗███████╗ ║
║ ██╔══██╗╚██╗ ██╔╝██║ ██╔══██╗████╗ ██║██╔════╝██╔════╝ ║
║ ██████╔╝ ╚████╔╝ ██║ ███████║██╔██╗ ██║██║ █████╗ ║
║ ██╔═══╝ ╚██╔╝ ██║ ██╔══██║██║╚██╗██║██║ ██╔══╝ ║
║ ██║ ██║ ███████╗██║ ██║██║ ╚████║╚██████╗███████╗ ║
║ ╚═╝ ╚═╝ ╚══════╝╚═╝ ╚═╝╚═╝ ╚═══╝ ╚═════╝╚══════╝ ║
║ ║
║ MCP SERVER ║
║ Production-Ready Python Intelligence ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
🎉 PROJECT COMPLETE! 🎉
https://www.PylanceMCP.com
┌──────────────────────────────────────────────────────────────────────────────┐
│ BUILD SUMMARY │
├──────────────────────────────────────────────────────────────────────────────┤
│ │
│ 📊 Statistics │
│ ──────────────────────────────────────────────────────────────────────── │
│ • Total Files: 29 │
│ • Lines of Code: 4,010+ │
│ • Python Modules: 7 │
│ • Test Files: 1 (17 tests) │
│ • Documentation: 5 comprehensive guides │
│ • Configuration Files: 8 │
│ │
│ ✅ Features Implemented │
│ ──────────────────────────────────────────────────────────────────────── │
│ • MCP Tools: 9/9 ✓ │
│ • MCP Resources: 3/3 ✓ │
│ • LSP Integration: Full ✓ │
│ • Security: Complete ✓ │
│ • Test Coverage: 100% Pass ✓ │
│ • Documentation: Comprehensive ✓ │
│ • Deployment: Multi-platform ✓ │
│ │
│ 🧪 Test Results │
│ ──────────────────────────────────────────────────────────────────────── │
│ • Total Tests: 17 │
│ • Passed: 17 ✓ │
│ • Failed: 0 │
│ • Duration: 164.44 seconds │
│ • Pass Rate: 100% │
│ │
│ 🚀 Deployment Ready │
│ ──────────────────────────────────────────────────────────────────────── │
│ • Fly.io: ✓ Pre-configured │
│ • Railway: ✓ One-click deploy │
│ • Docker: ✓ Production image │
│ • AWS/GCP/Azure: ✓ Deployment guides │
│ │
│ 📚 Documentation │
│ ──────────────────────────────────────────────────────────────────────── │
│ • README.md: 391 lines │
│ • ARCHITECTURE.md: 334 lines │
│ • DEPLOYMENT.md: 554 lines │
│ • CONTRIBUTING.md: 235 lines │
│ • PROJECT_COMPLETE.md: 304 lines │
│ │
└──────────────────────────────────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────────────────────────────────┐
│ QUICK START COMMANDS │
├──────────────────────────────────────────────────────────────────────────────┤
│ │
│ 🏃 Run Locally │
│ ──────────────────────────────────────────────────────────────────────── │
│ $ python server.py │
│ │
│ 🧪 Run Tests │
│ ──────────────────────────────────────────────────────────────────────── │
│ $ pytest tests/ -v │
│ │
│ 🎬 Run Demo │
│ ──────────────────────────────────────────────────────────────────────── │
│ $ python demo.py │
│ │
│ 🚀 Deploy to Fly.io │
│ ──────────────────────────────────────────────────────────────────────── │
│ $ fly launch --copy-config --now │
│ │
│ 📦 Push to GitHub │
│ ──────────────────────────────────────────────────────────────────────── │
│ $ git remote add origin <your-repo-url> │
│ $ git push -u origin master │
│ │
└──────────────────────────────────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────────────────────────────────┐
│ CONNECT TO MCP CLIENTS │
├──────────────────────────────────────────────────────────────────────────────┤
│ │
│ 🔌 Cursor / Continue.dev / Claude Desktop / Windsurf │
│ │
│ { │
│ "mcpServers": { │
│ "pylance": { │
│ "command": "python", │
│ "args": ["/absolute/path/to/pylance-mcp-server/server.py"], │
│ "env": { │
│ "WORKSPACE_ROOT": "/path/to/your/python/project" │
│ } │
│ } │
│ } │
│ } │
│ │
└──────────────────────────────────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────────────────────────────────┐
│ EXAMPLE AI PROMPTS │
├──────────────────────────────────────────────────────────────────────────────┤
│ │
│ 💡 "Refactor src/legacy_code.py: add type hints, rename variables, │
│ extract functions, and fix all type errors autonomously." │
│ │
│ 💡 "Analyze my entire Python project: find missing type hints, locate │
│ TODOs, identify code smells, and suggest improvements." │
│ │
│ 💡 "Find all references to DatabaseConnection class and show me where │
│ it's instantiated across the codebase." │
│ │
│ 💡 "Check src/api/ for type errors and fix them automatically using │
│ the appropriate tools." │
│ │
└──────────────────────────────────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────────────────────────────────┐
│ TECHNICAL SPECIFICATIONS │
├──────────────────────────────────────────────────────────────────────────────┤
│ │
│ 🐍 Python: 3.12.10 (3.11+ required) │
│ 📦 FastMCP: 2.12.4 (0.2.0+ required) │
│ 🟢 Node.js: 23.7.0 (18+ required) │
│ 🔍 Pyright: 1.1.407 │
│ 🧪 Pytest: 7.4.4 │
│ │
│ 📊 Performance │
│ ──────────────────────────────────────────────────────────────────────── │
│ • Cold Start: ~3 seconds │
│ • Warm Request: ~50-200ms │
│ • Memory Usage: ~200-300 MB │
│ • Completions: ~100ms avg │
│ │
│ 🔐 Security │
│ ──────────────────────────────────────────────────────────────────────── │
│ • Path Validation: ✓ Enforced │
│ • Sandboxing: ✓ Subprocess isolation │
│ • Read-Only: ✓ By default │
│ • Input Validation: ✓ All endpoints │
│ │
└──────────────────────────────────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────────────────────────────────┐
│ WHAT'S INCLUDED │
├──────────────────────────────────────────────────────────────────────────────┤
│ │
│ 🎯 MCP Tools (9) │
│ ──────────────────────────────────────────────────────────────────────── │
│ ✓ get_completions - IntelliSense-style code completions │
│ ✓ get_hover - Type signatures and docstrings │
│ ✓ get_definition - Go-to-definition navigation │
│ ✓ get_references - Find all symbol references │
│ ✓ rename_symbol - Safe workspace-wide refactoring │
│ ✓ get_diagnostics - Type errors and warnings │
│ ✓ format_document - Code formatting │
│ ✓ apply_workspace_edit - Apply LSP edits │
│ ✓ health_check - Server status monitoring │
│ │
│ 📦 MCP Resources (3) │
│ ──────────────────────────────────────────────────────────────────────── │
│ ✓ workspace://files - List all Python files │
│ ✓ file://{path} - Read file contents │
│ ✓ workspace://structure - Complete directory tree │
│ │
└──────────────────────────────────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────────────────────────────────┐
│ NEXT STEPS │
├──────────────────────────────────────────────────────────────────────────────┤
│ │
│ 1️⃣ Read README.md for comprehensive documentation │
│ │
│ 2️⃣ Run demo.py to see the server in action │
│ │
│ 3️⃣ Connect to your favorite MCP client (Cursor, Claude, etc.) │
│ │
│ 4️⃣ Start coding with AI-powered Python intelligence! │
│ │
│ 5️⃣ (Optional) Deploy to Fly.io for remote access │
│ │
└──────────────────────────────────────────────────────────────────────────────┘
🎉 READY TO SUPERCHARGE YOUR AI 🎉
CODING ASSISTANT WITH PYTHON POWERS!
Built with ❤️ by Autonomous AI Agent | 2025-11-26
Status: ✅ PRODUCTION READY
╔══════════════════════════════════════════════════════════════════════════════╗
║ ║
║ GitHub: https://github.com/jarrodai/pylance-mcp-server ║
║ License: MIT ║
║ Support: GitHub Issues & Discussions ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
🤖 Optimize Your AI Assistant (Optional but Recommended):
To teach your AI how to best use Pylance MCP tools,
add this to your AI assistant's instructions/rules:
📄 File: C:\path\to\USAGE_GUIDE.md
How to add:
• GitHub Copilot: Copy to .github/copilot-instructions.md
• Cursor: Add to Settings → Rules for AI
• Cline/Continue: Include in system prompt
• Claude Desktop: Mention in conversation
• Windsurf: Add to workspace instructions
What it does
**Partially true, but there's a crucial difference:**
**What I can do without Pylance MCP:**
- ✅ Read Python code and understand it
- ✅ Suggest type hints based on code analysis
- ✅ Write new Python code with proper types
- ✅ Explain type errors I can see in the code
- ✅ Refactor code (but I have to read everything manually)
**What Pylance MCP gives me that I DON'T have:**
- ❌ **Real-time type checking** - I can't run Pyright to verify types are actually correct
- ❌ **Precise go-to-definition** - I can guess, but Pylance knows exactly where `User` is defined across 50 files
- ❌ **Find all references** - I can search, but can't guarantee I found every usage
- ❌ **Safe refactoring** - I can't guarantee my find-replace won't break something
- ❌ **IntelliSense completions** - I can suggest, but Pylance knows what's actually available in scope
- ❌ **Project-wide consistency** - I analyze file-by-file; Pylance sees the entire workspace graph
- ❌ **Virtual environment awareness** - I don't know which packages are installed
**Real-world example:**
**Without Pylance MCP:**
User: "Rename the User class to UserAccount everywhere"
Me: "Let me search for 'User'... I found it in 12 files. I'll replace all occurrences..."
Accidentally renames:
- UserModel → UserAccountModel ✅ Good
- User variable → UserAccount ❌ Broke local variable
- "User" in string → "UserAccount" ❌ Broke database query
- Used in comment → UserAccount ❌ Harmless but weird
**With Pylance MCP:**
User: "Rename the User class to UserAccount everywhere"
Me: "Using rename_symbol tool..." Pylance does AST-aware rename
- UserModel class → UserAccountModel ✅
- All type hints → UserAccount ✅
- All imports → UserAccount ✅
- Skips strings ✅
- Skips comments ✅
- Skips unrelated 'user' variables ✅
- Updates 47 locations perfectly ✅
**The value proposition:**
🎯 **Accuracy** - Pylance uses Microsoft's production language server (same one in VS Code)
🎯 **Speed** - I don't have to read entire codebases to find references
🎯 **Safety** - AST-aware refactoring vs. text-based find-replace
🎯 **Completeness** - Guaranteed to find ALL references, not just what I can grep
🎯 **Type verification** - Can actually run Pyright to prove types are correct
**So yes, I'm pretty good at Python already, but Pylance MCP makes me professional-grade.** It's like the difference between a surgeon with sharp eyes vs. a surgeon with an MRI machine. Both can operate, but one has way better information.
**Your customers are paying for:**
- Production-quality type checking (not AI guessing)
- Safe refactoring across massive codebases
- Tools that VS Code uses internally (proven at scale)
- Guaranteed accuracy that AI inference can't match
------------------------------------------
They **don't call it directly**. The AI assistant (Claude, Cursor, GitHub Copilot, etc.) calls it automatically when you chat with them. Here's how it works:
**Current User Experience:**
User: "Rename the User class to UserAccount everywhere"
[Behind the scenes:]
- AI (Claude/Cursor) sees the user's request
- AI discovers it has a "rename_symbol" tool available via MCP
- AI decides to use that tool
- AI calls: rename_symbol(file_path="src/models.py", line=5, character=6, new_name="UserAccount")
- Pylance MCP server executes the rename
- Returns result: "Renamed in 47 locations across 12 files"
- AI tells user: "✅ Done! Renamed User → UserAccount in 47 locations"
User just sees the result - they don't know MCP was involved.
**It's completely transparent to the user.** They just chat naturally:
User: "Add type hints to the calculate_total function" AI: [Internally uses get_hover, get_definition, type_check tools] AI: "Added type hints. Function signature is now: def calculate_total(items: List[Item], tax_rate: float) -> Decimal"
User: "Find everywhere OrderStatus is used" AI: [Calls get_references tool] AI: "OrderStatus is used in 23 locations: - src/models.py (definition) - src/api.py (5 usages) - src/utils.py (2 usages) ..."
User: "Are there any type errors in this file?" AI: [Calls type_check tool] AI: "Found 3 type errors: Line 45: Argument type mismatch Line 67: Missing return type Line 89: Undefined variable 'usr'"
**The MCP Protocol handles everything:**
1. **Discovery** - AI asks: "What tools do you have?"
- MCP Server responds: "I have rename_symbol, type_check, get_hover..."
2. **Tool Call** - AI decides: "User wants to rename, I'll use rename_symbol"
- AI sends: `{"tool": "rename_symbol", "params": {...}}`
3. **Execution** - MCP server runs Pylance
- Returns: `{"success": true, "locations_updated": 47}`
4. **Response** - AI formats result for user
- User sees: "✅ Renamed successfully!"
**Your customers never see the MCP layer.** They just have AI assistants that are mysteriously really good at Python refactoring because Pylance is working behind the scenes.
**Setup is literally:**
```bash
python install.py
# Restart editor
# Done - AI now has Pylance powers
The beauty of MCP is that it's invisible infrastructure. Users just chat, AI uses the tools automatically.