Skip to main content
MSPortal connects the delivery record to the client conversation. Use Project AI to explain current work and propose changes, MCP to connect supported project operations to external AI tools, and project content in reports and meeting agendas.

​
Ask Project AI about the project

Open a project, then select Open Project AI at the right edge of the workspace. Ask a specific question, such as:
Summarize progress, open decisions, and the next delivery steps for this project. Explain any missing evidence.
The assistant can use project details, phases, tickets, milestones, deliverables, decisions, action items, available time entries, notes, and prior updates. Its answer depends on the information your account can access. Read-only users can ask questions without receiving permission to apply changes.

​
Draft and save a weekly update

1

Request an evidence-based draft

Ask: Draft a weekly project update using the latest tickets, time entries, milestones, decisions, and prior updates. Specify the reporting week and whether the update is internal if those matter.
2

Review the proposed change

Check the reporting week, summary, progress, next steps, risks, and client visibility. The proposal is a draft; it has not yet been saved.
3

Apply the update

Select Apply on the proposal you want to save. Wait for its applied state, then open Updates and confirm the resulting record.
A new weekly update proposal can default to client-visible. Check that setting before applying it. A client-visible record is different from sending an email; review any separate sending action before using it.
You can also ask for proposed milestones, deliverables, decisions, action items, or supported status and assignment changes. Review each proposal individually. The assistant must report an applied result before a change can be treated as saved.

A real AI draft, reviewed and applied to the walkthrough project.

​
Connect external AI tools through MCP

Configure a connection through Settings > MCP Server using the MCP Server guide. The connected user’s permissions, selected OAuth scopes, and company access determine which tools and records are available. Project MCP tools cover these workflows: Write tools use a proposal-and-confirmation flow. Read the proposed target and changes before confirming in the connected AI client.
MCP support is specific to each operation. The current project MCP catalog does not expose native project creation, template design, or native phase/ticket creation and deletion. Use the app for those workflows. Do not assume a PSA-specific note tool supports native tickets merely because both appear in Projects.
For example, ask a connected assistant to find a project, summarize its delivery evidence, and propose a weekly update. Review and confirm the proposed write before expecting it in the project’s Updates tab. See the MCP tool reference for the wider catalog.

​
Bring project context into a QBR report

Select the company in the header, then open Reports > New Report > Builder, or edit an existing report. The builder requires company scope and can auto-save a new report as you work. In the report builder, choose the project block that answers the client’s question: Some blocks summarize the company’s projects; others offer a project selector. Review each block’s date range and configuration, including Include Closed Projects where available, and inspect the report’s actual output. A new project may not have time, cost, or historical evidence for every block. Do not treat an empty result as proof that work is complete or on budget. Save the report and review its access and delivery options before sharing. Follow Reporting for the full report workflow.

​
Add a project to a meeting agenda

Open the relevant company meeting and use Add Item to choose Project. When creating a meeting first, confirm that the company name has appeared in Select company before saving its draft. Search for the project available for the meeting’s company, select it, and choose Add Selected. Wait for the agenda item to appear. Arrange it alongside supporting reports or discussion points. The project agenda view brings available health, dates, milestones, delivery information, and client actions into the discussion. Use Present, then Next to move from the agenda overview to the project slide and inspect what participants will see before the meeting. Record decisions and follow-up work in the appropriate place after the discussion. A meeting note is not automatically a change to a project ticket or a completed client decision. Review invitations, summaries, and any other sending action separately. See Meeting Pages and Meeting Summaries for meeting controls and reviewed communications.

​
Troubleshooting

Native Projects

Follow the full creation-to-closeout workflow.

Project workspace

Use the project’s delivery and collaboration tabs.