Project Management MCP Tools
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.
Read project numbering, statuses, permissions, working days, alerts, client portal, file versioning, and billing defaults.
Governance
Read-only; baseline before project writes.
Safety
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.
Read first
project.config.get
Governance
Read-only; used before planning or applying templates.
Safety
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.
Read first
project.workflow_templates.list
Governance
Read-only; required before AI task breakdown or batch task creation.
Safety
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.
Read first
project.config.get
Governance
Read-only; verify source state before automatic project creation.
Safety
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.
Read first
project.signed_sources.list
Governance
Read-only; the brief must be the primary input for AI planning.
Safety
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.
Read first
project.config.get
Governance
Read-only; used to avoid duplicate projects and review progress.
Safety
Return only projects visible to the user; avoid cross-client or cross-department leakage.
Read project goals, scope, client, owner, members, stages, budget, risks, and delivery records.
Read first
project.projects.list
Governance
Read-only; required before project updates, batch task creation, or close-out.
Safety
Mask internal costs, contracts, and client files by role.
List project members, roles, permissions, departments, task eligibility, and client portal visibility.
Read first
project.project.get
Governance
Read-only; used before task assignment, permissions, or client visibility changes.
Safety
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.
Read first
project.members.list, project.tasks.list
Governance
Read-only; used before automated assignment, rebalancing, or delay alerts.
Safety
Avoid public staff performance comparisons; return workload needed for operations only.
Read project stages, board columns, process order, entry criteria, completion criteria, and client visibility.
Read first
project.project.get, project.workflow_template.get
Governance
Read-only; used before board or milestone updates.
Safety
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.
Read first
project.project.get
Governance
Read-only; used before milestone completion, client approval, and invoicing.
Safety
Do not show contract amounts or billing terms to unauthorized roles.
List tasks by project, stage, owner, status, priority, due date, or overdue state.
Read first
project.project.get
Governance
Read-only; used before tracking, alerts, assignment, or batch updates.
Safety
Return only visible tasks; client portal tasks must respect visibility scope.
Read task description, owner, deadline, state, dependencies, comments, attachments, time logs, and acceptance criteria.
Read first
project.tasks.list
Governance
Read-only; required before task update, completion, or decision recording.
Safety
Mask sensitive comments and attachments by permission.
project.dependencies.list
readList task dependencies, blockers, critical path, and delay propagation impact.
Read first
project.tasks.list
Governance
Read-only; used before schedule risk previews and dependency updates.
Safety
Do not alter critical path based on incomplete task data.
List project files, contracts, drawings, reports, versions, owners, related tasks, and access scope.
Read first
project.project.get
Governance
Read-only; used before attachments, versioning, or client portal publishing.
Safety
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.
Read first
project.files.list
Governance
Read-only; verify before revision, delivery, or client sign-off.
Safety
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.
Read first
project.task.get
Governance
Read-only; used before decision extraction, close-out, or follow-up.
Safety
Private/internal comments must not leak into client reports.
project.decisions.list
readList confirmed decisions, client changes, approvals, owners, and effective scope.
Read first
project.comments.list, project.audit_logs.list
Governance
Read-only; prevents unconfirmed comments from becoming decisions.
Safety
Decisions must include source, timestamp, and approver.
Read project risks, blockers, delay reasons, impact, mitigation actions, and owners.
Read first
project.project.get, project.tasks.list
Governance
Read-only; used before risk summaries or schedule previews.
Safety
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.
Read first
project.project.get, project.tasks.list
Governance
Read-only; used before cost analysis, profitability, or close-out.
Safety
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.
Read first
project.project.get
Governance
Read-only; used before cost, profit, and reporting workflows.
Safety
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.
Read first
project.project.get, project.files.list, project.milestones.list
Governance
Read-only; verify before publishing or requesting client approval.
Safety
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.
Read first
project.tasks.list, project.dependencies.list, project.time_logs.list, project.expenses.list
Governance
Read-only; used for manager dashboard, alerts, and close-out.
Safety
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.
Read first
project.project.get
Governance
Read-only; used for disputes, errors, accountability, and approval history.
Safety
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.
Read first
project.client_brief.get, project.workflow_template.get, project.workload.list
Governance
Preview required; project lead approval required before creating project and tasks.
Safety
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.
Read first
project.workflow_template.get, project.project.get, project.tasks.list
Governance
Confirm no duplicate tasks or overwritten workflows before applying template.
Safety
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.
Read first
project.brief_to_plan.preview, project.tasks.list, project.members.list
Governance
Batch task writes require project lead approval.
Safety
Requires idempotency; avoid duplicate task batches.
project.assignment.preview
previewPreview workload, overload, deadline conflicts, and alternative assignees after task assignment or rebalancing.
Read first
project.workload.list, project.members.list, project.tasks.list
Governance
Bulk rebalancing or cross-department assignment requires manager approval.
Safety
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.
Read first
project.dependencies.list, project.health_summary.get, project.client_portal_state.get
Governance
Risk recommendations must be confirmed before plan updates or alerts.
Safety
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.
Read first
project.client_portal_state.get, project.files.list, project.milestones.list
Governance
Client-visible content must be approved by an authorized person.
Safety
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.
Read first
project.milestones.list, project.client_portal_state.get, project.expenses.list
Governance
Confirm milestone completion and client/internal approval before invoicing.
Safety
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.
Read first
project.project.get, project.milestones.list, project.files.list, project.time_logs.list, project.expenses.list, project.decisions.list
Governance
Project lead approval required before formal generation or client delivery.
Safety
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.
Read first
project.brief_to_plan.preview
Governance
Must be created from project lead approved preview.
Safety
Check duplicate projects, permissions, and idempotency.
project.project.update
writeUpdate project scope, status, priority, owner, delivery date, budget, or client visibility.
Read first
project.project.get, project.schedule_risk.preview
Governance
Scope, delivery date, budget, or client visibility changes require approval.
Safety
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.
Read first
project.signed_sources.list, project.client_brief.get, project.brief_to_plan.preview
Governance
Must confirm source is signed and not already project-linked.
Safety
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.
Read first
project.workflow_template.get, project.template_apply.preview
Governance
Template changes affect future projects and require admin approval.
Safety
Keep versions; do not retroactively overwrite active projects.
project.task_batch.create
writeBatch-create tasks, owners, deadlines, dependencies, checkpoints, alerts, and client visibility.
Read first
project.task_batch.preview
Governance
Must execute from an approved task batch preview.
Safety
Requires idempotency; check duplicate tasks and invalid owners.
Create or update one task's description, owner, deadline, priority, dependencies, acceptance criteria, and visibility.
Read first
project.task.get, project.assignment.preview
Governance
Material deadline, owner, or client-visible changes require approval.
Safety
Do not overwrite completed task outcomes.
project.task.status_update
writeUpdate task state, progress, blocker, field update, completion percentage, or next step.
Read first
project.task.get, project.dependencies.list
Governance
Owners may update routine progress; completion or blocker resolution follows workflow confirmation.
Safety
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.
Read first
project.dependencies.list, project.schedule_risk.preview
Governance
Approval required when delivery date or multi-person tasks are affected.
Safety
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.
Read first
project.milestones.list, project.schedule_risk.preview
Governance
Delivery date, billing trigger, or client approval changes require approval.
Safety
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.
Read first
project.milestones.list, project.files.list, project.client_portal_state.get
Governance
Required tasks and deliverables must be checked before completion.
Safety
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.
Read first
project.members.list, project.assignment.preview
Governance
Permission elevation, cross-department, or bulk assignment requires manager approval.
Safety
Do not grant unauthorized members access to sensitive client files.
Attach files, contracts, drawings, photos, reports, or sign-off records to projects or tasks with version and visibility.
Read first
project.files.list, project.file_version.get
Governance
Client-visible or contract files require authorized confirmation.
Safety
Check file type and permissions; avoid overwriting latest version.
Add project or task comments, field updates, blocker notes, client reply summaries, or follow-ups.
Read first
project.task.get, project.comments.list
Governance
Routine comments follow role permission; client-visible comments must be explicit.
Safety
Do not mark private internal comments as client-visible.
project.decision.record
writeRecord confirmed decisions, change requests, approval results, impact scope, source, and owner.
Read first
project.decisions.list, project.comments.list, project.audit_logs.list
Governance
Decisions must be confirmed by an authorized person or client before writing.
Safety
Do not treat AI summaries as confirmed decisions.
project.client_approval.request
writeRequest client or internal approval for stage outcomes, files, revisions, or milestones.
Read first
project.client_portal_publish.preview
Governance
Published content and recipients must be confirmed first.
Safety
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.
Read first
project.client_portal_state.get, project.decisions.list
Governance
Approval result must include source, timestamp, and identity verification.
Safety
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.
Read first
project.task.get, project.time_logs.list
Governance
Staff may submit; modifying approved time requires manager approval.
Safety
Prevent duplicate time logs and unreasonable entries.
project.expense.record
writeRecord materials, procurement, subcontracting, or travel expenses with receipts, supplier, task, and approval workflow.
Read first
project.expenses.list, project.project.get
Governance
Over-budget or receipt-missing expenses require manager approval.
Safety
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.
Read first
project.config.get, project.schedule_risk.preview, project.health_summary.get
Governance
Rules affecting many people or clients require manager approval.
Safety
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.
Read first
project.milestone_invoice.preview
Governance
Finance or authorized owner approval required.
Safety
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.
Read first
project.audit_logs.list
Governance
Read-only status; tracks batch tasks, client approvals, invoicing, and report generation.
Safety
Status endpoint must not re-execute writes.