MCP Packs - Curated Server Collections
Curated sets of MCP servers organized by role and use case.
MCP Packs
MCP Packs are curated sets of MCP servers organized by role and use case. Pick a persona to get a ready-to-install set of servers for your workflow.
Always default-deny new tools, pin versions, and use per-server tokens. Review the Security Pack for hardening guidance.
Available Packs
Developer
Code, issues, tests, API calls, docs search.
DevOps/SRE
Infrastructure, monitoring, deployments.
Data Analyst
Data analysis, visualization, SQL queries.
Designer
UI/UX design tools, prototyping, assets.
Product Manager
Roadmaps, specs, user research.
Marketing
Analytics, campaigns, content.
Content Writer
Writing, editing, publishing.
Sales/RevOps
CRM, pipelines, forecasting.
Support/Success
Tickets, knowledge base, customer data.
Security
Scanning, compliance, hardening.
ML/AI Engineer
Models, training, experiments.
QA Engineer
Testing, automation, bug tracking.
Research
Papers, citations, knowledge management.
Using Packs
Each pack page includes:
- Recommended MCP servers for that role
- Example configuration snippet
- Common workflows and use cases
- Security considerations
Example: Adding a Pack
{
"mcpServers": {
// Developer Pack servers
"github": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-github"] },
"filesystem": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-filesystem", "."] }
}
}Security Best Practices
When using packs:
- Default-deny new tools - Review tools before enabling
- Pin versions - Use specific npm versions, not latest
- Per-server tokens - Don't share credentials across servers
- Audit regularly - Review enabled tools periodically