Instapage MCP API Keys

Instapage MCP · Customer setup guide

Connect Instapage to your AI

This server lets your AI list landing pages, read analytics, manage folders, and publish — in the Instapage account behind your API key. Pick the tool you already use; we fill in the rest.

1Pick your tool 2Create an API key 3Choose permissions 4Copy the configuration
01 / YOUR TOOL

Pick the tool you will connect

This is the only choice that changes how we set things up. Expand a tool to see what we will configure for you.

02 / API KEY

Create your Instapage API key

The MCP server uses your personal Instapage API key. It forwards the key to the Public API for each request and does not store it.

Sign in to Instapage

Use a user who already has the access the agent needs. An API key cannot exceed its creator’s permissions.

Open API Keys

In the Instapage dashboard, go to API Keys (Developers) using the link below.

Create an API key

Create a key and set a maximum role. Optionally restrict which workspaces the key can access and set an expiry. Copy the secret when shown — you may not see it again.

Copy and store the key securely

Save it in your MCP client’s secret storage or an environment variable. Do not commit it to a repository or paste it into prompts.

Open Instapage API Keys
API key scoping Each key is limited by its maximum role, allowed workspaces, and expiry (when set). Those limits apply everywhere the key is used, including direct Public API calls outside MCP.
MCP permissions in this guide The permission settings in the next section are a client-side guardrail only. They limit which MCP tools your host exposes to the model; they do not expand a scoped key, and they do not reduce what the key can do outside MCP.
Recommended account choice Create the key from a user who already has the least access the agent needs. Prefer the lowest maximum role, the fewest workspaces, and an expiry when you can. Then use the MCP permission level below as an additional client-side guardrail.
03 / PERMISSIONS

Choose what the agent may access

These selections define the configuration generated in the next section. Nothing is sent anywhere; the generator runs entirely in this HTML file.

Permission level

Policy precedence: Exact tools→Write groups→Read / all tools
04 / CONFIG

Copy your ready configuration

The output below is generated from your tool and permission choices. Replace the API-key placeholder through your client’s secret mechanism.

Cursor · Read only 

        

        
      


      

        Header validation
        Names are case-sensitive. Lists are comma-separated. Literal * is accepted only as the whole value; regex such as .* is invalid. Empty or unknown values make the hosted server return HTTP 400; mcp-remote surfaces that as a bridge connection error.
      

    


    

      

        05 / EXAMPLES
        

          
Examples

          
These 25 examples are possible with the current Instapage Public API. Each one shows a sample prompt and whether it is available under your configuration.

        

      

      


      

        
Confirm side effects
Confirm public or destructive actions. Use dryRun: true where available.

        
Rate limits
200 requests per minute plus plan quota. Do not fetch list pages in parallel.

        
PII
Team data and submissions are masked by default. Unmask only with user consent.

        
Large payloads
Use snapshot IDs, upload links, or inline JSON for page JSON, and HTTPS URLs for images; never inline credentials or large files.

      

    


    

      

        06 / TOOLS
        

          
Complete tool catalog

          
All 46 Instapage MCP tools, their access classification, product group, and customer-facing purpose.

        

      


      

        
        
        
      

      
Showing 46 of 46 tools