Project Opener MCP Server

Created By
jlmelisa year ago
MCP server for easily opening code3 projects in either VS Code or Visual Studio
Overview

what is Project Opener MCP Server?

Project Opener MCP Server is a tool designed to facilitate the opening of code3 projects in popular code editors like VS Code and Visual Studio.

how to use Project Opener MCP Server?

To use the Project Opener MCP Server, you need to install Node.js, clone the repository, install dependencies, and configure it within Claude Desktop by adding it as an MCP server.

key features of Project Opener MCP Server?

  • Easily opens projects in the default code editor.
  • Retrieves project information based on the specified path.
  • Integrates seamlessly with Claude Desktop.

use cases of Project Opener MCP Server?

  1. Opening code projects quickly in your preferred editor.
  2. Accessing project details without manually navigating through files.
  3. Streamlining the workflow for developers using Claude Desktop.

FAQ from Project Opener MCP Server?

  • What is required to run the Project Opener MCP Server?

You need Node.js (v18.x or later) and the Filesystem MCP Server.

  • Can I use this server with any code editor?

It is designed to work with VS Code and Visual Studio, but can be adapted for others.

  • Is there a license for this project?

Yes, it is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jlmelis
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago