MCP Server Extension

Created By
ranjanbinwania year ago
A basic MCP server for tool exposure using FastMCP and VS code extension distribution
Overview

What is MCP Server Extension?

MCP Server Extension is a simple Visual Studio Code extension that automatically starts an MCP server for GitHub Copilot tool discovery, enabling users to utilize built-in tools seamlessly.

How to use MCP Server Extension?

To use the MCP Server Extension, install it via the VS Code marketplace or build it from source, then restart VS Code to configure it automatically. You can then interact with GitHub Copilot using commands like adding numbers or getting weather forecasts.

Key features of MCP Server Extension?

  • Auto-starts MCP server upon loading the extension
  • Includes three built-in tools for GitHub Copilot: add_numbers, get_weather, and list_files
  • No configuration required for initial setup

Use cases of MCP Server Extension?

  1. Quickly adding numbers using the add_numbers tool.
  2. Simulating weather forecasts with the get_weather tool.
  3. Listing files in a directory using the list_files tool.

FAQ from MCP Server Extension?

  • What tools are included?

The extension includes tools for adding numbers, getting weather forecasts, and listing files.

  • Is there any configuration needed?

No configuration is required; the extension sets itself up automatically upon loading.

  • What are the requirements?

You need Python 3.x, VS Code 1.80.0+, and the GitHub Copilot extension.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ranjanbinwani
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Crevio

2 days 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