Project Management MCP tools follow a delivery workflow across signed quote handoff, client briefs, SOP templates, projects, tasks, owners, deadlines, dependencies, milestones, file versions, comments and decisions, risks, time and cost tracking, client portal approvals, progress alerts, milestone invoicing, close-out reports, and audit logs.
project.config.get
readRead project numbering, statuses, permissions, working days, alerts, client portal, file versioning, and billing defaults.
-
Read-only; baseline before project writes.
Do not expose secrets, private integration tokens, or settings outside role scope.
project.workflow_templates.list
readList available project SOP templates, business use, stages, task count, default owner roles, and versions.
project.config.get
Read-only; used before planning or applying templates.
Show only templates authorized for the department; avoid leaking internal process.
project.workflow_template.get
readRead one template's stages, tasks, dependencies, checkpoints, deliverables, default deadlines, and risk hints.
project.workflow_templates.list
Read-only; required before AI task breakdown or batch task creation.
Do not modify template; expose template version to avoid applying outdated SOP.
project.signed_sources.list
readList signed quotations, confirmed orders, or contracts that can create projects.
project.config.get
Read-only; verify source state before automatic project creation.
Read only confirmed/signed sources; do not treat draft quotes as project-ready.
project.client_brief.get
readRead client requirements, scope, files, constraints, delivery criteria, communication history, and confirmed decisions.
project.signed_sources.list
Read-only; the brief must be the primary input for AI planning.
Mask sensitive client data by project permission; do not use unconfirmed chat snippets as formal scope.
project.projects.list
readList projects by client, owner, status, stage, delivery date, or health.
project.config.get
Read-only; used to avoid duplicate projects and review progress.
Return only projects visible to the user; avoid cross-client or cross-department leakage.
project.project.get
readRead project goals, scope, client, owner, members, stages, budget, risks, and delivery records.
project.projects.list
Read-only; required before project updates, batch task creation, or close-out.
Mask internal costs, contracts, and client files by role.
project.members.list
readList project members, roles, permissions, departments, task eligibility, and client portal visibility.
project.project.get
Read-only; used before task assignment, permissions, or client visibility changes.
Do not expose staff private data or non-project permissions.
project.workload.list
readRead member task load, availability, overdue tasks, field schedules, and overload risk.
project.members.list, project.tasks.list
Read-only; used before automated assignment, rebalancing, or delay alerts.
Avoid public staff performance comparisons; return workload needed for operations only.
project.stages.list
readRead project stages, board columns, process order, entry criteria, completion criteria, and client visibility.
project.project.get, project.workflow_template.get
Read-only; used before board or milestone updates.
Do not mislabel internal stages as client-visible.
project.milestones.list
readList milestones, delivery dates, completion state, sign-off state, billing triggers, and related tasks.
project.project.get
Read-only; used before milestone completion, client approval, and invoicing.
Do not show contract amounts or billing terms to unauthorized roles.
project.tasks.list
readList tasks by project, stage, owner, status, priority, due date, or overdue state.
project.project.get
Read-only; used before tracking, alerts, assignment, or batch updates.
Return only visible tasks; client portal tasks must respect visibility scope.
project.task.get
readRead task description, owner, deadline, state, dependencies, comments, attachments, time logs, and acceptance criteria.
project.tasks.list
Read-only; required before task update, completion, or decision recording.
Mask sensitive comments and attachments by permission.
project.dependencies.list
readList task dependencies, blockers, critical path, and delay propagation impact.
project.tasks.list
Read-only; used before schedule risk previews and dependency updates.
Do not alter critical path based on incomplete task data.
project.files.list
readList project files, contracts, drawings, reports, versions, owners, related tasks, and access scope.
project.project.get
Read-only; used before attachments, versioning, or client portal publishing.
Do not treat internal files as client-visible.
project.file_version.get
readRead one file version, change summary, sign-off state, uploader, and traceable source.
project.files.list
Read-only; verify before revision, delivery, or client sign-off.
Avoid delivering old versions; latest status must be explicit.
project.comments.list
readRead project or task comments, field updates, client replies, blocker notes, and follow-ups.
project.task.get
Read-only; used before decision extraction, close-out, or follow-up.
Private/internal comments must not leak into client reports.
project.decisions.list
readList confirmed decisions, client changes, approvals, owners, and effective scope.
project.comments.list, project.audit_logs.list
Read-only; prevents unconfirmed comments from becoming decisions.
Decisions must include source, timestamp, and approver.
project.risks.list
readRead project risks, blockers, delay reasons, impact, mitigation actions, and owners.
project.project.get, project.tasks.list
Read-only; used before risk summaries or schedule previews.
Risk summaries must separate facts, inferences, and recommendations.
project.time_logs.list
readList task or project time logs, people, dates, approval state, and cost attribution.
project.project.get, project.tasks.list
Read-only; used before cost analysis, profitability, or close-out.
Protect pay inference and personal performance data by permission.
project.expenses.list
readList materials, procurement, subcontracting, travel, and other project expenses with receipts and approval state.
project.project.get
Read-only; used before cost, profit, and reporting workflows.
Mask supplier-sensitive terms and receipts by role.
project.client_portal_state.get
readRead client portal visible stages, tasks, files, deliverables, approval requests, and comment permissions.
project.project.get, project.files.list, project.milestones.list
Read-only; verify before publishing or requesting client approval.
Strictly separate internal view from client view.
project.health_summary.get
readRead project health, completion rate, overdue items, blockers, workload, cost variance, and delivery risk.
project.tasks.list, project.dependencies.list, project.time_logs.list, project.expenses.list
Read-only; used for manager dashboard, alerts, and close-out.
Prefer aggregate view; avoid exposing sensitive individual performance.
project.audit_logs.list
readList audit logs for projects, tasks, files, decisions, approvals, time, costs, and invoices.
project.project.get
Read-only; used for disputes, errors, accountability, and approval history.
Audit logs are restricted to authorized administrators.
project.brief_to_plan.preview
previewPreview a project plan from client brief and SOP template, including tasks, owners, deadlines, checkpoints, and risks.
project.client_brief.get, project.workflow_template.get, project.workload.list
Preview required; project lead approval required before creating project and tasks.
Mark AI-inferred items clearly; do not write unconfirmed scope into the project.
project.template_apply.preview
previewPreview stages, tasks, dependencies, checkpoints, deliverables, and alerts added by applying a SOP template.
project.workflow_template.get, project.project.get, project.tasks.list
Confirm no duplicate tasks or overwritten workflows before applying template.
Do not overwrite completed tasks or signed-off milestones.
project.task_batch.preview
previewPreview batch task create/update with owners, deadlines, dependencies, alerts, client visibility, and duplicate checks.
project.brief_to_plan.preview, project.tasks.list, project.members.list
Batch task writes require project lead approval.
Requires idempotency; avoid duplicate task batches.
project.assignment.preview
previewPreview workload, overload, deadline conflicts, and alternative assignees after task assignment or rebalancing.
project.workload.list, project.members.list, project.tasks.list
Bulk rebalancing or cross-department assignment requires manager approval.
Do not assign tasks to unauthorized, unavailable, or clearly overloaded members.
project.schedule_risk.preview
previewPreview delay, dependency, critical path, resource shortage, cost variance, and client approval risks.
project.dependencies.list, project.health_summary.get, project.client_portal_state.get
Risk recommendations must be confirmed before plan updates or alerts.
Risk predictions must list evidence and not be presented as facts.
project.client_portal_publish.preview
previewPreview stages, files, deliverables, task progress, or approval requests to be published to the client portal.
project.client_portal_state.get, project.files.list, project.milestones.list
Client-visible content must be approved by an authorized person.
Prevent internal comments, costs, or unfinished files from being exposed.
project.milestone_invoice.preview
previewPreview invoice amount, contract terms, client approval, tax, and accounting sync impact after milestone completion.
project.milestones.list, project.client_portal_state.get, project.expenses.list
Confirm milestone completion and client/internal approval before invoicing.
Do not invoice before conditions are met; prevent duplicate invoicing.
project.closeout_report.preview
previewPreview close-out report with milestones, outcomes, files, sign-offs, time/costs, risks, and follow-ups.
project.project.get, project.milestones.list, project.files.list, project.time_logs.list, project.expenses.list, project.decisions.list
Project lead approval required before formal generation or client delivery.
Exclude internal costs, private comments, and unpublished decisions.
project.project.create
writeCreate a project with client, goals, scope, owner, team, stages, budget, and initial status.
project.brief_to_plan.preview
Must be created from project lead approved preview.
Check duplicate projects, permissions, and idempotency.
project.project.update
writeUpdate project scope, status, priority, owner, delivery date, budget, or client visibility.
project.project.get, project.schedule_risk.preview
Scope, delivery date, budget, or client visibility changes require approval.
Keep change reason and audit; do not silently change confirmed scope.
project.project.create_from_signed_source
writeCreate a project from signed quote, order, or contract with linked brief, amount, deliverables, and owner.
project.signed_sources.list, project.client_brief.get, project.brief_to_plan.preview
Must confirm source is signed and not already project-linked.
Do not create projects from draft quotes or unconfirmed orders.
project.workflow_template.upsert
writeCreate or update SOP templates, stages, default tasks, roles, dependencies, checkpoints, and delivery standards.
project.workflow_template.get, project.template_apply.preview
Template changes affect future projects and require admin approval.
Keep versions; do not retroactively overwrite active projects.
project.task_batch.create
writeBatch-create tasks, owners, deadlines, dependencies, checkpoints, alerts, and client visibility.
project.task_batch.preview
Must execute from an approved task batch preview.
Requires idempotency; check duplicate tasks and invalid owners.
project.task.upsert
writeCreate or update one task's description, owner, deadline, priority, dependencies, acceptance criteria, and visibility.
project.task.get, project.assignment.preview
Material deadline, owner, or client-visible changes require approval.
Do not overwrite completed task outcomes.
project.task.status_update
writeUpdate task state, progress, blocker, field update, completion percentage, or next step.
project.task.get, project.dependencies.list
Owners may update routine progress; completion or blocker resolution follows workflow confirmation.
Status changes need timestamp and actor; do not skip required predecessors.
project.dependency.upsert
writeCreate or update task dependencies, blockers, critical path markers, and delay propagation rules.
project.dependencies.list, project.schedule_risk.preview
Approval required when delivery date or multi-person tasks are affected.
Avoid circular dependencies; risk must be recalculated.
project.milestone.upsert
writeCreate or update milestones, delivery dates, completion criteria, client sign-off requirements, and billing triggers.
project.milestones.list, project.schedule_risk.preview
Delivery date, billing trigger, or client approval changes require approval.
Do not alter signed-off milestones without audit.
project.milestone.complete
writeMark milestone complete with deliverables, sign-off, completion date, follow-up tasks, and invoice-ready state.
project.milestones.list, project.files.list, project.client_portal_state.get
Required tasks and deliverables must be checked before completion.
Do not complete milestones with blocking tasks unless an admin approves exception.
project.member.assign
writeAdd, remove, or change project member roles, task ownership scope, and permissions.
project.members.list, project.assignment.preview
Permission elevation, cross-department, or bulk assignment requires manager approval.
Do not grant unauthorized members access to sensitive client files.
project.file.attach
writeAttach files, contracts, drawings, photos, reports, or sign-off records to projects or tasks with version and visibility.
project.files.list, project.file_version.get
Client-visible or contract files require authorized confirmation.
Check file type and permissions; avoid overwriting latest version.
project.comment.add
writeAdd project or task comments, field updates, blocker notes, client reply summaries, or follow-ups.
project.task.get, project.comments.list
Routine comments follow role permission; client-visible comments must be explicit.
Do not mark private internal comments as client-visible.
project.decision.record
writeRecord confirmed decisions, change requests, approval results, impact scope, source, and owner.
project.decisions.list, project.comments.list, project.audit_logs.list
Decisions must be confirmed by an authorized person or client before writing.
Do not treat AI summaries as confirmed decisions.
project.client_approval.request
writeRequest client or internal approval for stage outcomes, files, revisions, or milestones.
project.client_portal_publish.preview
Published content and recipients must be confirmed first.
Avoid sending internal files, costs, or unfinished drafts to clients.
project.client_approval.record
writeRecord client or internal approval, rejection, revision request, sign-off time, and attachments.
project.client_portal_state.get, project.decisions.list
Approval result must include source, timestamp, and identity verification.
Do not fabricate client approvals; all sign-offs must be traceable.
project.time_log.create
writeCreate time logs for tasks or projects with work notes, date, person, billable state, and approval state.
project.task.get, project.time_logs.list
Staff may submit; modifying approved time requires manager approval.
Prevent duplicate time logs and unreasonable entries.
project.expense.record
writeRecord materials, procurement, subcontracting, or travel expenses with receipts, supplier, task, and approval workflow.
project.expenses.list, project.project.get
Over-budget or receipt-missing expenses require manager approval.
Prevent duplicate reimbursement; protect sensitive receipts by permission.
project.alert_rule.upsert
writeCreate or update alerts for overdue tasks, upcoming deadlines, blockers, overload, pending client approvals, or cost overruns.
project.config.get, project.schedule_risk.preview, project.health_summary.get
Rules affecting many people or clients require manager approval.
Avoid notification spam; respect frequency and recipient permissions.
project.milestone_invoice.create
writeCreate an invoice or accounting-system invoice request from completed and approved milestones.
project.milestone_invoice.preview
Finance or authorized owner approval required.
Requires idempotency; check existing invoices and contract terms.
project.action_request.status
statusCheck write request, approval, execution, failure, retry, and audit status for project actions.
project.audit_logs.list
Read-only status; tracks batch tasks, client approvals, invoicing, and report generation.
Status endpoint must not re-execute writes.