QA / Testing Stack for VS Code
Configuration
{
"servers": {
"playwright-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@playwright/mcp"
]
},
"puppeteer-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-puppeteer"
]
},
"sentry-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"sentry-mcp"
],
"env": {
"SENTRY_AUTH_TOKEN": "YOUR_SENTRY_AUTH_TOKEN"
}
},
"github-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-github"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_GITHUB_PERSONAL_ACCESS_TOKEN"
}
},
"filesystem-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/path/to/allowed/directory"
]
}
}
}Where to save
Paste the config above into:
.vscode/settings.json → mcp sectionEnvironment Variables
Replace the YOUR_ placeholders with your actual values.
SENTRY_AUTH_TOKENrequiredSentry auth token
Used by: Sentry MCP
GITHUB_PERSONAL_ACCESS_TOKENrequiredGitHub personal access token
Used by: GitHub MCP
What’s in this stack
Automate browser interactions, take screenshots, fill forms, and test web applications using Microsoft Playwright from your AI editor.
The gold standard for browser automation. Write, run, and debug end-to-end tests with full page interaction from your AI assistant.
Automate browsers with Puppeteer. Navigate pages, take screenshots, fill forms, and generate PDFs from your AI editor.
A second browser automation engine for cross-tool coverage. Some legacy test suites depend on Puppeteer — having both avoids rewrites.
Query Sentry for error tracking, performance monitoring, and issue management directly from your AI editor.
Pull real production errors into your test planning. Write regression tests for the exact bugs your users are hitting.
Access the GitHub API to manage repositories, issues, pull requests, branches, and workflows directly from your AI editor.
Link test results to PRs, manage CI workflows, and ensure tests pass before merging. QA lives in the PR review cycle.
Read, write, search, and manage files on your local filesystem with secure directory-scoped access for your AI editor.
Read test fixtures, write test reports, and manage configuration files. QA workflows are file-heavy by nature.