
vscode-mcp-servers
by samelhousseini
SKILL.md
name: vscode-mcp-servers description: Configure and use MCP (Model Context Protocol) servers in VS Code. Use when setting up MCP servers, configuring mcp.json, using MCP tools in chat, managing server trust, or troubleshooting MCP connections.
MCP Servers in VS Code
Model Context Protocol (MCP) is an open standard that lets AI models use external tools and services through a unified interface. MCP servers provide tools for file operations, databases, APIs, and more.
Add MCP Servers
From GitHub MCP Server Registry
- Enable
chat.mcp.gallery.enabledsetting - Open Extensions view (
Ctrl+Shift+X) - Search
@mcpor runMCP: Browse Servers - Select Install (user profile) or Install in Workspace
Configuration Locations
| Scope | Location |
|---|---|
| Workspace | .vscode/mcp.json |
| User | Settings via MCP: Open User Configuration |
| Dev Container | devcontainer.json |
Configuration Format
Basic Structure
{
"servers": {
"server-name": {
// Server configuration
}
},
"inputs": [
// Optional input variables for sensitive data
]
}
Standard I/O (stdio) Servers
For locally-run servers communicating via stdin/stdout:
{
"servers": {
"my-server": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem"],
"env": {
"API_KEY": "${input:api-key}"
},
"envFile": "${workspaceFolder}/.env"
}
}
}
| Field | Required | Description |
|---|---|---|
type | Yes | "stdio" |
command | Yes | Executable command |
args | No | Command arguments array |
env | No | Environment variables |
envFile | No | Path to .env file |
HTTP/SSE Servers
For remote servers over HTTP:
{
"servers": {
"remote-server": {
"type": "http",
"url": "https://api.example.com/mcp",
"headers": {
"Authorization": "Bearer ${input:api-token}"
}
}
}
}
| Field | Required | Description |
|---|---|---|
type | Yes | "http" or "sse" |
url | Yes | Server URL |
headers | No | HTTP headers |
Unix sockets: unix:///path/to/server.sock
Windows pipes: pipe:///pipe/named-pipe
Input Variables
Securely store sensitive data:
{
"inputs": [
{
"type": "promptString",
"id": "api-key",
"description": "GitHub Personal Access Token",
"password": true
}
],
"servers": {
"github": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_TOKEN": "${input:api-key}"
}
}
}
}
Use MCP Tools in Chat
Automatic Invocation
- Open Chat view (
Ctrl+Alt+I) - Use tool picker to enable MCP tools (grouped by server)
- Ask naturally: "List my GitHub issues"
- Review and approve tool invocations when prompted
Explicit Tool Reference
Type # followed by tool name to reference directly.
In Custom Prompts/Agents
Reference MCP tools in frontmatter:
tools: ['github/*', 'filesystem/*']
Use <server>/* format to include all tools from a server.
MCP Resources
Access server-provided resources as context:
- In Chat view, select Add Context > MCP Resources
- Select resource type and provide parameters
- Resources returned by tools can be saved via Save or drag-and-drop
MCP Prompts
Invoke preconfigured prompts with slash commands:
/mcp.servername.promptname
Server Management
Commands
| Command | Action |
|---|---|
MCP: List Servers | View all servers with actions |
MCP: Browse Servers | Browse GitHub registry |
MCP: Reset Cached Tools | Clear tool cache |
MCP: Reset Trust | Reset server trust |
MCP: Open User Configuration | Edit user mcp.json |
MCP: Open Workspace Folder Configuration | Edit workspace mcp.json |
Auto-Start
Enable chat.mcp.autostart (experimental) to automatically restart servers on configuration changes.
Server Naming Conventions
- Use camelCase:
uiTesting,githubIntegration - No whitespace or special characters
- Unique names per server
- Descriptive names reflecting functionality
Development Mode
Enable debugging in server configuration:
{
"servers": {
"my-server": {
"type": "stdio",
"command": "node",
"args": ["server.js"],
"dev": {
"watch": "**/*.js",
"debug": true
}
}
}
}
Troubleshooting
| Issue | Solution |
|---|---|
| Server not starting | Check command/args, verify not using Docker -d flag |
| Error indicator in Chat | Select error → Show Output for logs |
| "Cannot have more than 128 tools" | Reduce enabled tools in picker or enable github.copilot.chat.virtualTools.threshold |
| Trust prompt not appearing | Starting from mcp.json bypasses trust prompt |
View Server Logs
MCP: List Servers→ Select server → Show Output- Or click error notification → Show Output
Security
- Only add servers from trusted sources
- Review configuration before starting
- Trust confirmation required on first start
- Use
MCP: Reset Trustto revoke trust
Settings Sync
Synchronize MCP servers across devices:
- Run
Settings Sync: Configure - Ensure MCP Servers is included
Example: GitHub MCP Server
{
"inputs": [
{
"type": "promptString",
"id": "github-token",
"description": "GitHub Personal Access Token",
"password": true
}
],
"servers": {
"github": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_TOKEN": "${input:github-token}"
}
}
}
}
Then in chat: "List my GitHub issues" or "Create a new issue in repo X"
スコア
総合スコア
リポジトリの品質指標に基づく評価
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新がある
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
レビュー
レビュー機能は近日公開予定です