Pages, Numbers and Keynote: governing enterprise MCP agents

Created and analysed on 30 October 2026 · Source published on 27 October 2026: Apple Newsroom

Before entrusting a business document to an agent, IT teams should define what it may read, change and transmit. Underside proposes a qualification plan to prepare new office workflows on Mac, with decision criteria that can be verified.

1. The official starting point

On 27 October 2026, Apple announced MCP support in Pages, Numbers and Keynote for external agents to read, edit and automate actions. It requires macOS 27 or later. Creator Studio updates are planned for November. Separate built-in assistants are in beta, U.S. English only, requiring an Apple Intelligence-capable device on iOS 27, iPadOS 27 or macOS 27 or later.

Read the announcement and compatibility notes. For projects in Belgium or France, confirm local availability, languages and contractual terms before starting a pilot.

2. Set document boundaries before the pilot

We recommend starting with a fictional document and a limited task: formatting a memo, preparing a chart or making a slide deck consistent. Appoint a business owner and specify which parts of the document may be read or changed. Exclude customer data, HR information and trade secrets from this initial phase.

Create a record for each scenario

Record the application, its version, the macOS version, the selected agent, the model provider and the expected outcome. Ask the connector vendor to specify which data is transmitted, where it goes, how long it is retained and how it can be deleted. Have security review these answers and involve the data protection lead for any proposed processing of personal data.

3. Test permissions and control over changes

Run three separate tests: reading an authorised extract, modifying a copy and attempting an action outside the approved scope. For each, retain the request, the result and any confirmation prompts. Explicitly check what happens when the user refuses permission or interrupts the agent. These are acceptance criteria proposed by Underside; success must be demonstrated on the selected configuration.

Plan human approval and restoration

For a financial spreadsheet, check formulas, ranges and totals before and after the action. For a presentation, check figures, sources and speaker notes. Require human approval before any external distribution. Test restoring the reference copy and define who can suspend the experiment if a change cannot be explained.

4. Include the managed Apple fleet in testing

Prepare a pilot group of Macs in your Apple Business Manager and Jamf or other MDM environment. On these devices, check app distribution, sign-in to the expected account, network rules and security tools. Request precise documentation before relying on any prospective MDM control for MCP: an announced automation capability does not demonstrate an administrable setting.

Add a shutdown procedure to the record: remove agent access, revoke the relevant permissions and check behaviour after restarting. Our Apple deployment traceability guide complements the collection of evidence for each device.

5. What this changes for a Belgian or French business

For an SME, we recommend one pilot process and a business–IT pairing. Measure time saved, corrections required and supervision costs before expanding use. For mid-sized organisations, large enterprises or public bodies, propose a common matrix across Belgian, French and European sites, then have each owner approve language variations and permitted document categories.

For French-language workflows, require testing in French using the actual date formats, numbers and templates. Set a stop criterion if checking the output costs more than completing the original task. These recommendations establish neither regulatory compliance nor local feature availability.

6. Underside analysis: approve a specific task

Our approach is to approve a documented scenario with an identified dataset, agent and owner. We recommend broader rollout only when tests demonstrate control over access, output quality and restoration. The decision record should also identify which checks remain manual and who is responsible for carrying them out.

Underside recommendation: record the data boundaries, expected permissions, test evidence and shutdown procedure in one document. Underside, an Apple Business Partner, supports integration, MDM management and fleet security for Apple in Belgium and France.

Plan a Mac office workflow pilot

Source : Apple Newsroom — Apple Creator Studio (2026-10-27)