Instapage Model Context Protocol (MCP) Server

Table of contents

• Key highlights
• What you need to use the Instapage MCP server
• How to set up the Instapage MCP server

  • Setup overview
  • Step 1: Create an Instapage API key
  • Step 2: Choose your AI app and permission level
  • Step 3: Add the configuration to your AI app
• How to check that the connection works
• What the Instapage MCP server can do

  • Tool groups
  • Use cases with example prompts
• Built-in safety controls
• Tasks that are still done in the Instapage app
• How to send feedback about the MCP server

Article details

Written by IuliaUpdated November 9, 2026

The Instapage MCP server connects AI assistants such as ChatGPT, Claude, Cursor, VS Code, and Windsurf to your Instapage account. MCP (Model Context Protocol) is the open standard that AI apps use to connect to external tools. Instead of copying numbers out of Instapage into a chat window, you connect the AI assistant once, and the assistant works with your live Instapage account directly.

The Instapage MCP server lets an AI assistant work inside your Instapage account the same way you would: building complete pages from a brief or a design, pulling analytics, reading lead submissions, checking experiment results, creating and publishing pages, and managing assets. It can also organize folders and collections, manage lead notifications, and handle team access.

You ask in plain language, for example, “Which of my pages converted best last month?” or “Duplicate the Spring Sale page as Summer Sale,” and the assistant picks the right Instapage tools for the job. Your API key and the permissions you choose decide what it’s allowed to do.

For setup steps for every supported AI app, the full tool catalog, and more examples, see the Instapage MCP setup page: https://mcp.instapage.com/howto.

This article is for Instapage users who want to connect an AI assistant to their Instapage account. The article explains what the Instapage MCP server does, how to set it up, how to check the connection, which tasks the MCP server supports, and which safety controls apply. The step-by-step setup instructions for each AI app are on the Instapage MCP setup page, which is linked below.

Key highlights

• Inherited Workspace Access: The MCP server uses an Instapage API key that you create. The assistant can never do more than the user who created the key, and you can limit the key to specific workspaces, a lower role, and an expiration date.

• Granular Client-Side Guardrails: On top of the key’s limits, you choose which tools the assistant can see: read-only, all tools, selected write groups, or an exact list of tools. These settings can only narrow what the key allows; they never extend it.

• Stateless & Secure: The MCP server forwards your key directly to the Instapage Public API per request and does not store your credentials.

• Works With Your AI App: ChatGPT, Claude, Cursor, VS Code, Windsurf, and other MCP clients connect to the same hosted server, so your team can keep the AI tools it already uses.

• Safe by Default: Deletions and other risky changes show a preview first, and personal data stays masked until the assistant checks with you.

What you need to use the Instapage MCP server

• An Instapage account with API access. What the assistant can do follows your role and plan, and your plan sets the API quota. Owners and Managers can publish; Editors can build and save pages but not publish. Team members need Developer Access, which only the account owner can turn on.

• An AI app that supports MCP, such as ChatGPT, Claude (desktop app or Claude Code), Cursor, VS Code, or Windsurf.

How to set up the Instapage MCP server

Setup works the same way in every AI app: create an API key, generate a configuration on the setup page, and add it to your app. The example below uses Claude; the setup page shows the steps for the other apps.

Step 1: Create an Instapage API key

The Instapage MCP server uses an Instapage API key. The API key inherits the workspace permissions of the Instapage user who creates it, so the AI assistant can never do more than that user.

1. Sign in to your Instapage Account using the account whose workspace access your AI agent should inherit.

2. Go to API Keys in your Dashboard or My Account Admin → Developers & API → API Keys and click CREATE API KEY.

3. In Key name, enter a unique name between 3 and 36 characters.

4. In Allowed workspace(s), choose what the key can access:

   • All workspaces (default): all your current workspaces, plus any you create or join later.

   • Specific workspaces: use the search field to find workspaces, or click Select all to pick every workspace on the list right now. Workspaces other people share with you appear under Shared with me.

5. In Maximum permitted role, choose Inherited, Manager, Editor, or Viewer.

6. In Expiration, choose 7 days, 30 days, 90 days, Never, or Custom…. If you choose Custom…, click the date field, pick a day, and click APPLY.

7. Click CREATE.

8. The API key generated window shows your key. Click COPY, save the key somewhere secure, then click CLOSE.

All the details about the API Keys and how they work can be found in our article here: Control access with Public API Keys.

Step 2: Choose your AI app and permission level

Open the Instapage MCP setup page, pick the AI app you use, and choose what the assistant can access:

• Read only (safest default): the assistant can look at workspaces, pages, analytics, leads, assets, collections, domains, experiments, and team data, but can’t change anything.

• All tools: every read and write tool, including publishing, deletion, page creation, image uploads, folder changes, and team access management.

• Selected write groups: all read tools, plus write tools only from the product groups you pick.

• Exact tool list (advanced): only the tools you select, read or write.

The setup page shows how many tools and example use cases each choice unlocks.

Step 3: Add the configuration to your AI app

1. Copy the configuration that the setup page generates for your app and permission level.

2. Add it to your AI app, following the Where to put it steps on the setup page.

3. Replace the API key placeholder with your key, using your app’s secret or environment settings. Never paste the key into a chat.

4. Restart or reconnect your AI app.

Example: Connect the Claude desktop app

1. On the setup page, pick Claude and your permission level, then click Copy configuration.

2. In Claude, open Settings → Developer → Edit Config. This opens the file claude_desktop_config.json.

3. Paste the instapage entry inside "mcpServers", next to any servers you already have, and replace <YOUR_INSTAPAGE_API_KEY> with your key.

4. Save the file and restart Claude. The configuration runs mcp-remote with npx, so Node.js must be installed on your computer.

5. In a new chat, ask: “Which Instapage workspaces can you see?”

Claude Code uses the same entry in .mcp.json in your project folder, or you can add it with the claude mcp add command.

For ChatGPT (custom MCP connector), Cursor, VS Code, Windsurf, and other MCP clients, pick your app on the setup page and follow the steps it shows. Apps that connect to remote servers directly use the server URL https://mcp.instapage.com with two headers: your key and the permission level.

How to check that the connection works

After you connect, ask the AI assistant to check the connection, for example: “Check my Instapage connection and list the workspaces you can see.” The assistant runs these two tools:

• session_info — Validates your API key header and connection status. It also shows your API usage against your plan’s limit.

• workspaces_list — Lists all Instapage workspaces accessible to your account.

If the Instapage tools don’t appear, restart or reconnect the app. Header names are case-sensitive, and an empty or unknown value returns an HTTP 400 error.

What the Instapage MCP server can do

The server currently exposes 46 tools in total: 22 read-only and 24 that make changes. They cover these product areas:

The setup page documents 26 worked examples, each with a sample prompt and an indicator of whether it’s available under the permission level you chose.

Use cases with example prompts

Here are common ways teams use the MCP, each with a prompt you can try. The assistant finds the pages and data it needs, and checks with you before anything public or destructive happens.

1. Build and import landing pages

• New Pages From a Brief: Describe the goal, audience, and offer. The assistant plans the page from your brand documents, shows you the plan, then builds a complete, editable page with native elements for desktop and mobile.

Try: “Build a registration page for our webinar ‘Scaling paid search in 2027’ using our brand guidelines. Show me the plan first.”

• Import a Design You Own: Rebuild a live URL, an HTML file, a Figma design, screenshots, or a PDF as an editable Instapage page.

Try: “Rebuild https://example.com/spring-offer in Instapage and stack the columns on mobile.”

For the full setup (instructions, the page-building guide, and your brand documents), see Build and import Instapage pages with your own AI assistant.

2. Landing page CRO and content audits

• Layout & Copy Review: Analyze headlines, CTA buttons, and overall page structure against CRO best practices.

Try: “Review the Spring Sale page against CRO best practices and list the five changes with the biggest expected impact.”

• 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.

Try: “Which experiments are running in the Acme workspace, and which variation converts best so far?”

• Page JSON & Snapshot Inspection: Inspect technical page elements and mobile layout rules directly via snapshot IDs.

Try: “List every form field and button link on the Spring Sale page.”

3. Campaign launch and page management

• Find Any Page: Search by name or URL across workspaces and get a fact sheet: status, live URL, type, and folder.

Try: “Give me a fact sheet for the page that’s live on promo.example.com/black-friday.”

• Duplicate & Localize Pages: Clone existing winning landing pages to launch regional or localized versions fast.

Try: “Duplicate Spring Sale as Summer Sale, translate the copy into Spanish, and save it in the Summer folder.”

• Create & Edit Page Snapshots: Change text or values and save the result as a new page, ready to review and publish. The original page stays as it is.

Try: “Make a version of Spring Sale with the headline ‘Save 40% this week’.”

• Publishing & URL Control: Publish pages live, unpublish inactive campaigns, or update live public URLs on the fly.

Try: “Publish Summer Sale to summer.example.com and take Spring Sale offline.”

4. Folders, collections, and asset workflows

• Folder & Group Organization: Create, rename, or clean up page folders to keep workspaces structured.

Try: “Move all Black Friday pages into a new folder called BF 2026.”

• Dynamic Collections: Add pages to a collection with their own text and images, publish them, and unpublish or remove them later, for scalable personalization.

Try: “Add Spring Sale and Summer Sale pages to the Retail collection, then publish them.”

• Media Library Management: Upload image assets directly via HTTPS URLs and check available media folders.

Try: “Upload https://cdn.example.com/hero-spring.jpg to the Campaigns image folder.”

5. Leads, analytics, and workspace administration

• Form & Submission Audits: Inspect required form fields and review submission trends (with PII safely masked).

Try: “Export last month’s form submissions from Spring Sale as a list I can hand to sales.”

• Performance Analytics: Fetch aggregate visitor, conversion, and lead counts over custom date ranges, by device, traffic source, or A/B variation.

Try: “Rank my pages by conversion rate for October, mobile traffic only.”

• Lead Notifications: See who receives lead emails for a page, add or remove recipients, and brand the emails with your sender name, reply-to address, subject, logo, and HTML.

Try: “Who gets lead emails for Spring Sale? Add sales@example.com.”

• Team Access & Permissions: Invite new team members, edit access roles, or revoke workspace access.

Try: “Invite dana@example.com to the Acme workspace as an editor.”

• Domain & Connection Health: Verify connected custom domains, check their SSL status, and check your API usage against your plan’s quota.

Try: “Are all our custom domains connected, with SSL applied?”

• Workspace Clean-up: Find draft pages that haven’t changed in months, and delete them after a preview of what will be removed.

Try: “Which draft pages in Acme haven’t been updated in the last six months?”

Built-in safety controls

When using any of these actions, your team benefits from built-in safety controls:

• Preview Before Changes (dryRun): Deleting pages, removing team members, changing lead notifications, and other risky changes return a preview first where available. Nothing changes until you confirm.

• Privacy Protections: Submissions and team details remain masked by default to safeguard sensitive user data. The assistant reveals them only after checking with you.

• Confirmation for Public Changes: Publishing, unpublishing, and URL changes affect live pages, so the assistant confirms them with you first. Many AI apps can also ask for your approval before each tool runs.

• Experiment Protection: A page with a running A/B test can’t be deleted, and its live URL can’t be changed, until you stop the test.

• Recoverable Deletions: A deleted page can be restored from the Instapage app within 3 days.

• Rate Limits: The server accepts up to 200 requests per minute, within your plan’s API quota.

Tasks that are still done in the Instapage app

The Instapage MCP server cannot do the following tasks. Do these tasks in the Instapage app:

• Page SEO and social settings (title, description, sharing image), and Show in search results.

• Creating and starting A/B tests and personalized experiences. The MCP can read them.

• Creating collections. The MCP adds, publishes, and removes pages in existing collections.

• Integrations, conversion goals, and connecting custom domains.

• Editing a saved page in place. The MCP saves changes as a new page, and the original stays as it is.

• Uploading image files from your computer. The MCP uploads images from public HTTPS links; other files go through the Image Manager.

How to send feedback about the MCP server

The AI assistant can send feedback about the MCP server directly to the Instapage team, for example when a tool is missing or doesn’t work as described. Ask the assistant to send feedback. The assistant shows you the note before sending it.