This article provides a deeper look at the key improvements delivered in Precursive 2.25. It is intended for customers, admins, and power users who want to understand what changed, how new capabilities work, and enablement guidance on how to roll out these changes successfully. Version 2.25 introduces the Precursive MCP Server, connecting MCP-compatible AI assistants such as Claude or Copilot directly to your Precursive data, and extends Precursive's permission and validation guardrails to every route, so that each action runs under the user's own permissions and is validated the same way however it is made.

Precursive MCP Server

Highlights

Connect any MCP-compatible AI assistant, such as Claude or Copilot, directly to your Precursive data. A curated catalogue of tools lets the assistant read and act on Projects, Resources, Bookings, Tasks and Timesheets, always running as the connected user and bounded by that user's existing permissions.

What Changed

Precursive now ships a native, Salesforce-hosted MCP (Model Context Protocol) server inside the core package. The server gives an MCP-compatible assistant, such as Claude, a curated set of tools to read and act on your Projects, Resources, Bookings, Tasks and Timesheets. Every tool runs as the connected user, so an assistant can only see and perform what that user is permitted to do in Precursive, and any action the user is not permitted to take is refused with a clear message rather than appearing to succeed.

How It Works

Once your admin has connected the Precursive MCP server to your AI assistant, you can work with Precursive in plain language instead of navigating the interface. For example, you can ask your assistant to:

• Find Projects, Resources or Tasks.
• Check utilisation and availability across a Team or a date range.
• Create and update Bookings, and assign Participants and Contributors to Phases and Tasks.
• Log time against a Project, Phase or Task, and submit a Timesheet for approval.
• Approve or reject Timesheets you are the approver of.
• Refresh Project Budgets and start longer background jobs, then check when they have completed.

Every action runs under your own account, so you can only see and change what your Precursive permissions already allow. To connect, see Getting Started with Precursive MCP. For the full list of what an assistant can and cannot do, see Precursive MCP Capabilities.

Enablement Guidance

The full step-by-step guide, including the External Client App settings, permissions, governance and security considerations, and troubleshooting, is in Setting Up the Precursive MCP Server. 

Extending Precursive's Guardrails to Every Route

Highlights

Precursive 2.25 extends the permission checks and business rules that guard the Precursive user interface to every route - the API, Flows, Data Loader and an AI assistant. Each action runs under the user's own Salesforce permissions and is validated the same way, however your data is created or changed.

What Changed

Precursive checks that previously ran only on screen now run on every write path, so a record created through the API, a Flow, Data Loader or an assistant is validated exactly as if a person had entered it in Precursive. Each action also runs strictly under the user's own permissions, so an operation succeeds only if that user has the field access it needs - the same access they would need on screen.

Most customers will see no change. Precursive's own permission sets are updated automatically when you upgrade to 2.25, so users on our standard permission sets continue to work as before. If you use cloned or custom permission sets, review the Enablement Guidance table below to see which field access to add.

How It Works

• The checks are enforced in Precursive's core logic, so they apply to the user interface, the API, Flows, Data Loader and MCP alike. The user interface behaves as before; the difference is that other routes now apply the same checks.
• Bookings are sized and checked for overlaps and employment dates on every write, and availability is kept up to date.
• Timesheets follow their normal flow everywhere: a Timesheet moves to Submitted only from Planned, so a Rejected or Approved Timesheet is recalled first.
• If an action is missing a required field permission, or breaks a rule, it is refused with a clear error and nothing is saved.

Your own configuration applies the same way. Custom validation rules run on every route, including the API and an AI assistant. A field made required only on a page layout is not enforced on these routes, so use a validation rule when a field must always be set.

Enablement Guidance

Users on Precursive's packaged permission sets need no action - the required field access is added automatically on upgrade.

If you use custom or cloned permission sets, grant the field access below to the sets that perform each operation, before or shortly after you upgrade. Without it, those operations will fail for the affected users after the upgrade. Each field already has Read Access unless the table says otherwise. You only need to add Edit Access. Granting field access is a Salesforce administration task - see Salesforce's documentation on editing field permissions in a permission set.

Operation	Precursive permission set that performs it	Field access added
Log time outside a Booking, copy planned hours to actual, copy the first day's hours across the week, copy last week's lines, add a row	Core Platform Standard User and Individual Contributor	Edit on the Timesheet Entry object (preempt__TimesheetEntry__c) fields: Timesheet (preempt__timesheet__c) Phase (preempt__phase__c) Resource (preempt__resource__c) Date (preempt__date__c) Task Category (preempt__activityCategory__c) Contributor (preempt__contributor__c)
Submit or recall a Timesheet	Core Platform Standard User and Individual Contributor	Edit on the Timesheet object (preempt__Timesheet__c) field: Status (preempt__Status__c)
Fulfil a Resource Request that sets Use Costs From Resource, from the Resource Plan or through the API and MCP	Resource Management. This remains a Resource Management capability; the Core Platform sets do not receive it.	Read and Edit on the Participant object (preempt__Participant__c) field: Use Costs From Resource (preempt__useCostsFromResource__c) Cost and rate fields are not opened.
Set Baseline, from the quick action or the Gantt	Project Management Standard User and Super User	Edit on the Phase object (preempt__Phase__c) field: Baseline Set Date (preempt__baselineSetDate__c)
Save related templates in the Template Builder	Project Management Super User. Standard Users retain Read-only access and cannot edit templates.	Read and Edit on the Template object (preempt__Template__c) field: Related Templates (preempt__relatedTemplates__c)

What Else Changed

• Kanban cards can now be reordered within a list by drag and drop, and the new order is saved and preserved after reload.
• The Task Planner now shows a loading indicator on first load instead of a premature "No data" message.
• Task Planner rows now expand to fit their content, so Participant roles, Phase names and Project names are no longer truncated.
• In the Task Planner, dragging a task into a Contributor's available dates is now allowed immediately, without a full page refresh.
• A Standard User who owns a Phase can now remove a task template from it without an access error.
• Activating, deactivating or deleting a Contributor via a Customer or Partner Workspace now rebuilds the Timesheet structure correctly, matching Standard User behaviour.

Data Model

New Fields: None.

Deprecated Fields: None.

Updated Fields:

Object	Field Label	API Name	Change
User	Precursive License Type Actual	preempt__precursiveLicenseTypeActual__c	Picklist is no longer restricted, so new license type values are saved automatically and the manual upgrade step of adding missing picklist values is no longer required.