Bifrost - VSCode Dev Tools MCP Server
@biegehydra
VSCode Extension with an MCP server that exposes semantic tools like Find Usages and Rename to LLMs
概要
What is Bifrost - VSCode Dev Tools MCP Server?
This VS Code extension provides a Model Context Protocol (MCP) server that exposes VSCode’s development tools and language features to AI assistants. It enables advanced code navigation, analysis, and manipulation for developers using AI coding tools that support the MCP protocol.
How to use Bifrost - VSCode Dev Tools MCP Server?
Install the extension from the VS Code marketplace, then install language-specific extensions for your project. The server starts automatically on port 8008 (configurable via bifrost.config.json). Configure your MCP‑compatible AI assistant to connect to http://localhost:8008/sse for SSE and http://localhost:8008/message for messages. For multiple projects, create a bifrost.config.json per project with a unique port and path.
Key features of Bifrost - VSCode Dev Tools MCP Server
- Language Server Integration for any supported language
- Code navigation: references, definitions, implementations
- Symbol search across the entire workspace
- Code analysis: semantic tokens, document symbols, type info
- Smart selection using semantic selection ranges
- Code actions: refactoring suggestions and quick fixes
- HTTP/SSE MCP server for AI assistant integration
Use cases of Bifrost - VSCode Dev Tools MCP Server
- AI-assisted code navigation and reference discovery
- Automated refactoring and applying quick fixes
- Multi‑project development with isolated server endpoints
- Obtaining inline documentation and type information
FAQ from Bifrost - VSCode Dev Tools MCP Server
What languages are supported?
Any language that has a corresponding VS Code language extension installed.
What are the runtime requirements?
Visual Studio Code version 1.93.0 or higher, and appropriate language extensions for your project.
How do I configure multiple projects?
Create a bifrost.config.json in each project root with projectName, description, path, and a unique port (default 8008). Each project then gets its own SSE and message endpoints.
What transport protocol does the server use?
The server uses HTTP with Server‑Sent Events (SSE). The SSE endpoint is at /sse and the message endpoint at /message.
Is authentication or authorization required?
—
