Instapage MCP · Customer setup guide

Configure Instapage MCP

Generate an API key, choose exactly what your AI agent may access, and copy a ready-to-use configuration.

01 / 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 the account whose workspace access the agent should inherit.

Open the API key page

Go directly to the account settings page below and generate a personal API key.

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 account settings
The API key itself has no scopes It inherits all permissions of its creator. The permission settings in this guide limit which MCP tools the client exposes to the model; they do not reduce the key’s permissions outside MCP.
Recommended account choice Generate the key from an Instapage user whose workspace access already matches the intended business role. Then use the MCP permission level below as an additional client-side guardrail.
02 / PERMISSIONS

Choose connection and permission level

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

A. Connection method

B. Permission level

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

Copy your ready configuration

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

Remote · 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.
      

    


    

      

        04 / 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 for page JSON and HTTPS URLs for images; never inline credentials or large files.

      

    


    

      

        05 / TOOLS
        

          
Complete tool catalog

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

        

      


      

        
        
        
      

      
Showing 39 of 39 tools