This document describes the recommended Model Context Protocol (MCP) servers for enhancing the Agentic Development Framework.
MCPs extend Claude's capabilities by providing specialized tools and data sources. This framework is designed to work with several MCPs that significantly enhance autonomous development workflows.
These MCPs provide transformative capabilities for the framework:
Package: @modelcontextprotocol/server-github
Impact: Critical for PR/issue workflows
What it provides:
github_create_or_update_file- Programmatic file updatesgithub_create_issue- Automated issue creationgithub_create_pull_request- Enhanced PR creationgithub_get_file_contents- Direct file accessgithub_list_commits- Commit history accessgithub_search_code- Advanced code searchgithub_search_issues- Issue/PR search
Framework Skills Enhanced:
/create-pr- More robust PR creation with better error handling/review-pr- Fetch PR diffs and comments programmatically/bugfix- Search issues for similar bugs before implementing/explore- Search code across repositories
Installation:
npm install -g @modelcontextprotocol/server-githubConfiguration (in Claude Code settings):
{
"mcpServers": {
"github": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-github"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<your-token>"
}
}
}
}Usage in Skills:
When GitHub MCP is available, prefer its tools over gh CLI for:
- Fetching PR details and diffs
- Creating/updating issues programmatically
- Searching code and issues
- File operations in PRs
Package: @modelcontextprotocol/server-memory
Impact: Game-changing for multi-session development
What it provides:
create_entities- Store facts, patterns, conventionscreate_relations- Link related conceptssearch_nodes- Query stored knowledgeopen_nodes- Retrieve detailed informationadd_observations- Record insights
Framework Enhancements:
- Cross-session ADR awareness - Remember established patterns
- Project conventions - Store and recall user preferences
- Historical context - Remember why decisions were made
- Pattern recognition - Identify when similar code patterns recur
- User preferences - Remember commit message style, testing preferences
Installation:
npm install -g @modelcontextprotocol/server-memoryConfiguration:
{
"mcpServers": {
"memory": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}Usage Patterns:
// Store ADR summary when created
create_entities({
entities: [{
name: "ADR-017: Feature-Specific Custom Hooks",
entityType: "architectural_decision",
observations: [
"Custom hooks should be placed in feature directories",
"Colocation reduces import complexity",
"Established 2026-01-23"
]
}]
})
// Recall patterns before implementing similar features
search_nodes({
query: "custom hooks architecture pattern"
})Framework Integration Points:
/adrskill - Store ADR summaries in memory/heavy-task- Recall similar patterns before starting/medium-task- Remember component patterns/explore- Store findings for future reference- Orchestrator Agent - Leverage historical decision context
Package: @modelcontextprotocol/server-sequential-thinking
Impact: Enhanced reasoning and planning
What it provides:
- Structured thinking process
- Step-by-step reasoning
- Decision tree exploration
- Complex problem decomposition
Framework Enhancements:
- Orchestrator Agent - Better task decomposition
- Bugfix investigations - Systematic root cause analysis
- Architecture reviews - Trade-off analysis
- Planning phase - Complex feature breakdown
Installation:
npm install -g @modelcontextprotocol/server-sequential-thinkingConfiguration:
{
"mcpServers": {
"sequentialthinking": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-sequential-thinking"
]
}
}
}Usage in Skills:
/heavy-task- Planning complex features with multiple domains/bugfix- Root cause analysis with systematic elimination/refactor- Analyzing multiple refactoring approaches- Orchestrator planning - Breaking down complex tasks
Package: @modelcontextprotocol/server-brave-search
Impact: Better research and documentation discovery
What it provides:
brave_web_search- Privacy-respecting web searchbrave_local_search- Location-aware results- Developer-focused results
Framework Enhancements:
/researchskill - Better external information gathering- Library documentation discovery
- API documentation search
- Best practices research
- Technology comparison research
Installation:
npm install -g @modelcontextprotocol/server-brave-searchConfiguration:
{
"mcpServers": {
"brave-search": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-brave-search"
],
"env": {
"BRAVE_API_KEY": "<your-api-key>"
}
}
}
}Usage in Skills:
/research- Prefer Brave Search over WebSearch for developer topics- Technology evaluation
- Library comparison research
- API documentation lookup
- Install GitHub MCP
- Install Memory MCP
- Update
/create-prand/review-prto use GitHub MCP tools - Integrate memory persistence in ADR creation workflow
- Install Sequential Thinking MCP
- Install Brave Search MCP
- Update Orchestrator Agent to leverage sequential thinking
- Update
/researchskill to use Brave Search
- Identify additional MCP usage opportunities
- Fine-tune memory storage patterns
- Optimize MCP tool selection logic
- Document MCP-specific patterns
With GitHub MCP:
- Use
github_create_pull_requestfor more reliable PR creation - Better error handling and validation
- Automatic branch detection
- Link issues automatically
With GitHub MCP:
- Use
github_get_file_contentsto fetch PR files directly - Use GitHub API for more accurate diff retrieval
- Check PR CI status programmatically
- Fetch existing review comments
With Memory MCP:
- Store ADR summary in memory after creation
- Tag with decision type and domains affected
- Link related ADRs automatically
With Memory MCP:
- Recall similar task patterns before starting
- Remember user preferences for testing, commits, etc.
- Store successful orchestration patterns
With Sequential Thinking MCP:
- Enhanced task decomposition
- Better parallel vs sequential decision-making
- Improved trade-off analysis
With GitHub MCP:
- Search for similar issues before implementing fix
- Link fix to related issues automatically
With Sequential Thinking MCP:
- Systematic root cause elimination
- Evidence-based debugging
With Brave Search MCP:
- Privacy-respecting searches
- Developer-focused results
- Better API documentation discovery
Skills should detect MCP availability and adapt:
// Example pattern in skill documentation
**If GitHub MCP available**:
- Use `github_create_pull_request` for PR creation
- Otherwise: Fall back to `gh pr create` command
**If Memory MCP available**:
- Store ADR summary with `create_entities`
- Otherwise: Skip memory persistence (no error)- 40% faster PR workflows - Direct API access vs CLI parsing
- Cross-session continuity - Remember patterns and decisions
- Better code search - GitHub API search vs local grep
- Historical context - Why decisions were made, not just what
- Improved planning - Systematic problem decomposition
- Better research - Developer-focused search results
- Enhanced debugging - Structured root cause analysis
- Architectural insight - Trade-off analysis support
- Filesystem MCP - Advanced file operations
- Puppeteer MCP - Browser automation for E2E testing
- Slack/Discord MCP - Team notifications
- PostgreSQL/Database MCPs - Database operations
- Verify MCP server is installed:
npx -y @modelcontextprotocol/server-github --version - Check API keys are configured in Claude Code settings
- Restart Claude Code after configuration changes
- Check MCP server logs for errors
- MCPs add latency for network calls
- Memory MCP should be lightweight (local storage)
- GitHub MCP caches responses (check cache settings)
- Sequential Thinking MCP has minimal overhead
- Skills should gracefully degrade without MCPs
- Always provide CLI fallback paths
- Document MCP vs non-MCP behavior differences
- ADR-002: MCP Integration Strategy - Architectural decisions around MCP usage
- CLAUDE.md - Main framework documentation
- Skills Documentation - Individual skill implementations