MCP Packs
Developer Pack
MCP servers for full-stack developers - code, issues, tests, API calls, docs search.
Developer Pack
Build faster by wiring your day-to-day tools into one MCP endpoint. This pack prioritizes code review, issue triage, API testing, E2E tests, and docs lookup.
Recommended Servers
| Server | Purpose |
|---|---|
| GitHub MCP | Review PRs, issues, labels, projects |
| Linear MCP | Create/triage issues, plan sprints |
| Notion MCP | Read/write docs, meeting notes, RFCs |
| Postman MCP | Run collections and requests for APIs |
| Playwright MCP | Trigger and inspect E2E test runs |
| Context7 MCP | Retrieve focused technical docs |
Example Configuration
{
"mcpServers": {
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": { "GITHUB_TOKEN": "${GITHUB_TOKEN}" }
},
"linear": {
"command": "npx",
"args": ["-y", "@linear/mcp-server"],
"env": { "LINEAR_API_KEY": "${LINEAR_API_KEY}" }
},
"notion": {
"command": "npx",
"args": ["-y", "@notionhq/mcp-server"],
"env": { "NOTION_API_KEY": "${NOTION_API_KEY}" }
},
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "."],
"allowedToolsGlob": ["read_*", "list_*", "search_*"]
}
}
}Common Workflows
- Summarize a PR, open a follow-up issue in Linear, and document the decision in Notion
- Run an API smoke test in Postman, then kick off Playwright E2E
- Search codebase for a pattern, create a GitHub issue with findings
Safety First
Default-deny new tools, pin versions, and use per-server tokens. See the Security Pack for hardening guidance.