This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
This is a curated registry of persona-based MCP (Model Context Protocol) server configurations. Each persona bundles together MCP servers and tools optimized for specific professional roles or use cases, similar to installable packages or specialized Claude subagents.
awesome-mcp-personas/
├── personas/ # All persona definitions
│ ├── [persona-name]/ # Individual persona directory
│ │ ├── mcp.json # MCP server configuration (required)
│ │ ├── README.md # Persona documentation (required)
│ │ ├── tools.md # Tool reference guide (required)
│ │ └── examples/ # Usage examples (optional)
├── README.md # Main registry listing
├── CONTRIBUTING.md # Contribution guidelines
└── LICENSE # Repository license
Every persona MUST include:
- mcp.json - Valid MCP server configuration following the Model Context Protocol specification
- README.md - Clear documentation explaining the persona's purpose, target audience, and key capabilities
- tools.md - Comprehensive list of available tools and their usage
{
"mcpServers": {
"server-name": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-package"],
"config": {
// Server-specific configuration
}
}
}
}- Create directory:
personas/[persona-name]/ - Add required files: mcp.json, README.md, tools.md
- Validate JSON configuration syntax
- Update main README.md with the new persona entry in the appropriate category
- Ensure the persona listing includes: name, description, MCP servers list, key features, and best use cases
When reviewing or adding personas, verify:
- JSON syntax is valid in mcp.json
- All referenced MCP servers exist and are publicly available
- Configuration keys match the server's expected schema
- No duplicate server definitions within a persona
- Server combinations make logical sense for the stated use case
Personas should be organized into these primary categories:
- Software Engineering (language-specific and framework-specific dev tools)
- Data Science & Analytics (data processing, ML, visualization)
- DevOps & Infrastructure (cloud, containers, monitoring)
- Content & Documentation (writing, editing, publishing)
- Security & Compliance (scanning, auditing, hardening)
- Research & Analysis (information gathering, processing)
When updating the main README:
- Maintain alphabetical order within categories
- Use consistent emoji indicators for visual recognition
- Include brief (1-2 line) descriptions
- List 3-5 key MCP servers for each persona
- Specify primary use cases
- Specificity: Target a clear, well-defined use case or professional role
- Completeness: Include all essential tools for the stated purpose
- Compatibility: Ensure MCP servers work well together without conflicts
- Documentation: Provide clear, actionable documentation with examples
- Testability: Configuration should be directly usable without modifications
Each persona README should include:
- Purpose statement
- Target audience
- Prerequisites or requirements
- Installation instructions specific to the persona
- List of included MCP servers with brief descriptions
- Common workflows or use cases
- Troubleshooting section for known issues
- Check for valid JSON syntax
- Verify required "mcpServers" top-level key
- Ensure each server has "command" and "args" properties
- Validate optional "config" objects match server requirements
- Check for proper heading hierarchy
- Verify all links are valid (internal and external)
- Ensure code blocks have appropriate language tags
- Validate that required sections are present