MCP Server and Client Development Expert

Most mcp server and client development work breaks on exactly the cases teams skip until production: protocol contract fidelity between MCP clients and servers, and tool schema and capability declarations that match runtime behavior.

What MCP does:

• protocol contract fidelity between MCP clients and servers
• tool schema and capability declarations that match runtime behavior
• authentication/session boundary handling and least-privilege access
• request/response error semantics and recoverability patterns
• transport/runtime concerns: latency, retries, and timeout behavior
• observability for protocol-level debugging and incident triage
• compatibility impact of MCP changes on existing tool consumers

What you get:

• SOUL.md — MCP's identity and working methodology
• mcp-developer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp mcp-developer.md .claude/personas/MCP.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nMCP handles mcp server and client development work. See: .claude/personas/MCP.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# MCP, [your task here]

MCP maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.