
clientos-brain
Clientos-brain serves as a living memory for agency project managers and consultants. Pull rich client briefs with get_client_context before meetings, track decisions via log_decision and get_decision_trail, flag risks with flag_risk, generate weekly summaries using summarize_project_week, and detect scope creep to protect agreed scopes. Stay ahead of project dynamics with precise, actionable insights.
Overview
clientos-brain acts as a living memory and intelligence layer for client projects in agencies and consultancies. It maintains detailed histories of decisions, risks, and scope changes, ensuring teams always access the full context. This prevents miscommunications and forgotten details during client interactions or project handoffs.
Key Capabilities
Use get_client_context to retrieve a client's personality profile, relationship score, active projects, open risks, and recent decisions before calls or meetings.
log_decision records project choices with rationale and authorship, optionally superseding prior ones, while get_decision_trail fetches the complete chronological decision history.
flag_risk logs concerns like blockers or technical debt with severity levels, visible in summaries; summarize_project_week generates shareable digests of recent activity; and detect_scope_creep scores task deviations from original scope (0–100) with flagged items.
Use Cases
Before a client meeting, call get_client_context to review their risk profile and recent decisions, tailoring your discussion to build rapport.
After a scope change debate, use log_decision to document the outcome and detect_scope_creep to quantify impacts against the baseline.
On Fridays, run summarize_project_week for a formatted update on decisions, resolved risks, and new tasks to email clients or teams.
When onboarding a new team member, query get_decision_trail and flagged risks via flag_risk to explain the project's current state and rationale.
Who This Is For
Project managers, account executives, and consultants in agencies handling multiple client engagements.
Requires basic familiarity with API tools but no advanced coding; ideal for teams using MCP servers in daily workflows.