Split azure-m365-mcp into two pure-play servers

Decision

Split single 913-tool azure-m365-mcp server into azure-mcp (561 tools, Azure infra) + m365-mcp (356 tools, Graph API)

Rationale

913 tools = ~220K tokens JSON, exceeding Claude 200K context window. Every interaction returned Prompt is too big. Splitting eliminates context pressure while maintaining complete coverage. Each server stays within safe tool budget.

Alternatives Rejected

Rejected: (1) Tool dispatcher/router layer adding complexity and single point of failure, (2) Reducing tool count by removing features — loses functionality

Outcome

Pending