Your coding agent can make your App Store pages.

Try it without an account

Add the server and ask your agent to analyze any app on the App Store. You get the pages we would plan for it and the first one designed, with a link to look at it. Nobody is asked to sign in for that.

claude mcp add --transport http pagefully https://pagefully.com/api/mcp

Claude Code

One command in your terminal, and no token to copy:

claude mcp add --transport http pagefully https://pagefully.com/api/mcp

Start Claude Code and ask for what you want:

Make a custom product page for my app with Pagefully:
https://apps.apple.com/us/app/your-app/id1234567890

Sign in when asked. The first time your agent needs your account, Claude Code says the server needs you to sign in: run /mcp, choose pagefully, and your browser opens Pagefully. You see which app is asking, for which workspace and to do what, and you approve or deny. No account yet? Sign up free on the way.

The server also brings two prompts, first-page and refresh, which Claude Code offers as slash commands.

Cursor

Put this in .cursor/mcp.json in your project, or in ~/.cursor/mcp.json for every project. Cursor opens your browser to sign in when the server asks:

{
  "mcpServers": {
    "pagefully": {
      "url": "https://pagefully.com/api/mcp"
    }
  }
}

What you approve when you sign in

• Read and generate is what your agent asks for first. It can look at your apps, plans, pages and results, add your app, make pages, and edit and approve them. It cannot publish.
• Read, generate and publish is asked for only when your agent first tries to publish, on its own screen, and never approved for you.

Signing in lasts as long as you keep using it, and each app you approved is listed in Settings under Connected apps. Disconnect one there and it is signed out at once.

A token, for CI and scripts

Where nobody is there to sign in, use a token. Sign up free, open Settings and make one under API tokens. In Claude Code:

claude mcp add --transport http pagefully https://pagefully.com/api/mcp \
  --header "Authorization: Bearer <token>"

In Cursor, with the token in your environment as PAGEFULLY_TOKEN:

{
  "mcpServers": {
    "pagefully": {
      "url": "https://pagefully.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PAGEFULLY_TOKEN}"
      }
    }
  }
}

Any other client

The server speaks Streamable HTTP at one address. A client that follows the MCP authorization specification needs only the address: it finds out how to sign you in by itself. A client that does not takes a token as a bearer header, in a file shaped like this:

{
  "mcpServers": {
    "pagefully": {
      "type": "http",
      "url": "https://pagefully.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

Which token to make

A token is one of three kinds, the same three you can approve when you sign in:

• Read lets your agent look: apps, plans, pages, results and usage.
• Generate also lets it add your app, plan, make pages, edit and approve them. It cannot publish.
• Full also lets it send approved pages to App Store Connect, in two steps.

With a generate token your agent does everything up to publishing, and you publish from the web app. Revoke a token in Settings and it stops working at once.

What your agent can do

It can also read three things for context: your app’s brief, its current plan, and the Pagefully playbook, which tells an agent how to choose pages, what Apple allows, and to check every preview with you.

Every page comes back with a link to its preview on pagefully.com, and the screenshots themselves where your client shows pictures. In a chat app that shows MCP Apps (Claude on the web and desktop is one), the page also appears in the conversation as the App Store would show it, and a coding agent in a terminal shows the link and the pictures. A page is something you look at before you say yes.

Publishing takes two steps, and the second one is yours

A page sent to App Store Connect is slow to take back, so no single tool does it.

1. publish_pages sends nothing. It answers with exactly what would be made in App Store Connect, each page’s preview link, and a confirmation token.
2. Your agent shows you that summary and waits. The tool tells it to, in so many words.
3. confirm_publish spends the token after your yes. It lasts 10 minutes and works once.

Only a full token, or an app you approved to publish, can publish at all. A page is in the summary only if you approved it and its checks have no failure, and a page changed after the summary cancels the whole confirmation. A page is made in App Store Connect and is not submitted for review: that click stays yours. We never touch your default page, your keyword field, your app binary, your pricing or your in-app purchases.

Plans

The same plans as the web app, and the same count: Free makes 1 page for an app, the Pack ($49 once) makes 10, and Pro goes up to Apple’s 70. The MCP server is on all three and no call is charged for. When a plan stops something, your agent is told the numbers and given the link to your plan screen, and it tells you. See plans.

More

The same work over plain HTTP is the Pagefully API. Your agent can add screens it captures from the simulator with add_screens. Something missing that you need: hello@pagefully.com.