Marketing & Social Media · Hyperise + Claude
Hyperise MCP with Claude: Personalised Images, Pages and Videos at Scale
The short answer
Claude connects to Hyperise through the Model Context Protocol, an open standard that lets Claude securely use software with permissions you control. Once connected, Claude can request personalised images, update dynamic landing pages and generate custom videos, all guided by plain-language instructions from your team.
What is Hyperise?
Hyperise is a personalisation toolkit for sales and marketing teams. It adds dynamic, personalised elements to images, videos and websites, so each reader sees content tailored to them. Marketing teams, sales development teams and account managers use it to make outreach feel individual and to lift engagement across email, social media, websites and other channels.
How Claude connects to Hyperise through MCP
The Model Context Protocol, or MCP, is an open standard that acts as a universal adapter between Claude and other software. It lets Claude read information from a tool and take actions in it, using permissions your organisation sets. Hyperise can be connected to Claude through its MCP server or its direct API, using the API key sign-in method it supports.
Once connected, Claude can work with Hyperise in plain language. For example, a marketer can ask for a personalised image for each account on a list, ask for a landing page to be updated with a prospect's company name, or request a custom video for a campaign. Claude can prepare these requests and carry them out within the scope of the access you grant.
Permissions and approvals keep your team in charge. Access is limited to the actions you allow, typically through a key that can be restricted and revoked. Consequential steps, such as publishing a live page or sending a batch of personalised content, can be set to wait for a person to review and approve before they go ahead.
What you can automate
Personalised images for outbound campaigns
A sales development team uploads a list of target accounts. Claude asks Hyperise to generate a personalised image for each account, using the company name and logo. The team reviews a sample set, then approves the batch for use in email and social outreach. This typically saves hours of manual design work.
Dynamic landing pages for events
A marketing manager running a webinar series wants each registrant to see a landing page that greets them by name and company. Claude can update the dynamic page content in Hyperise from the registration list, keeping pages current as sign-ups arrive without a developer making each change.
Custom videos for account-based marketing
An account executive preparing for a key prospect asks for a short personalised video that mentions the prospect's business and recent news. Claude drafts the request and generates the video through Hyperise, which the executive reviews before sharing. This suits high-value accounts where a personal touch matters.
Campaign personalisation on demand
A marketing operations lead describes a campaign in plain language, such as tailoring a banner to each region. Claude translates that instruction into the right Hyperise requests, applies the variables, and reports back what was produced, so the team can adjust quickly without learning the tool's controls.
Refreshing personalised content
Campaign assets go stale over time. Claude can be asked to regenerate personalised images or pages with updated details on a set schedule, and flag any records with missing information so the team can fix them before content goes out.
An end-to-end workflow: Personalised account outreach from the CRM
TriggerA sales lead moves a company into the 'Ready for outreach' stage in the CRM.
Claude reads the account details, including company name, contact role and region, from the CRM.
Claude asks Hyperise to generate a personalised image and landing page link for that account.
The generated assets are placed in a draft outreach email in Microsoft 365 for the sales rep.
The sales rep reviews the email and personalised content and approves it.
Once approved, the email is sent and the CRM record is updated with the campaign activity.
OutcomeEach target account receives outreach that reflects its own name and context, while the sales rep keeps final control. Teams typically see faster preparation of outreach and more consistent personalisation across accounts.
How we set it up
Free automation audit
We review how your sales and marketing teams create personalised content today and identify the workflows worth automating with Hyperise and Claude.
Secure connection with API key
We connect Claude to Hyperise using its API key sign-in method, or its MCP server where appropriate. The key is stored securely and access is limited to the actions your workflow needs.
Workflow design
We design the end-to-end process across Hyperise and your other systems, such as your CRM, Microsoft 365 or ticketing tools, and agree which steps need human approval.
Testing and launch
We test the workflow against real past campaigns, then launch with monitoring and audit logs so every generated asset can be traced.
Team training
We train your marketers, sales staff and operations leads to make requests, review outputs and handle exceptions with confidence.
Who benefits
- Sales development leaders
- Personalised outreach at scale, with reviewed content for every account.
- Marketing managers
- Faster creation of personalised images, pages and videos without waiting on design or development.
- Marketing operations leads
- Campaign personalisation controlled in plain language, with clear logs of what was produced.
- Account executives
- Personal videos and pages for priority accounts, prepared quickly and reviewed before use.
Security and control
- Least-privilege access: Claude can only use the Hyperise actions your workflow requires.
- Human approval for publishing live pages and sending personalised content to prospects.
- Secure storage of the API key, with the ability to rotate or revoke it at any time.
- Audit logs that record requests made through Claude and the assets they produced.
- Data minimisation: only the fields needed for personalisation are passed to Hyperise.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host their Claude workflows in their chosen region to support their data handling requirements. Businesses in India must consider the Digital Personal Data Protection Act, 2023, when personal data is used for personalisation. Organisations in the UAE and Saudi Arabia must follow local data protection laws, and we select the hosting region to meet those requirements. Hosting is chosen with your compliance team before launch.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Hyperise MCP server do?
The Hyperise MCP server lets Claude and other AI agents use Hyperise in a structured way. Through it, Claude can request personalised images, update dynamic landing pages and generate custom videos, all within the permissions you set. It is an alternative to calling the direct API yourself, and we select the approach that suits your workflow.
Is connecting Hyperise to Claude secure?
Security depends on the setup. We connect using the API key method, store the key securely, limit access to the actions required, and keep audit logs of activity. Consequential actions such as publishing can require human approval. We design these controls before launch, and we do not guarantee outcomes for any specific environment.
What can Claude do with Hyperise?
Typically, Claude can create personalised images, update dynamic landing pages, generate custom videos and automate campaign personalisation from natural language instructions. Claude prepares and carries out these requests, and your team reviews the results where approval is needed.
How long does setup take?
Timelines vary with the number of workflows and systems involved. A focused integration with one workflow often takes a few weeks from the free audit to launch, including testing and team training. We confirm a realistic timeline during the audit.
What plan or permissions do I need?
You need an active Hyperise account with API access and an API key that the team can authorise for the workflow. Exact plan requirements depend on Hyperise's current terms, so we confirm what your account supports during the free automation audit.