MCP

LSP is great for IDEs — and that’s the problem The Language Server Protocol (LSP) was designed to let editors provide interactive editing features: autocomplete, diagnostics, go-to-definition, etc. That design assumes an IDE-like client that: Keeps files open in memory (buffers) Streams every edit to the server in real time Maintains a long-lived session with capability negotiation and message envelopes (JSON-RPC + headers) That’s a perfect fit for an editor. ...

A practical comparison of LLM workflows in a large C# codebase: plain text search vs Roslyn-powered MCP tools (symbols, types, references, callers) — and why autosync changes the ergonomics.

When you ask an AI coding agent to understand a C# solution, you quickly hit two problems: Text search is not semantic. Grep cannot reliably answer questions about symbols, types, overloads, or implementations. The agent burns context and time doing many small tool calls (search -> open file -> search again -> open file again). Glider MCP is my attempt to fix both. It is a Roslyn-powered Model Context Protocol (MCP) server that gives MCP clients (like Claude Code) compiler-grade understanding of your codebase: symbols, types, relationships, diagnostics, and safe refactors. ...

What is MCP? MCP is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications. Just as USB-C provides a standardized way to connect your devices to various peripherals and accessories, MCP provides a standardized way to connect AI models to different data sources and tools. Core Architecture MCP Server: The component that exposes resources, tools, and prompts to the AI assistant. Servers can provide access to databases, APIs, file systems, or other external services. ...