MCP.Market

Pages Native MCP server

by viames·io.github.viames/pages-native·v0.5.0·2 stars

Native Apple Pages: guarded edits, templates, batches, recipe history and PDF previews.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

2 stars

Reviews

Write one

Nobody has reviewed Pages Native yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Pages Native tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 7 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Pages Native compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
GitHub stars
2
more than 75% of 28,688 servers

Install Pages Native in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Pages Native repository's README, as published. We do not edit it. Read it on GitHub

Pages Native

Native Apple Pages documents for Codex and MCP. Author: Viames Marino · MIT.

Version 0.5.0. Native acceptance passed 76 checks on one Mac with Pages 14.5 and macOS 27.0.1; 70 portable tests passed separately. Other Pages/macOS configurations remain unverified. See verification.

Pages Native uses Apple's scripting API through fixed JXA and AppleScript workers. Documents remain .pages: no Word conversion, private-format parser, clipboard driver, Accessibility or UI automation.

Capabilities

36 MCP tools cover native documents and templates, rich text, existing tagged placeholders, tables with formulas, text/shape/image objects, existing object geometry, explicit native exports, opaque backups and PDF/PNG previews. Existing-text edits, placeholder fills, text/cell formatting, table/cell changes, sorting, merging, dimensions, objects and facing-page changes have preview/apply revision guards. Migration from 0.1: mutation tools now default to preview. Apply the identical request with mode:"apply" and its expected_revision; a successful preview is not a completed edit.

New in 0.5: previewed batches of up to 10 native outputs, immutable recipe history with saved prototype snapshots, structural comparisons, historical reuse and guarded restoration. Batch and history guide.

New in 0.4: typed table fields in composed models and a local reusable recipe library with relative prototype paths, saved-byte fingerprints, version counters and guarded save/delete/use. See typed fields and recipes.

New in 0.3: structured literal search with native text/cell references, and guided composition from saved prototypes with required/default fields and revision-guarded new copies. See search and model recipes.

Mutations may partially apply; there is no automatic rollback. Pages 14.5 exposes placeholder tags for reading but rejects changing them through its scripting API.

The synthetic example shows a native table total of 265 EUR and a separately positioned text item.

The native API does not expose complete paragraph styles, headings/lists, comments, tracked changes, hyperlinks, headers/footers, page setup or chart series/type/title. Features already present in a saved prototype can be preserved through opaque native copies. Creating and editing chart data is not claimed. Font/size/color formatting does not assign named paragraph styles; semantic style preservation during model filling is not yet certified.

Requirements and installation

  • macOS with an interactive, logged-in session and Apple Pages.
  • Node.js 22 or later and Automation permission for the actual host controlling Pages.
  • Local execution. This cannot run against the user's Mac from a cloud-only task.

Install the public Codex plugin marketplace and enable Pages Native:

codex plugin marketplace add viames/pages-native
codex plugin add pages-native@viames-pages

Start a new local Codex task and run the setup skill. A compatible MCP host can run node /absolute/path/to/plugins/pages-native/dist/server.mjs; runtime npm installation is unnecessary after build.

Optional PAGESNATIVEALLOWED_ROOTS is a JSON array of existing directories. It guards plugin file paths; it is not a macOS sandbox for the Pages process.

Development

npm ci
npm test
npm run build
npm run test:bundle
npm run test:native
npm run package

Portable tests validate protocol, bounds, path restrictions, revision planning and timeout recovery. test:native controls Pages on an explicitly designated Mac using isolated synthetic documents; ordinary CI does not certify a graphical Pages installation.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Pages Native: common questions

Is Pages Native MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Pages Native safety report
Does Pages Native need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Pages Native maintained?
The last commit was 15 days ago (2026-10-20). The latest release is v0.5.0.
How does Pages Native compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); github stars 2 (more than 75% of 28,688 servers). Full comparison.