Server providing Argo CD integration for MCP clients.
aft.page is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Deploy HTML or dist/ to a live HTTPS URL. No account. Drop, MCP, or CLI.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http aft-page-mcp https://mcp.aft.page/mcp
# 2 — ask your agent for something these tools do
# deploy, deploy_repo, aft_deploys and 3 more
aft.page costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http aft-page-mcp https://mcp.aft.page/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Publish to a live URL. Pass html (one page) OR files (built site). Plain HTML → html. Vite/React → npm run build, then files from dist/. Next static export → files from out/. Always include index.html. Never upload src/, node_modules, or .next/. First hit: preferred_slug from aft.json (include aft.json in files). Later: same slug + edit_token from .aft/state.json — every update is a new version (v
| Parameter | Type | Required | Notes |
|---|---|---|---|
| html | string | no | One HTML document. Ignored if files is set. |
| files | array | no | — |
| preferred_slug | string | no | aft.json slug. Required with edit_token. |
| edit_token | string | no | From first deploy / .aft/state.json. Required to update or rollback the same URL. |
| expires | string | no | Optional quick-view expiry, e.g. "1h", "24h", "90s", "7d". Anonymous (unclaimed) deploys only — the link 404s after this. |
| hold | boolean | no | Update only: build and verify but do not go live; promote later with aft_promote. |
| label | string | no | Short name for this version, e.g. 'before redesign'. |
Same engine as aft.page/run: public GitHub URL → detect → build → live URL. Static is instant; Vite and Next.js build in the background (polls until live or failed). Private repos are refused. For a local project dir, use hosted CLI aft deploy instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | GitHub URL or owner/repo, e.g. https://github.com/mdn/beginner-html-site |
List the versions (v1, v2…) of a slug with their label, door, commit and whether each is live or a held preview. Needs edit_token from .aft/state.json (or the first deploy). Same history the project UI shows after claim.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Site slug from aft.json or .aft/state.json |
| edit_token | string | yes | From first deploy / .aft/state.json. Required to update or rollback the same URL. |
Point the live slug at a prior version from aft_deploys, by version number or deploy_id. Same URL. Needs edit_token from .aft/state.json. Claim not required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Site slug from aft.json or .aft/state.json |
| edit_token | string | yes | From first deploy / .aft/state.json. Required to update or rollback the same URL. |
| deploy_id | string | no | deployId from aft_deploys |
| version | integer | no | Version number from aft_deploys, e.g. 3 for v3 |
Make a held preview version live at the same URL. Pass version (e.g. 4) or deploy_id from aft_deploys. Needs edit_token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Site slug from aft.json or .aft/state.json |
| edit_token | string | yes | From first deploy / .aft/state.json. Required to update or rollback the same URL. |
| deploy_id | string | no | deployId from aft_deploys |
| version | integer | no | Version number from aft_deploys, e.g. 3 for v3 |
Ping the aft.page deploy API.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install aft.page or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish aft.page can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.