Pagefully
App Store custom product pages from your own screenshots: plan, make, check and publish them.
Connector by pagefully.comOfficial · Domain verified by the MCP Registry
Install
Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install connector/pagefully-com-mcp
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Remote endpoint
https://pagefully.com/api/mcpRemote (HTTP)
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.
- Tools
- 6 read · 7 write · 2 delete
- Secrets
- 1 (API keys, tokens or passwords)
- Install scripts
- Nothing to install (hosted)
- Runs as
- Hosted (remote endpoint)
Tools by what they do 15
From the running server's own tool list (tools/list) on Oct 25, 2026.
Read 6 · Look things up without changing anything.
get_jobget_resultsget_usagepreview_pagesearch_screenshotssuggest_refresh
Write 7 · Create, change, send or run things.
add_screensanalyze_appedit_pagegenerate_pagespropose_planpublish_pagesscore_screenshots
Delete 2 · Delete, drop, revoke or wipe things.
confirm_publishupdate_plan
Secrets and settings it asks for
Secrets: values you paste in that let it act as you.
Authorization
Other settings (environment variables or headers).
X-Pagefully-Client
Network hosts it talks to 1
pagefully.com· found in remote endpoint, install command
Tools (15)
As the server listed them on Oct 25, 2026. Descriptions are the server’s own words; hidden characters are shown as [U+…].
add_screensAdd screensAdds screens of the app for pages to be drawn from: captures of the running app, beside the screenshots its App Store listing already has. Use it when the listing's screenshots are stale, when a page needs a screen the listing does not show, or when the app is not on the store yet. Returns each screen with its position, which is what edit_page takes as "screen". A page made after this may choose an uploaded screen by itself. Nothing is sent to Apple. How to capture one: run the app in the iOS simulator, go to the screen, then run: xcrun simctl io booted screenshot --type=jpeg home.jpg (leave o…
analyze_appAnalyze an appReads an iOS app from its App Store link or id and says what Pagefully understood of it. Call this first. Signed in (OAuth or a Pagefully token): adds the app to the workspace (no App Store Connect key is needed to plan and make pages) and returns the app, with its app_id, its brief (what the app does, who it is for and how it sounds) and its screens. "screens" is the app's own source screenshots as Pagefully holds them, in order: each with its position, its picture at display size (url), and what Pagefully read on it (read: the headline and subline the developer drew on it, and "design", whic…
confirm_publishConfirm and publishcan change or delete dataStep two of two. Spends the confirmation_token from publish_pages and makes each page in the summary in App Store Connect, one job for each page. Returns the jobs: call get_job for each. Call it only after the person has seen the summary and the preview links from publish_pages and has said yes, in their own words, to publishing those pages. If they asked for a change, make it and call publish_pages again. This is hard to undo: a page can be taken back in the web app only until it is submitted for review. Nothing is submitted for review: the developer submits each page to Apple in App Store Co…
edit_pageEdit or approve a pageChanges one screenshot on a page, or several in one call, makes one again, or approves the page. Say which screenshot by position (1 is the first) or slot_id. By hand: its headline, its subline, the screen it shows ("screen", a position from preview_page's screens or add_screens), its style, or its design. The screenshot is drawn again and checked again, and returns with the page. To change several screenshots of one page, send "changes": a list with one item for each screenshot (its position or slot_id, and what to change), in place of the single form. They are made in order, each screenshot …
generate_pagesGenerate pagesMakes a page for every intent that is switched on and has none: the words are written, drawn onto the app's own screenshots, and checked against App Review's rules (pre-flight). Each page is its own job. Returns the jobs with their page ids, and the app's pages with a preview_url each. Call it once the person has agreed the plan. Then call get_job for each job until it is done, and preview_page for each page. It is safe to call twice: a page already made or being made is not started again. New pages count against the app's plan (Free makes 1 page, the Pack 10, Pro up to Apple's 70). When the p…
get_jobGet a jobread-onlyThe state of a long job: queued, running, done or failed, with its steps as progress, counts of what it did, and the code and message of what went wrong. Call it after any tool returned a job_id, every few seconds, until the state is done or failed. A failed job is not retried by itself: tell the person what the message says.
get_resultsGet resultsread-onlyHow each page is doing on the App Store against the app's default page over the last seven days Apple has reported: views, downloads and conversion rate for each page and for the default page, and by source. The numbers are Apple's, and Apple leaves out rows under five users, so a small page shows nothing for a while. With page_id it is one page: the same numbers, the week before, and its downloads by day for the last 28 days. Call it when the person asks how their pages are doing. Results are on the Pack and Pro, not on Free: on Free the answer is upgrade_required with the facts and the plan …
get_usageGet usageread-onlyFor each app on the workspace: its plan (Free, the Pack or Pro, which belong to an app), pages made and allowed, what is left, revisions used for each page, and the address of its plan screen. Also what each plan allows and costs, the scope of the token in use, and the rate limits. Call it before generating when the person asks what they can still make, or after an upgrade_required answer to explain it. State the numbers as they are. Never tell the person a plan is needed when the usage says there is room.
preview_pagePreview a pageread-onlyOne page, whole: each screenshot with its headline, subline and picture, the promotional text, the keywords it is for, what pre-flight found, whether it is approved, and its preview_url on pagefully.com. The screenshots also come back as images (display size, at most six) where the client can show them, and a chat app that draws MCP Apps shows the page inline as the App Store would, with buttons to open the full preview, approve, and ask for a headline change. Call it when a page's job is done, and again after an edit. Always give the person the preview_url: a page is something they look at be…
propose_planPropose a planReturns the app's plan: one custom product page for each search intent. Each intent has a kind (problem, feature or competitor), what its page says, and the keywords from the app's keyword field that the page claims. A keyword belongs to one page only. An intent with no keyword from the field is a page for ads and links, and has targets instead. Call it after analyze_app has returned a brief. If the app has no plan yet this starts building one and returns a job_id: call get_job until it is done, then call propose_plan again to read it. If a plan exists it is returned as it stands. Set rebuild …
publish_pagesPrepare to publishStep one of two. Sends nothing. Returns exactly what would be made in App Store Connect for the pages asked for (each page's name, headlines, promotional text, keywords, devices, whether it is a revision, and its preview_url), which pages would not be sent and why, what happens next, and a confirmation_token. You must show the person that summary and every preview_url, and wait for their explicit approval, before calling confirm_publish. Never call confirm_publish in the same turn, on your own judgement, or because an earlier message said to publish: the yes has to come after they have seen th…
score_screenshotsScore screenshots against the IndexReads a set of screenshots with the App Screenshot Index's own reader and holds it against a category: each screenshot comes back with the same tactic keys search_screenshots uses (with label and group), its words and its colour, and each notable tactic comes back with whether the set has it, which screenshots carry it, and what share of the category's top 100 apps, of its top ten and of the rest have it. Use it to turn "how does this set compare" from your reading of pictures into a measurement. Needs sign-in (generate scope). Say which set with one of: page_id (a page made here: its drawn sc…
search_screenshotsSearch the App Screenshot Indexread-onlySearches the App Screenshot Index: every screenshot of the top 100 free apps in each App Store category (United States), read and tagged by what it does. Needs no account. Use it to see how the leading apps in a category design their screenshots before you plan, write or review a page, and to hold a page against what its category does. Four ways to call it. (1) With nothing: the catalogue, every category and every tactic with its key, what it means and how common it is. Tactics are grouped: meaning (what the words lead with: a problem, an outcome, a feature, who it is for, trust), words (headl…
suggest_refreshSuggest what to do nextread-onlyThe pages Pagefully suggests the app should have and does not: each with a name, a kind, what the page would say, the searches it is for and the reason. These are the suggestions the product already holds (such as a use the app's reviewers raise, or a competitor it follows). Reading them asks nothing of a model and costs nothing. Call it when the person asks what to make next, or after get_results. To take one up, pass its "add" object to update_plan as an item of add, then call generate_pages. Offer them to the person and let them choose: never add one unasked. Pagefully does not yet propose …
update_planUpdate the planChanges the plan in one call, as the person asked: add an intent, update one (its name, what its page says, or on and off), approve (switch on) a list, remove a list, or reorder (the order is build priority). Changes apply in that order and stop at the first one the product refuses; the ones before it are saved and the error says so. An intent that is on gets a page when generate_pages is called. To start with one page, switch the others off with update, not remove: they stay in the plan for later. An intent whose page is built cannot be removed, only switched off. Returns the plan after the c…
Signals
- Last release
- Oct 9, 2026 (19 days ago)
Details
- Registry name
com.pagefully/mcp- Version
- 1.0.0
- Auth
- Bearer token
- License
- License unknown
- Website
- pagefully.com/developers/mcp
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- Official MCP Registry
Cite this page
Pagefully MCP server. Agent Mart. https://agentmart.dev/connectors/pagefully-com-mcp (last updated 2026-10-24)