Zesty.io MCP for AI. Manage Site Content Without Touching the Dashboard
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Zesty.io lets your AI client manage content models, data entries, and site instances from natural language. Instead of logging into a CMS dashboard or writing complex API calls, you talk to it: ask for all associated sites, check what data structures exist, or tell it to create and update specific pieces of content.
What your AI can do
Create content item
Builds and publishes a new piece of content by defining its field values in a JSON object.
Delete content item
Removes an existing content item from the CMS.
Get content item
Fetches all details for a single, specific piece of content.
List every single instance associated with your account, giving you visibility into multiple properties.
List available content models to understand the required structure and unique IDs for your content types.
Fetch lists of specific items within a given model, giving you an overview of current published data.
Get the full set of information for one particular content item using its unique identifier.
Build and publish brand-new content items by passing a structured JSON object with required field values.
Update specific fields on an already published content item, like changing a title or body copy.
Ask an AI about this
Waiting for input…
Zesty.io: 8 Tools for CMS Management
These tools let your agent interact with Zesty.io data by listing models, retrieving specific content pieces, or performing bulk updates and creations.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Zesty.io on VinkiusCreate Content Item
Builds and publishes a new piece of content by defining its field values in a JSON object.
Delete Content Item
Removes an existing content item from the CMS.
Get Content Item
Fetches all details for a single, specific piece of content.
List Zesty Instances
Retrieves a list of every Zesty.io property associated with the account.
List Content Items
Lists all content items belonging to a specific data model.
List Content Models
Reads all available content models, helping you find the correct unique identifier (ZUID) for your data structure.
Get Instance Settings
Retrieves the configuration settings and technical metadata for the connected CMS instance.
Update Content Item
Modifies existing content items by accepting updated field values.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Zesty.io integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Zesty.io, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Zesty.io. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 8 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Dealing with CMS Content Feels Like a Maze
Today, modifying content means logging into the Zesty.io UI. You click through model selectors, navigate to specific instances, find the right data field, and copy-paste your changes—or worse, you have to build complex API calls in a separate terminal just to read what's there.
With this MCP, you bypass the entire dashboard. Your agent accepts natural language commands like 'Check if the Product Showcase site has content for Q3.' You get a direct answer and the ability to make changes without touching any UI.
Getting Content Data with Zesty.io MCP
You eliminate the need to remember specific API endpoints or the correct parameter order for creating items. You don't have to manually verify if you used the right Model ZUID.
The process is simple: tell your agent what content needs changing, and it executes the complex sequence of calls required across multiple tools—from reading model definitions to updating item records.
What your AI can actually do with this
This MCP connects your AI agent directly to the Zesty.io platform, giving it full read/write access over your digital assets. You can treat your CMS like a database you talk to. Need to know what sites you run? Ask for all associated instances and get their metadata. Want to publish an article? Instruct your agent to create a new content item using the correct data structure.
It handles listing, retrieving, updating, or outright deleting existing content pieces across any model. Because this MCP manages credentials through Vinkius's zero-trust proxy, your API tokens never sit on disk; they only flow securely during transit. This capability lets you manage complex site architectures and content lifecycles without ever needing to handle the raw API keys yourself.
019d7628-6abe-7322-ac9e-41e0827b82a6 
Here's how it actually works
The bottom line is you tell your AI client what content change you need, and the MCP executes the API action directly.
Subscribe to this MCP and input your Zesty API Token along with the instance's unique identifier.
Connect your preferred AI client (like Cursor or Claude) to Vinkius. The agent now has access to all configured tools.
Ask your agent a natural language question, such as 'List all models for my marketing site,' and it executes the necessary tool call.
Who is this actually for?
Content Managers who dread logging into multiple CMS dashboards. Developers building internal tools that need to read or write site data without manual endpoint calls. Growth Engineers automating content population for marketing campaigns.
Needs to check if the 'About Us' page copy is updated across three different properties, requiring checks and modifications in multiple UIs.
Wants to quickly query available content models and test API data structures from their IDE without writing boilerplate connection code.
Needs to programmatically generate and publish a batch of landing page items based on external spreadsheet data.
What Changes When You Connect
Get instant visibility across all your sites using list_zesty_instances. You don't have to manually navigate through multiple dashboards just to know which properties you own.
Know exactly what data structures are available by running list_content_models. This lets developers test schema requirements before they write a single line of code.
Need an overview of published content? Use list_content_items to get lists of assets for any model, letting you audit your current content inventory quickly.
Instead of copy-pasting data and refreshing pages, use the agent to execute updates via update_content_item. The AI handles the field mapping and API calls in one go.
Need to publish a piece of content from scratch? Use create_content_item to generate new assets directly through natural language instructions.
The ability to delete obsolete content using delete_content_item keeps your CMS clean, letting you manage the entire lifecycle—creation, modification, and archival.
See it in action
Checking site inventory
A marketing manager needs to know how many properties are linked under their account. They ask: 'List all my Zesty instances.' The agent uses list_zesty_instances and provides a clean, immediate list of every property ID.
Drafting new product copy
A growth engineer has 20 pieces of copy ready for a new landing page. They instruct their agent: 'Create 20 content items in the Product Landing model.' The agent handles the JSON formatting and calls create_content_item repeatedly.
Auditing stale data
A developer needs to see which articles haven't been updated in six months. They ask: 'List all content items from the blog model.' The agent uses list_content_items, giving them a dataset they can then filter.
Mass updating metadata
A team needs to change the boilerplate legal text on 50 existing pages. They ask: 'Update the content item ID X with new terms and conditions.' The agent executes update_content_item for every specified asset.
The honest tradeoffs
Writing raw API calls in your client
Manually building a complex POST request body with nested JSON objects, only to find the required ZUID is wrong.
Don't write the code. Use the agent first to run list_content_models. Then, tell the agent: 'Use this model ID and create content item X.' The MCP handles the structured payload.
Assuming all data is in one place
Trying to list all models without knowing which specific instance you are targeting.
Always start by calling list_zesty_instances to confirm your target property ID before running any read or write tools.
Overwriting data blindly
Telling the agent to 'update content X' without specifying which fields need changing, risking a full overwrite with null values.
Be specific. Use get_content_item first to verify the current structure, then tell the agent: 'Update only the title and body of this item.'
When It Fits, When It Doesn't
Use this MCP if your primary need is managing structured content (models) or published assets (items). You want an AI agent to read, write, or inspect data stored in a CMS. However, do not use it if you are trying to manage payment records, user authentication flows, or external ticketing systems. For those tasks, connect a dedicated billing or CRM MCP instead. If your goal is simply listing available models, stick to list_content_models. If you need to know which site ID to work on, start with list_zesty_instances before attempting any other action.
Questions you might have
How do I find all properties linked to my account using list_zesty_instances? +
You simply ask your agent to 'List all Zesty.io instances.' The MCP will execute list_zesty_instances and provide a clean, categorized list of every property you have access to.
Can I use create_content_item if I don't know the model ID? +
No. First, you need to run list_content_models so your agent can show you all available content structures and identify the correct Model ZUID before attempting creation.
Is update_content_item safe for large batches of data? +
It works best when you specify exactly which fields need updating. It's safest to run get_content_item first, verify the current structure, and then provide a targeted instruction for the update.
What is the difference between list_content_items and get_content_item? +
list_content_items shows you a summary of multiple assets (like an index), while get_content_item fetches all the deep, detailed data for one single asset.
How do I get started running list_content_models? +
You must provide a valid Zesty API Token and the specific Instance ZUID. With those credentials, your agent can call list_content_models to immediately map out all available content types in your account.
If I run get_content_item and the item ID is wrong, what should happen? +
The system returns a specific 'Not Found' status code. This means you need to double-check the content item ID or use list_content_items first to verify the correct record.
How can I check my agent’s permissions for deletions using get_instance_settings? +
You run get_instance_settings to review the current configuration and access scopes. This view tells you exactly which permissions are active, confirming if your agent has delete rights.
What data structure does create_content_item require? +
It requires a structured JSON object containing all field values. The required keys and types must match an existing content model schema; check your models using list_content_models.
How do I find my Instance ZUID? +
You can list all your accessible instances using the list_zesty_instances tool, or find it in your Zesty.io URL (it starts with 8-).
Can I see all content items for a particular model? +
Yes, use the list_content_items tool with the unique ZUID of the model (starts with 6-) to retrieve all associated entries.
Is it possible to update content via the agent? +
Absolutely. Use the update_content_item tool by providing the Model ZUID, the Item ZUID, and a JSON object containing the fields you wish to modify.
We've already built the connector for Zesty.io. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 8 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.