From qe-framework
Guides users through discovering, installing, and configuring MCP servers to integrate Claude Code with external services like Google Drive, Slack, GitHub, and databases.
How this skill is triggered — by the user, by Claude, or both
Slash command
/qe-framework:Qmcp-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill is a **setup and configuration guide only**. It does NOT execute MCP operations.
This skill is a setup and configuration guide only. It does NOT execute MCP operations.
| Request | Correct action |
|---|---|
| "Set up MCP server", "connect Google Drive" | This skill — guide setup steps |
| "Get files from Google Drive", "Send Slack messages" | NOT this skill — use connected MCP tools directly |
Before guiding setup, check if the requested MCP server is already connected:
claude mcp list 2>/dev/null | grep -i {service-name}
If connected: "Already connected. Use MCP tools directly." — exit skill. If NOT connected: proceed with setup guide.
Guides users through discovering, installing, and configuring MCP servers to connect Claude Code with external services.
Ask the user which external service they want to connect. Common MCP servers:
| Service | Recommended Package | Transport |
|---|---|---|
| Google Drive | @piotr-agier/google-drive-mcp | stdio |
| Google Workspace | google_workspace_mcp (Python) | stdio |
| GitHub | @modelcontextprotocol/server-github | stdio |
| Slack | @anthropics/mcp-server-slack | stdio |
| PostgreSQL | @modelcontextprotocol/server-postgres | stdio |
| Filesystem | @modelcontextprotocol/server-filesystem | stdio |
| Fetch (HTTP) | @modelcontextprotocol/server-fetch | stdio |
| Memory | @modelcontextprotocol/server-memory | stdio |
| Brave Search | @modelcontextprotocol/server-brave-search | stdio |
| Puppeteer | @modelcontextprotocol/server-puppeteer | stdio |
| Redis | @modelcontextprotocol/server-redis | stdio |
| SQLite | @modelcontextprotocol/server-sqlite | stdio |
| Sentry | @modelcontextprotocol/server-sentry | stdio |
If the service is not listed, search npm/PyPI/GitHub for mcp-server-{service} or {service}-mcp.
node --version # Requires Node.js 18+
python3 --version # Requires Python 3.10+
pip install uv # Recommended package manager
# npm packages
claude mcp add <server-name> -- npx <package-name>
# npm packages with env vars
claude mcp add <server-name> -e KEY=value -- npx <package-name>
# Python packages (uvx)
claude mcp add <server-name> -- uvx <package-name>
# Local scripts
claude mcp add <server-name> -- node /path/to/server.js
Edit ~/.claude.json or project .claude.json:
{
"mcpServers": {
"server-name": {
"command": "npx",
"args": ["<package-name>"],
"env": {
"API_KEY": "your-key"
}
}
}
}
claude mcp list # List configured servers
claude mcp get <name> # Check specific server config
Start a new Claude Code session and verify the MCP tools are available.
See references/service-setup-guides.md for detailed setup instructions for Google Drive, GitHub, Slack, PostgreSQL, and Filesystem.
These MCPs have dedicated setup skills in the framework. Use the dedicated skill for detailed guidance, or set up quickly from here.
Run this to check all framework MCP connections at once:
echo "=== QE Framework MCP Status ==="
echo -n "Chrome: "; claude mcp list 2>/dev/null | grep -qi chrome && echo "CONNECTED" || echo "NOT CONNECTED → /Qchrome"
echo -n "Stitch: "; claude mcp list 2>/dev/null | grep -qi stitch && echo "CONNECTED" || echo "NOT CONNECTED → /Qstitch-cli"
echo -n "Agentation: "; claude mcp list 2>/dev/null | grep -qi agentation && echo "CONNECTED" || echo "NOT CONNECTED → /Qagentation"
| MCP | Purpose | Setup Skill | Quick Add |
|---|---|---|---|
| Claude-in-Chrome | Browser automation (navigate, click, read, GIF) | /Qchrome | claude mcp add claude-in-chrome -- npx @anthropic/claude-in-chrome-mcp |
| Google Stitch | AI UI design → HTML/CSS | /Qstitch-cli | claude mcp add stitch -- npx @_davideast/stitch-mcp proxy |
| Agentation | Visual UI feedback for agents | /Qagentation | claude mcp add agentation -- npx agentation mcp |
For services not in this catalog (Google Drive, Slack, GitHub, etc.), see the general setup guide below.
| Command | Description |
|---|---|
claude mcp add <name> -- <command> | Add a new MCP server |
claude mcp remove <name> | Remove an MCP server |
claude mcp list | List all configured servers |
claude mcp get <name> | Show server details |
claude mcp add <name> -s project | Add to project scope only |
claude mcp add <name> -s user | Add to user scope (default) |
When using Agent Teams (--agents flag), each teammate can have its own MCP server configuration.
In the --agents JSON, use the mcpServers field:
[
{
"name": "researcher",
"mcpServers": [
{ "name": "brave-search", "command": "npx", "args": ["-y", "@anthropic-ai/mcp-brave-search"] }
]
},
{
"name": "coder",
"mcpServers": [
{ "name": "filesystem", "command": "npx", "args": ["-y", "@anthropic-ai/mcp-filesystem", "/src"] }
]
}
]
| Pattern | Use Case | Setup |
|---|---|---|
| Shared | All teammates need the same tool | Configure in project .mcp.json |
| Dedicated | Only one teammate needs it | Use mcpServers in agent definition |
| Mixed | Some shared, some dedicated | Combine both approaches |
.mcp.json servers unless overridden| Scope | Config File | Use Case |
|---|---|---|
user | ~/.claude.json | Personal tools (default) |
project | .claude.json in project root | Team-shared tools |
| Issue | Solution |
|---|---|
| Server not starting | Check node --version >= 18, verify package name |
| Auth errors | Verify API keys/tokens in env vars |
| Tools not showing | Restart Claude Code session after adding MCP |
| Timeout | Check network, increase timeout in config |
| Permission denied | Verify OAuth scopes, re-authenticate |
Use this section when building MCP servers from scratch. This is a development guide only — it does NOT auto-generate server code.
| Request | Correct action |
|---|---|
| "Show me how to build MCP servers", "MCP development guide" | This section — guide development process |
| "Write MCP server code", "Build a server" | NOT this section — use standard code implementation |
Phase 1: Research & Planning
https://modelcontextprotocol.io/sitemap.xmlPhase 2: Implementation
outputSchema + structuredContentPhase 3: Review & Test
npx @modelcontextprotocol/inspectorPhase 4: Evaluations
Pre-configured MCP server sets are available in presets/. Offer these to the user before building from scratch:
| Preset | File | Use Case |
|---|---|---|
| Recommended | presets/recommended.json | General-purpose (filesystem, git, fetch, memory, sequential-thinking) |
| Frontend | presets/frontend.json | Frontend development (browser, puppeteer, filesystem, git) |
| Full-stack | presets/fullstack.json | Full-stack development (filesystem, git, postgres, redis, fetch, docker) |
Usage: Copy the selected preset's mcpServers block into the project's .claude.json or MCP config file. Replace ${PROJECT_ROOT} and other environment variables with actual values.
https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.mdhttps://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.mdnpx claudepluginhub inho-team/qe-framework --plugin qe-frameworkCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.