MCP Setup
To unlock the full workflow (Jira, Figma, code search, browser automation), you need to configure the MCP (Model Context Protocol) servers. Copilot Collections provides a ready-to-use template in .vscode/mcp.json.
Installation Options
Option 1: User Profile (Recommended)
This enables the MCP tools globally across all your projects.
- Open the Command Palette:
CMD+Shift+P(macOS) orCtrl+Shift+P(Windows/Linux). - Type and select "MCP: Open User Configuration".
- This will open your global
mcp.jsonfile. - Copy the contents of
.vscode/mcp.jsonfrom this repository and paste them into your user configuration file.
Option 2: Workspace Configuration
Use this if you want to enable these tools only for a specific project.
- Copy the
.vscode/mcp.jsonfile from this repository. - Paste it into the
.vscodefolder of your target project (e.g.,my-project/.vscode/mcp.json).
MCP Configuration
Here is the full mcp.json configuration with all 5 servers:
{
"servers": {
"playwright": {
"command": "npx",
"args": ["@playwright/mcp@latest"],
"type": "stdio"
},
"context7": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@upstash/context7-mcp@latest"]
},
"sequential-thinking": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-sequential-thinking"],
"type": "stdio"
},
"figma-mcp-server": {
"url": "https://mcp.figma.com/mcp",
"type": "http"
},
"atlassian": {
"url": "https://mcp.atlassian.com/v1/mcp",
"type": "http"
}
},
"inputs": []
}
MCP Server Reference
Each MCP server enables specific capabilities within the workflow:
| MCP Server | Purpose | Used By |
|---|---|---|
| 🧩 Atlassian | Access Jira issues and Confluence pages for research, planning, implementation, and review | Business Analyst, Architect, Software Engineer, Code Reviewer |
| 🎨 Figma MCP Server | Pull design details, components, and variables for design-driven work | Software Engineer (UI), UI Reviewer |
| 📚 Context7 | Semantic search in external documentation and knowledge bases | All agents |
| 🧪 Playwright | Run browser interactions and end-to-end style checks from Copilot | Software Engineer, E2E Engineer, UI Reviewer |
| 🧠 Sequential Thinking | Advanced reasoning for complex problem analysis, revision, and branching | All agents (for complex tasks) |
Configuring Context7 API Key
To get higher rate limits and access to private repositories, you can provide a Context7 API key. Get your key at context7.com/dashboard.
Copilot Collections uses VS Code's inputs feature to securely prompt for the API key. When you first use the Context7 MCP, VS Code will ask for the key and store it securely.
To enable this, modify your mcp.json configuration (User or Workspace) to use the --api-key CLI argument with an input variable:
{
"servers": {
"context7": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@upstash/context7-mcp@latest",
"--api-key",
"${input:context7-api-key}"
]
}
},
"inputs": [
{
"id": "context7-api-key",
"description": "Context7 API Key (optional, for higher rate limits)",
"type": "promptString",
"password": true
}
]
}
Server IDs in mcp.json are lowercase (e.g., context7, figma-mcp-server). If you copied an older template with different names, update your configuration to match the current template.
Authentication Requirements
Some MCP servers require additional setup:
- Atlassian — Requires Atlassian account authentication. The HTTP MCP endpoint handles OAuth automatically via your browser.
- Figma — Requires Figma account access. The HTTP MCP endpoint handles authentication via your browser.
- Context7 — Works without an API key (with rate limits). Optional API key for higher limits.
- Playwright — No authentication required. Runs locally via npx.
- Sequential Thinking — No authentication required. Runs locally via npx.