Copilot New Mcp.prompt

---
description: Scaffold MCP server configuration for VS Code and GitHub Copilot agents
name: New MCP Setup
agent: Copilot Customization Builder
tools: ['search', 'edit/editFiles']
---

# New MCP Setup

Create or update MCP server configuration for this repository.

## Inputs

- MCP server name (stable kebab-case): `${input:mcpServerName}`
- Server transport (`stdio`, `http`, or `sse`): `${input:mcpTransport}`
- Server command or URL: `${input:mcpCommandOrUrl}`
- Scope (`vscode-workspace`, `vscode-user`, `github-copilot-agent`, or `plugin`): `${input:mcpScope}`
- Tools to expose (comma-separated, or `*`): `${input:mcpTools}`

## Requirements

1. Inspect existing MCP configuration before editing:
   - VS Code workspace: `.vscode/mcp.json`
   - VS Code user profile: use `MCP: Open User Configuration`
   - GitHub Copilot cloud agent: `mcp-servers` in `.github/agents/<agent>.agent.md`
   - Agent plugin: `.mcp.json` or `mcpServers` in `plugin.json`
2. Prefer an example file (`mcp.example.json`) unless the user explicitly asks to enable a live server.
3. Never hardcode secrets, tokens, passwords, or API keys.
   - Use VS Code input variables, environment files, or GitHub Copilot environment secrets/variables.
4. For local stdio servers, consider `sandboxEnabled: true` on macOS/Linux and restrict filesystem/network access.
5. Keep tool exposure narrow:
   - Use explicit tools such as `github/list_issues` where practical.
   - Use `<server>/*` only when the full server is intentionally needed.
6. Document how to start, trust, disable, and troubleshoot the MCP server.

## VS Code workspace example

Create or update `.vscode/mcp.json`: