pzalutski-pixel/sharplens-mcp

v1.2.2 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 5mo MCP Developer Tools

✓ No known CVEs patched

✓ No known CVEs patched in this version

Topics

ai claude-code code-analysis c# .net mcp

+2 more

roslyn semantic-analysis

Affected surfaces

breaking_upgrade

Summary

AI summary

Agents must call sync_documents after edit/write operations.

Full changelog

sync_documents infrastructure tool - Synchronize file changes from disk into the loaded solution
- Faster than load_solution - only updates changed documents, doesn't re-parse projects
- Handles modified files, new files, and deleted files
- Supports specific file list or sync all documents
Agent Responsibility documentation in README explaining sync workflow

Agents are now responsible for calling sync_documents after using Edit/Write tools
SharpLensMcp refactoring tools continue to auto-update (no sync needed)

dotnet tool update -g SharpLensMcp

Agents are now required to invoke `sync_documents` after using Edit/Write tools; previous behavior where auto-update handled synchronization is removed.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track pzalutski-pixel/sharplens-mcp

Get notified when new releases ship.

About pzalutski-pixel/sharplens-mcp

58 semantic C#/.NET analysis tools via Roslyn. Navigation, refactoring, find usages, and code intelligence for AI agents.

v1.5.3 `health_check` response now uses `{success, data, meta}` envelope; callers must read `data.status` instead of `status`.