Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
VS Code MCP server for semantic code tools
Bifrost is a VS Code extension that starts an MCP server and publishes editor capabilities to AI assistants. Those tools include references, definitions, rename, completions, semantic tokens, code actions, and workspace symbol search. It is meant to sit between your editor and an MCP client so the agent can use the language server through VS Code.

Builders who want their agent to navigate, inspect, and rename code through VS Code language features.
You can let your assistant use real editor intelligence for navigation, refactors, and code search.
What it does
MCP server in VS Code
Starts an HTTP/SSE MCP server from the extension and exposes editor capabilities on localhost.
Semantic navigation tools
Provides find usages, go to definition, implementations, declarations, type definitions, and workspace symbols.
Refactor and code-action access
Surfaces rename locations, rename operations, code actions, and selection ranges for safer edits.
Language server queries
Returns hover info, completions, signature help, document symbols, highlights, and semantic tokens.
Multi-project endpoints
Reads `bifrost.config.json` so each project can use its own port and SSE path.
Agent rules examples
Includes sample Cursor and MDC rule files to help assistants use the tools well.
README
Bifrost - VSCode Dev Tools MCP Server
This VS Code extension provides a Model Context Protocol (MCP) server that exposes VSCode's powerful development tools and language features to AI tools. It enables advanced code navigation, analysis, and manipulation capabilities when using AI coding assistants that support the MCP protocol.

Table of Contents
- Features
- Installation/Usage
- Multi-Project Support
- Available Tools
- Available Commands
- Troubleshooting
- Contributing
- Debugging
- License
Features
- Language Server Integration: Access VSCode's language server capabilities for any supported language
- Code Navigation: Find references, definitions, implementations, and more
- Symbol Search: Search for symbols across your workspace
- Code Analysis: Get semantic tokens, document symbols, and type information
- Smart Selection: Use semantic selection ranges for intelligent code selection
- Code Actions: Access refactoring suggestions and quick fixes
- HTTP/SSE Server: Exposes language features over an MCP-compatible HTTP server
- AI Assistant Integration: Ready to work with AI assistants that support the MCP protocol
Usage
Installation
- Install the extension from the VS Code marketplace
- Install any language-specific extensions you need for your development
- Open your project in VS Code
Configuration
The extension will automatically start an MCP server when activated. To configure an AI assistant to use this server:
- The server runs on port 8008 by default (configurable with
bifrost.config.json) - Configure your MCP-compatible AI assistant to connect to:
- SSE endpoint:
http://localhost:8008/sse - Message endpoint:
http://localhost:8008/message
- SSE endpoint:
LLM Rules
I have also provided sample rules that can be used in .cursorrules files for better results.
Cline Installation
- Step 1. Install Supergateway
- Step 2. Add config to cline
- Step 3. It will show up red but seems to work fine
Windows Config
{
"mcpServers": {
"Bifrost": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"supergateway",
"--sse",
"http://localhost:8008/sse"
],
"disabled": false,
"autoApprove": [],
"timeout": 600
}
}
}
Mac/Linux Config
{
"mcpServers": {
"Bifrost": {
"command": "npx",
"args": [
"-y",
"supergateway",
"--sse",
"http://localhost:8008/sse"
],
"disabled": false,
"autoApprove": [],
"timeout": 600
}
}
}
Roo Code Installation
- Step 1: Add the SSE config to your global or project-based MCP configuration
{
"mcpServers": {
"Bifrost": {
"url": "http://localhost:8008/sse"
}
}
}
Follow this video to install and use with cursor
FOR NEW VERSIONS OF CURSOR, USE THIS CODE
{
"mcpServers": {
"Bifrost": {
"url": "http://localhost:8008/sse"
}
}
}
Multiple Project Support
When working with multiple projects, each project can have its own dedicated MCP server endpoint and port. This is useful when you have multiple VS Code windows open or are working with multiple projects that need language server capabilities.
Project Configuration
Create a bifrost.config.json file in your project root:
{
"projectName": "MyProject",
"description": "Description of your project",
"path": "/my-project",
"port": 5642
}
The server will use this configuration to:
- Create project-specific endpoints (e.g.,
http://localhost:5642/my-project/sse) - Provide project information to AI assistants
- Use a dedicated port for each project
- Isolate project services from other running instances
Example Configurations
- Backend API Project:
{
"projectName": "BackendAPI",
"description": "Node.js REST API with TypeScript",
"path": "/backend-api",
"port": 5643
}
- Frontend Web App:
{
"projectName": "FrontendApp",
"description": "React frontend application",
"path": "/frontend-app",
"port": 5644
}
Port Configuration
Each project should specify its own unique port to avoid conflicts when multiple VS Code instances are running:
- The
portfield inbifrost.config.jsondetermines which port the server will use - If no port is specified, it defaults to 8008 for backwards compatibility
- Choose different ports for different projects to ensure they can run simultaneously
- The server will fail to start if the configured port is already in use, requiring you to either:
- Free up the port
- Change the port in the config
- Close the other VS Code instance using that port
Connecting to Project-Specific Endpoints
Update your AI assistant configuration to use the project-specific endpoint and port:
{
"mcpServers": {
"BackendAPI": {
"url": "http://localhost:5643/backend-api/sse"
},
"FrontendApp": {
"url": "http://localhost:5644/frontend-app/sse"
}
}
}
Backwards Compatibility
If no bifrost.config.json is present, the server will use the default configuration:
- Port: 8008
- SSE endpoint:
http://localhost:8008/sse - Message endpoint:
http://localhost:8008/message
This maintains compatibility with existing configurations and tools.
Available Tools
The extension provides access to many VSCode language features including:
- find_usages: Locate all symbol references.
- go_to_definition: Jump to symbol definitions instantly.
- find_implementations: Discover implementations of interfaces/abstract methods.
- get_hover_info: Get rich symbol docs on hover.
- get_document_symbols: Outline all symbols in a file.
- get_completions: Context-aware auto-completions.
- get_signature_help: Function parameter hints and overloads.
- get_rename_locations: Safely get location of places to perform a rename across the project.
- rename: Perform rename on a symbol
- get_code_actions: Quick fixes, refactors, and improvements.
- get_semantic_tokens: Enhanced highlighting data.
- get_call_hierarchy: See incoming/outgoing call relationships.
- get_type_hierarchy: Visualize class and interface inheritance.
- get_code_lens: Inline insights (references, tests, etc.).
- get_selection_range: Smart selection expansion for code blocks.
- get_type_definition: Jump to underlying type definitions.
- get_declaration: Navigate to symbol declarations.
- get_document_highlights: Highlight all occurrences of a symbol.
- get_workspace_symbols: Search symbols across your entire workspace.
Requirements
- Visual Studio Code version 1.93.0 or higher
- Appropriate language extensions for the languages you want to work with (e.g., C# extension for C# files)
Available Commands
Bifrost MCP: Start Server- Manually start the MCP server on port 8008Bifrost MCP: Start Server on port- Manually start the MCP server on specified portBifrost MCP: Stop Server- Stop the running MCP serverBifrost MCP: Open Debug Panel- Open the debug panel to test available tools

Star History
Example Tool Usage
Find References
{
"name": "find_usages",
"arguments": {
"textDocument": {
"uri": "file:///path/to/your/file"
},
"position": {
"line": 10,
"character": 15
},
"context": {
"includeDeclaration": true
}
}
}
Workspace Symbol Search
{
"name": "get_workspace_symbols",
"arguments": {
"query": "MyClass"
}
}
Troubleshooting
If you encounter issues:
- Ensure you have the appropriate language extensions installed for your project
- Check that your project has loaded correctly in VSCode
- Verify that port 8008 is available on your system
- Check the VSCode output panel for any error messages
Contributing
Here are Vscodes commands if you want to add additional functionality go ahead. I think we still need rename and a few others. Please feel free to submit issues or pull requests to the GitHub repository.
vsce package
Debugging
Use the MCP: Open Debug Panel command

License
This extension is licensed under the APGL-3.0 License.
Files in the repo
- .vscode
- src
- .gitignore
- .vscode-test.mjs
- .vscodeignore
- CHANGELOG.md
- eslint.config.mjs
- example.bifrost.config.json
- example.mdc
- ExampleCursorRules.md
- icon.png
- icon.txt
- LICENSE
- package-lock.json
- package.json
- placeholder.txt
- README.md
- tsconfig.json
- vsc-extension-quickstart.md
- webpack.config.js
Discussion (0)
Ask about usage, or say what you built with itSign in to join the discussion.
No comments yet. Be the first to say what this is good for.
More connectors
High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 158 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.

Universal provider proxy for OpenAI Codex & Claude Code — use any LLM (Claude, Gemini, Grok, DeepSeek, Ollama…) with Codex CLI, App, SDK, and Claude Code
Git-native persistent memory for AI coding agents. Implements Google OKF v0.2 with sub-300µs in-memory BM25 search, embedded MCP server, and progressive disclosure. Slashes token bloat by 80% with zero external databases or dependencies. Built in pure Go.
Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked context reductions on reviews and large-repo workflows.
Stop your AI from making things up — it proposes, deterministic tools decide, every claim checked against ground truth with evidence. Grounded facts and context survive resets. Reverse engineering is the proving ground. MCP server + CLI.