Apple Adds AI Assistants to Pages, Keynote and Numbers

What Apple announced

According to Apple's newsroom, the company announced on 27 October 2026 that Keynote, Pages and Numbers will receive beta AI features in November. The headline feature is an intelligent assistant built on Apple models and OpenAI models. It reads the document that is open and works on it directly. In Keynote it helps design, animate and refine slides. In Pages it drafts, restructures and fine-tunes text. In Numbers it runs calculations, recommends chart types and builds custom tables.

The second change is quieter but more important for automation. Apple says the three apps now support the Model Context Protocol on macOS 27 or later. MCP is an open standard that lets an AI tool connect to another application through a defined set of actions. Apple describes the result as letting external AI agents read content, perform edits and execute automated actions in the apps.

The assistant went into beta on 22 October, according to release notes described in a third-party guide. Apple's own announcement covers the wider rollout in November.

Why it matters for businesses that automate work

Most automation in an office today ends at the document. A tool pulls numbers from a system, then a person pastes them into a Numbers sheet, formats a table, and copies the result into a Pages report or a Keynote deck. Each handover is a point where errors and delays creep in.

MCP support changes where that handover can happen. If an agent can open a Numbers file and update it, the same agent can refresh a monthly summary without a person re-keying figures. This is the kind of routine work that AiStaffo's AI workers are built to take over, such as data entry, reconciliations and report preparation. The point is not the assistant inside the app. It is the access that other tools gain to the file.

Access to the apps is also a control question. An agent that can edit a document can also change it wrongly. Any business that lets software touch financial or client documents needs a clear record of what changed and who approved it.

What changes in practice

The table below sets out what the announcement covers and what it means for an operations team. Requirements come from Apple's footnotes and the Creator Studio page.

For a small firm, the practical path is simple. Pick one recurring document, such as a weekly sales sheet or a client report template. Run the assistant on a copy and note how long the edit takes compared with the current method. If the output needs heavy correction, the feature is not yet saving time for that task.

For a larger organisation, the question is governance. Finance, HR and operations teams will need a decision on which agents may connect to which files, who approves changes, and where the audit trail is kept. Apple has not named the agents that will work with the feature.

Limits to plan around

The feature is in beta, the language support is narrow, and the MCP path needs a Mac on macOS 27. Apple has not published the list of actions that agents can perform, how a user grants permission to an agent, or how the assistant's requests are handled privacy-wise. Results from the assistant will also vary with the quality of the source file. Automation does not replace the person who checks a figure before it goes to a client or a regulator. That check stays with the business.

What to watch next

• Whether Apple publishes developer documentation for MCP, including the list of actions and the permission model.
• Which third-party AI agents announce support for Keynote, Pages and Numbers.
• Whether the assistant reaches languages beyond US English.
• When the beta moves out of beta, and whether the iOS 27 and iPadOS 27 versions gain MCP support.

A business that automates reports or billing documents should wait for the documentation before connecting any agent to live files. Testing on copies is the sensible first step in the meantime.