Page4U - Landing Page Deployment

Created By
Page4U4 months ago
Deploy landing pages, manage leads, and view analytics from any AI assistant. Works with Claude Code, Claude Desktop, and Cursor.
Overview

Page4U MCP Server

Let AI assistants deploy and manage landing pages with built-in lead tracking.

Available Tools

ToolDescription
list_pagesList all your landing pages
get_pageGet detailed info about a page
deploy_pageDeploy HTML as a live landing page
update_pageUpdate page metadata (name, contact, colors)
delete_pagePermanently delete a page
get_leadsView leads from contact forms
get_analyticsView page analytics (views, clicks, submissions)

Setup

  1. Get your API key at page4u.ai/dashboard/settings
  2. Install: npm install -g page4u-mcp

Example Prompts

  • "Deploy this HTML as a landing page called my-bakery"
  • "Show me leads for my-bakery"
  • "What are the analytics for my-bakery this month?"
  • "Create a landing page for a pizza restaurant with WhatsApp ordering"

Server Config

{
  "mcpServers": {
    "page4u": {
      "command": "page4u-mcp",
      "env": {
        "PAGE4U_API_KEY": "your_key"
      }
    }
  }
}
Project Info
Created At
4 months ago
Updated At
4 months ago
Author Name
Page4U
Star
-
Language
-
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago