# RevCent MCP Guide: `CreateProject` AI/MCP-focused guide for creating a RevCent Project. --- ## Related Documentation Read `Project Overview` first. Business onboarding is one important Project use case, but Projects are not limited to businesses. | Guide | Link | Why It Matters | |---|---|---| | Project Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewProject.md` | Explains Projects as durable AI/MCP pseudo repositories for businesses, objectives, reporting workspaces, external-agent source-of-truth context, and operational notes. | | GetProjects | `https://revcent.com/documentation/markdown/mcp/operation/GetProjects.md` | Check whether a relevant Project already exists before creating a new one. | | SearchProjects | `https://revcent.com/documentation/markdown/mcp/operation/SearchProjects.md` | Search existing Projects by name/description search term or associated entity ID before creating duplicates or paging through broad Project lists. | | GetProject | `https://revcent.com/documentation/markdown/mcp/operation/GetProject.md` | Retrieve one Project, including its name, description, and associated entities. | | ProjectAssociateEntity | `https://revcent.com/documentation/markdown/mcp/operation/ProjectAssociateEntity.md` | Associate related RevCent entities with the Project after creation. | | GetProjectNotes | `https://revcent.com/documentation/markdown/mcp/operation/GetProjectNotes.md` | Retrieve Project Note titles and metadata when Project history is needed. | | GetProjectNote | `https://revcent.com/documentation/markdown/mcp/operation/GetProjectNote.md` | Retrieve the full content of a specific Project Note when needed. | | CreateProjectNote | `https://revcent.com/documentation/markdown/mcp/operation/CreateProjectNote.md` | Briefly record important Project creation context, decisions, and follow-up work. | | SearchProjectNotes | `https://revcent.com/documentation/markdown/mcp/operation/SearchProjectNotes.md` | Search Project Notes by keyword or phrase, optionally within a specific Project, when note content or history needs to be found quickly. | --- ## Operation Summary Operation: ```text CreateProject ``` Purpose: ```text Create a Project in RevCent. ``` A Project is a durable RevCent context container that behaves like a **pseudo repository** for AI/MCP work. A Project can represent: - a business being onboarded, - an account setup initiative, - a WooCommerce/store implementation, - an operational objective, - a metrics/reporting workspace, - a business advice or analysis workspace, - an external-agent source of truth, - a notes repository or operating journal, - a group of related RevCent entities. A Project helps save AI tokens by storing durable context outside the active conversation. Future AI/MCP can retrieve the relevant Project, associated entities, and selected Project Notes instead of keeping all historical information in prompt context. Simple model: ```text Project = pseudo repository for durable AI/MCP context Project name = concise repository label Project description = README-like source-of-truth purpose statement Project entities = related RevCent objects / repository index Project notes = compact history, decisions, findings, and follow-up ``` Use `CreateProject` when durable context should be preserved and no existing Project clearly matches the work. --- ## Project Search Note Use `SearchProjects` when AI/MCP has a business name, Project name, objective phrase, report name, agent purpose, or known associated entity ID and needs to locate a relevant Project quickly. `SearchProjects` can search Project `name` and `description` with `search_term`. It can also find Projects by associated entity IDs such as `campaign_id`, `product_id`, `payment_profile_id`, `ai_assistant_id`, `custom_function_id`, `third_party_shop_id`, `tracking_domain_id`, and other supported Project association IDs. Use `SearchProjects` before creating a new Project when a search term or associated entity ID is available. Use `GetProject` afterward to retrieve the full Project details and associated entities for the selected Project. --- ## When to Use Use `CreateProject` when: - a user is onboarding a business into RevCent, - a user is setting up or modifying RevCent configuration, - a user is starting a meaningful operational initiative, - AI/MCP needs a reusable context container before creating or editing related entities, - the work will involve recurring analysis, reporting, or recommendations, - an external agent needs a source-of-truth Project for its objective, - notes, decisions, warnings, or follow-up should be retained for future sessions, - there is no existing Project that clearly matches the business, objective, workflow, report, agent, or operation. Do not create a new Project for every tiny one-off action. Prefer an existing relevant Project when one already exists. Decision rule: ```text If future AI/MCP would benefit from retrieving this context later, use a Project. ``` --- ## Project Scope Guidance A Project should have a clear purpose and boundary. Good Project scopes include: - one specific business onboarding or implementation, - one operational objective, - one reporting or analysis workspace, - one external-agent purpose, - one related group of RevCent configuration work, - one durable notes/context repository. Avoid mixing unrelated objectives into one Project. A broad Project can make future AI/MCP retrieve irrelevant context and waste tokens. Business-specific Projects should include the business name. Objective-specific Projects should include the objective. Reporting Projects should include the report or metric purpose. Agent Projects should include the agent purpose. --- ## Input Schema | Field | Type | Required | Description | |---|---:|---:|---| | `name` | string | Yes | Project name. Use a concise name that identifies the business, objective, report, agent, workflow, or notes repository. | | `description` | string | No | Project description. Use a README-like description that explains the Project purpose, scope, systems/entities involved, and what future AI/MCP should understand before acting. | Schema behavior: ```text CreateProject requires name. description is optional, but strongly recommended when the Project will be used by AI/MCP as durable context. ``` --- ## Naming Guidance Use names that make the Project easy to identify from a list. Good naming patterns: ```text [Business Name] [Implementation / Migration / Setup] [Objective] Initiative [Metric / Report] Review [Agent Purpose] Source of Truth [Workflow] Operating Notes ``` Avoid vague names: ```text Setup Changes Stuff New Project Notes Main ``` --- ## Description Guidance The Project description is the Project's README-like source-of-truth statement. It should explain: - why the Project exists, - whether it is for a business, objective, report, workflow, agent, or notes repository, - the scope and boundaries, - relevant RevCent entity categories, - systems involved, such as WooCommerce, email, payment, fulfillment, AI, reporting, or agents, - warnings, assumptions, or confirmation requirements, - what future AI/MCP should review before acting. A good description reduces token usage because future AI/MCP can quickly understand the Project without reconstructing its purpose from conversation history. --- ## Example Request Bodies Business onboarding Project: ```json { "name": "Acme Skincare WooCommerce Implementation", "description": "Pseudo repository for Acme Skincare's WooCommerce implementation in RevCent, including shop setup, product import, payment/subscription configuration, shipping, tax, fulfillment, email, customer portal, and AI support context." } ``` Reporting Project: ```json { "name": "Monthly Subscription Metrics Review", "description": "Reporting workspace for recurring subscription metrics analysis, including reviewed date ranges, key findings, recommendations, assumptions, and follow-up questions." } ``` External-agent Project: ```json { "name": "Renewal Recovery Agent Source of Truth", "description": "Source-of-truth Project for the renewal recovery agent, including its objective, allowed actions, relevant RevCent entities, escalation rules, safety constraints, and operating context." } ``` --- ## Output Schema Successful output can include: | Field | Description | |---|---| | `api_call_id` | 20-character API call ID. | | `api_call_unix` | Unix timestamp when the API call was initiated. | | `code` | API response code. `1` indicates success. | | `project_id` | 20-character Project ID. | | `result` | Result message. | --- ## Recommended Workflow ```text 1. Use `SearchProjects` when a name, phrase, or associated entity ID is available; otherwise use `GetProjects` to check whether a relevant Project already exists. 2. If needed, use GetProject on likely matches to inspect details and associated entities. 3. If no relevant Project exists, run CreateProject with a clear name and README-like description. 4. Briefly create a Project Note for important creation context when the Project will be used for ongoing AI/MCP work. 5. Associate related RevCent entities with the Project using ProjectAssociateEntity as work progresses. 6. Use Project Overview and Project Note operation guides when deeper Project Note behavior is needed. ``` Project Notes are mentioned here only as a companion memory mechanism. For details about note title/content behavior and retrieval, use: ```text https://revcent.com/documentation/markdown/mcp/operation/OverviewProject.md https://revcent.com/documentation/markdown/mcp/operation/CreateProjectNote.md https://revcent.com/documentation/markdown/mcp/operation/GetProjectNotes.md https://revcent.com/documentation/markdown/mcp/operation/GetProjectNote.md ``` --- ## Common Mistakes to Avoid Do not: - create duplicate Projects without checking `GetProjects`, - treat Projects as only business containers, - create a Project with a vague name or empty-looking purpose, - use one broad Project for unrelated businesses, objectives, reports, or agents, - omit the description when AI/MCP will need durable context, - create Project-related entities without associating them when association is supported, - store all historical context in active prompt memory instead of using the Project as a pseudo repository, - create a Project for a tiny one-off task with no future context value. --- ## Final AI/MCP Instruction Use `CreateProject` to create a durable pseudo repository for RevCent work when future AI/MCP, users, reports, or external agents will benefit from reusable context. A Project may represent a business, objective, report, workflow, agent source of truth, or notes repository. Use a clear name and README-like description, check for existing Projects first, and briefly record important creation context with Project Notes when the Project will be used over time. --- Document Parent Directory * [Operations](https://revcent.com/documentation/markdown/mcp/operation/index.md) - AI/MCP details and overviews for operations available within the RevCent MCP.