MCP (Model Context Protocol) is the open standard that AI clients such as Claude Desktop, Cursor, and other MCP-compatible hosts use to connect to external tools. Instead of copying numbers out of Instapage into a chat window, you connect once, and your assistant queries the live account directly.
The Instapage MCP server lets an AI assistant work inside your Instapage account the same way you would: pulling analytics, reading lead submissions, checking experiment results, creating and publishing pages, and managing assets.
To access all the details and a step-by-step guide, check out our page: https://mcp.instapage.com/howto.
Key Highlights
Inherited Workspace Access: The MCP server uses your personal Instapage API key. The agent inherits the exact permissions and workspace visibility of the user who generated the key.
Granular Client-Side Guardrails: Even though your API key holds your full workspace access, you can use client-side permission settings to restrict your AI model to Read-Only or selective Write-Group permissions.
Stateless & Secure: The MCP server forwards your key directly to the Instapage Public API per request and does not store your credentials.
How To Set It Up
Create Your Instapage API Key:
Inherits user workspace permissions.
Sign in to your Instapage Account using the account whose workspace access your AI agent should inherit.
Navigate to My Account Admin, and under Account settings, you can find the Personal API Token section and generate a personal API key.
Copy and store the key securely in your MCP client’s secret storage or environment variables. Never expose this key in public repositories or raw prompts.
Select Your Connection & Permission Level:
Choose your connection method (Remote via mcp-remote or Local) and define the permission scope:
Read-Only (20/39 Tools): Exposes safe lookup tools to inspect assets, list workspaces, and review landing page structures (enables 13 standard use cases).
Write Groups / Full Access (Up to 39/39 Tools): Grants permission to create, update, publish, or delete assets across specified product groups.
Copy and Add Configuration to Your MCP Client:
Copy the generated JSON configuration snippet from the generator page.
Paste it into your MCP host configuration file (e.g.,
claude_desktop_config.json).Replace the API key placeholder with your secret key environment variable.
Restart or reconnect your MCP client host.
Verification & Testing
Once connected, verify your setup by running the following commands in your AI prompt window:
session_info— Validates your API key header and connection status.workspaces_list— Lists all Instapage workspaces accessible to your account.
What You Can Do With It
The server exposes 39 tools in total: 20 read-only and 19 that write. They cover these product areas:
| Group | What the agent can reach |
|---|---|
| Workspaces | Workspace list, session, and account context |
| Pages | Page inventory, page content and structure, creation, publishing, deletion |
| Analytics | Visits, conversions, conversion rate, performance over time |
| Leads | Form submissions and lead data (masked by default) |
| Experiments | A/B test setup and results |
| Assets | Images and uploaded files |
| Collections | Grouping and organization of pages |
| Domains | Connected domains and publishing destinations |
| Team | Members, roles, and access management |
| Folders | Page organization and folder changes |
The published guide documents 25 worked examples, each with a sample prompt and an indicator of whether it's available under the permission level you chose.
Use Cases
1. Landing Page CRO & Content Audits
Layout & Copy Review: Analyze headlines, CTA buttons, and overall page structure against CRO best practices.
A/B Experiments & Personalization: Inspect running A/B test variations and personalized page setups to see what content is being served to different audience segments.
Page JSON & Snapshot Inspection: Inspect technical page elements and mobile layout rules directly via snapshot IDs.
2. Campaign Launch & Page Management
Duplicate & Localize Pages: Clone existing winning landing pages to launch regional or localized versions fast.
Create & Edit Page Snapshots: Patch text copy, alter values, and save new page versions based on AI feedback.
Publishing & URL Control: Publish pages live, unpublish inactive campaigns, or update live public URLs on the fly.
3. Folders, Collections & Asset Workflows
Folder & Group Organization: Create, rename, or clean up page folders to keep workspaces structured.
Dynamic Collections: Inspect placeholder layouts and publish collection pages for scalable personalization.
Media Library Management: Upload image assets directly via HTTPS URLs and check available media folders.
4. Leads, Analytics & Workspace Administration
Form & Submission Audits: Inspect required form fields and review submission trends (with PII safely masked).
Performance Analytics: Fetch aggregate visitor, conversion, and lead counts over custom date ranges.
Team Access & Permissions: Invite new team members, edit access roles, or revoke workspace access.
Domain & Connection Health: Verify connected custom domains, test active SSL states, and check API token quotas.
Built-in Execution Safety
When using any of these actions, your team benefits from built-in safety controls:
Preview Before Publishing (
dryRun): Ask the AI to test updates or deletions indryRunMode first to preview changes before impacting live pages.Privacy Protections: Submissions and team details remain masked by default to safeguard sensitive user data.