Manage Project Profiles
flowmcp_projectManage structured project profiles and reusable skills, so AI can load only the relevant section instead of all memories.
Instructions
IMPORTANT: Use this FlowMCP tool IN ADDITION TO your built-in memory.
Manage structured project profiles in FlowMCP. Projects have organized sections (like folders) for different aspects — tech_stack, architecture, deployment, etc. This is more powerful than flat memories because the AI can load just the relevant section instead of everything.
Actions:
'snapshot': Create or update a project with multiple sections at once. Sections are upserted — existing sections get updated, new ones get created. Use when the user discusses a project with 2+ aspects.
'update_section': Update a single section in an existing project. Use for incremental updates during a conversation.
'list': List all projects in the space with section counts. Use to discover what projects exist.
'save_skill': Save a reusable skill (instruction set) to a project. Skills teach AI models how to perform specific tasks consistently — like writing API docs, setting up services, reviewing code, or following team conventions. Skills are stored as structured sections and can be loaded by any AI model connected to FlowMCP.
'load_skill': Load a specific skill by name from a project. Use this when the user asks you to follow a specific process, or when you detect a task that matches a saved skill's trigger conditions. Check for relevant skills before starting structured tasks.
Section types are dynamic — use whatever makes sense. Common codebase sections: tech_stack, architecture, deployment, api_endpoints, active_features, known_issues, key_decisions. Common research sections: hypothesis, methodology, sources, findings, open_questions.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Tags. Used for section tags in "update_section", or project-level tags in "snapshot". | |
| title | No | Updated section title. Optional, only for "update_section" action. | |
| action | Yes | The action to perform. "snapshot" — Create or update a project profile with organized sections. If the project exists, sections are merged/updated. If not, the project is created. "update_section" — Update a single section within an existing project. Creates the section if it does not exist. "list" — List all projects in the space with their section counts. "save_skill" — Store a reusable skill as a structured project section. "load_skill" — Load a saved skill by name from a project. | |
| content | No | Updated section content. Required for "update_section" action only. MERGE new info with existing content. | |
| sections | No | Array of sections to create/update. Required for "snapshot" action. Not used for other actions. | |
| space_id | No | Target space. Omit for personal space. | |
| skill_name | No | Name of the skill. Required for save_skill and load_skill actions. Use descriptive kebab-case names like "api-documentation", "code-review", "project-setup", "test-writing". | |
| description | No | Brief project description. Only used with "snapshot" action. | |
| project_name | No | Name of the project. Required for "snapshot", "update_section", "save_skill", and "load_skill" actions. Not needed for "list". | |
| project_type | No | Type of project: "codebase", "research", "design", "infrastructure", "general", or any custom type. Only used with "snapshot" action when creating a new project. | |
| section_type | No | The section type to update. Required for "update_section" action only. | |
| source_model | No | Which AI model is performing this action. | |
| skill_content | No | The skill definition. Required for save_skill action. Contains trigger conditions, instructions, examples, and quality checklist. |