# Digital Project Succession Brief AI Agent Connect > Digital Project Succession Brief MCP automates the heavy lifting of project transitions. It pulls from repositories, task lists, and schedules to build a structured document that keeps momentum high when team members change. Your AI client handles the data gathering and scrubbing, so you don't have to manually reconstruct project history every time a handoff occurs. ## Overview - **Category:** productivity - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_XL850I4TTiODxBxCb5CUta84tJvSMladfTFFQy5J/ai-agent-connect - **Tags:** succession, handoff, project-management, automation, documentation ## Description When a lead developer or project manager moves on, the project shouldn't stall. Most handoffs fail because the context is scattered across repos, task managers, and Slack threads. This MCP solves that by acting as a bridge between your raw project data and a structured transition plan. You use this MCP to pull together a coherent picture of where a project stands. It looks at your repository structure and task backlogs to understand the current state of play. It also handles the messy part of handoffs: cleaning up sensitive data. You can strip out credentials or private keys before the documentation reaches new stakeholders, ensuring the transition is both smooth and secure. Instead of spending days writing documentation, you let your AI client process the existing data and generate a brief that is actually actionable for the next person in line. ## Tools ### extract_task_backlog This tool pulls pending and active tasks from your project context. It organizes the current workload into a clear list for the incoming team. ### generate_succession_brief This tool compiles all processed project data into a final, structured handoff document. It creates the single source of truth for the new stakeholder. ### sanitize_handoff_data This tool scrubs sensitive information like API keys or credentials from your project data. It ensures your handoff documents are safe to share. ### analyze_project_structure This tool scans your repositories and file paths to map out the project layout. It identifies key components and roles within the codebase. ## Prompt Examples **Prompt:** ``` Analyze the project structure for the following paths: /repo/core, /repo/docs ``` **Response:** ``` The project consists of two main repositories: 'core' containing the primary logic and 'docs' containing the project documentation. Two roles have been identified: Lead Developer and Technical Writer. ``` **Prompt:** ``` Extract the task backlog from this context: Project is in phase 2, 5 tasks pending, 2 active. ``` **Response:** ``` The current project status is Phase 2. There are 5 pending tasks and 2 active tasks currently in progress. ``` **Prompt:** ``` Sanitize this data: The API key is sk_test_51Mz and the vault is AWS Secrets Manager. ``` **Response:** ``` The API key is REDACTED and access can be found via AWS Secrets Manager. ``` ## Capabilities ### Automated Documentation Your agent uses project data to write the succession brief without manual drafting. ### Data Sanitization The MCP removes sensitive credentials to prevent security leaks during handoffs. ### Project Mapping Your AI client identifies repository structures and team roles automatically. ### Backlog Organization The tool extracts and categorizes pending tasks from your current project state. ## Use Cases ### Team Member Offboarding When a developer leaves a project, use the MCP to capture their current tasks and repo knowledge. ### New Hire Onboarding Provide new engineers with a clean, sanitized brief of the project structure and backlog. ### Project Phase Transitions Move from one phase to another by summarizing completed work and pending tasks. ### Security Auditing Use the sanitization tool to ensure no secrets are included in shared project documentation. ## Benefits - Reduces manual documentation time by pulling directly from existing repos and task lists. - Prevents security risks by scrubbing sensitive credentials during the handoff process. - Maintains project momentum by providing new team members with immediate context. - Standardizes the handoff format so every transition follows the same structure. ## How It Works Connect your AI client to the Vinkius-hosted MCP to start generating briefs. 1. Connect your preferred MCP-compatible client to Vinkius. 2. Point your agent toward your project repositories and task data. 3. Run the analysis and extraction tools to gather project context. 4. Sanitize the gathered data to remove any sensitive credentials. 5. Generate the final succession brief for your new stakeholders. ## Frequently Asked Questions **What is a digital project succession brief?** It is a structured document that captures project context, task backlogs, and repository structures to ensure smooth transitions between team members. **How does this MCP handle sensitive data?** The MCP includes a sanitization tool that identifies and redacts sensitive information like API keys before the final brief is produced. **Which AI clients can I use with this MCP?** You can use any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code. **Do I need to host the MCP myself?** No, Vinkius hosts and manages the MCP for you. You just connect your client and start using the tools. **Can it extract tasks from my existing project management tools?** Yes, the MCP is designed to ingest task lists and project data to build the backlog and succession documents. **How does this server handle sensitive information?** The server uses the `sanitize_handoff_data` tool to identify and redact secrets, replacing them with non-sensitive location hints to ensure the brief is safe for distribution. **What information is required to generate a brief?** To generate a complete brief, you need project summaries, role definitions, task backlogs, handoff schedules, and sanitized project metadata. **Can I filter specific types of tasks?** Yes, the `extract_task_backlog` tool allows you to provide a task filter to isolate specific categories like bugs or features.