Design & Creative Tools · OKZest + Claude
OKZest MCP with Claude: Personalised Design Automation at Scale
The short answer
Claude works with OKZest through the Model Context Protocol (MCP), an open standard that gives Claude secure, permission-controlled access to the platform. Once connected, Claude can inspect reusable designs, list design assets, validate component consistency and request personalised image renders using plain English instructions.
What is OKZest?
OKZest is a design automation platform. It inspects reusable designs and renders personalised images through a REST API, so teams can produce tailored visuals without opening a design tool for each one. It is typically used by marketing, creative operations and brand teams that manage large volumes of similar artwork, such as product images, campaign banners, certificates or social posts that vary by name, location or offer.
How Claude connects to OKZest through MCP
The Model Context Protocol is an open standard that lets Claude use other software securely. Think of it as a universal adapter between Claude and the tool. The organisation decides what Claude can see and do, and the connection can be switched off at any time.
Once OKZest is connected, Claude can read information from the platform. For example, it can list the design assets available, inspect how a reusable design is built, and check whether components follow the brand rules. Claude can also request personalised renders by supplying the data that should fill each template.
Permissions and approvals keep people in charge. Access uses an API key with least-privilege settings, so Claude only reaches the designs and actions the organisation allows. Consequential steps, such as publishing a batch of renders, can require a named person to approve before anything leaves the system.
What you can automate
Brand consistency audits
Claude can review the reusable designs in OKZest and check that fonts, colours, logo placement and component versions match the current brand guidelines. It produces a short report listing any components that have drifted, so the design team can fix them before they are used in campaigns.
Personalised product visuals
An e-commerce team can feed product names, prices and images into a template and ask Claude to render a set of tailored visuals for each market. Operations staff review a sample before the full batch is released, which saves hours of manual editing each week.
Event badges and certificates
Training and events teams often need hundreds of name badges or certificates with the right names, dates and session details. Claude can match attendee records to the approved template, request the renders, and flag any records with missing or malformed data.
Campaign asset inventory
Marketing managers can ask Claude which design assets are available for a particular campaign, which ones are outdated, and which have not been used recently. This helps teams reuse approved work instead of recreating it and keeps visual language consistent across channels.
Localised banners for regional offices
A head office can produce one master design and ask Claude to render versions with local language text, dates and offers for each regional team. Each version is checked for consistency before it is shared, which reduces the risk of costly mistakes in regional launches.
An end-to-end workflow: Monthly personalised offer banners
TriggerThe CRM marks a new monthly customer offer as approved by the commercial team.
Claude reads the approved offer details and customer segments from the CRM, such as Microsoft 365 spreadsheets or CRM exports.
Claude checks in OKZest that the current banner template uses the latest brand components and flags any issues.
Claude requests personalised banner renders in OKZest, filling each template with the customer's first name and the segment's offer.
A marketing manager reviews a random sample of renders and approves the batch in the workflow.
Claude logs the render run, saves the files to the shared asset folder, and notifies the campaign team in the ticketing system.
OutcomeTypically, the marketing team moves from days of manual design work to a same-day review cycle, with a documented audit trail of every batch sent out.
How we set it up
Free automation audit
We review your current design and content workflows with you at no cost. We identify the processes where personalised rendering or component checks would save the most time, and agree on the first workflow to automate.
Secure API key connection
We set up OKZest access using an API key stored in a secure vault, with least-privilege permissions. We connect it to Claude through an MCP server so that Claude can reach only the designs and actions you have approved.
Workflow design and approvals
We design the end-to-end workflow across OKZest and your other systems, such as Microsoft 365, your CRM or your ticketing tool. We set clear approval points so that a named person signs off before consequential actions, such as publishing renders.
Testing against real cases
We test the workflow using past campaigns, real customer data and sample templates. We compare outputs with what your team produced manually, correct any errors, and confirm that the rules for consistency and data quality work as expected.
Launch, monitoring and training
We launch with audit logs and monitoring, so every render and approval is recorded. We then train your design, marketing and operations staff to use the workflow and to handle exceptions, and we review performance with you after the first month.
Who benefits
- Marketing managers
- Launch personalised campaigns faster while keeping every visual on brand.
- Creative and design leads
- Spend less time on repetitive edits and more time on new design work.
- Operations and events teams
- Produce large volumes of badges, certificates or notices with fewer errors.
- IT and compliance heads
- Control access with API keys, least-privilege permissions and full audit logs.
Security and control
- Access uses an API key stored securely, with permissions limited to the designs and actions each workflow needs.
- Named people approve consequential actions, such as publishing batches of renders, before they leave your systems.
- Every render request, approval and output is recorded in audit logs that your team can review.
- Customer and personal data is only passed to OKZest where the workflow requires it, and is minimised wherever possible.
- The connection can be paused or revoked at any time by your IT team.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can use OKZest with Claude under their existing data protection frameworks, with hosting chosen to meet their requirements. Indian organisations are supported in line with the Digital Personal Data Protection Act, 2023. Businesses in the Middle East, including the UAE and Saudi Arabia, can align the setup with local data protection laws. In every region, the hosting location for Claude is selected to meet your specific compliance needs.
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 OKZest MCP server do?
The OKZest MCP server acts as a secure bridge between Claude and the OKZest platform. It allows Claude to list design assets, inspect reusable designs, validate component consistency and request personalised renders, using instructions written in plain English. The server only exposes the actions that your organisation has permitted.
Is connecting OKZest to Claude secure?
Security is built into the setup. Access uses an API key stored in a secure vault, with least-privilege permissions. Consequential actions can require human approval, and every request and output is recorded in an audit log. Your IT team can pause or revoke the connection at any time.
What can Claude do with OKZest once it is connected?
Typically, Claude can review reusable designs for brand consistency, list available assets, request personalised image renders from supplied data, and report on any problems it finds. It works within the permissions you set, so it cannot take actions beyond those you have approved.
How long does setup take?
Timelines depend on the complexity of your templates and the number of systems involved. A focused first workflow can often be connected and tested within a few weeks, following the free automation audit. We agree on the timeline with you before any work begins, and we launch only after testing against real cases.
Which plan or permissions do I need for OKZest?
In general, you need an OKZest account that allows API access, and an API key with permissions matching the workflow you want to automate. The exact requirements depend on your current OKZest arrangement, so we confirm them during the free automation audit.