# Amplience MCP for AI Agents AI Agent Connect > Amplience MCP lets you connect your headless CMS to your AI agent. You can query hubs, pull content, edit schemas, and deploy live items directly through chat. It turns your content architecture into something your agent can actually navigate and modify without you having to jump between tabs. ## Overview - **Category:** ecommerce - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_JeoiOM8ki8jslAZQLhECHOmHPjVyKZPKjRrtAdGX/ai-agent-connect - **Tags:** digital-asset-management, content-architecture, edge-delivery, schema-management, enterprise-content ## Description The way most teams handle headless CMS content is a mess of tabs and manual data entry. You're constantly switching between your code editor, your content management dashboard, and your delivery logs to make sure everything is synced. This Connector changes that by giving your AI agent a direct line into your Amplience environment. Instead of copy-pasting JSON payloads or hunting for specific repository IDs, you can just tell your agent what needs to happen. It can look up your asset hierarchies, grab specific content items, or push updates to your live site. It's a big shift in how you manage enterprise content architecture. Because Vinkius hosts this, you can plug it into your existing setup and start talking to your CMS immediately. You're not just integrating a tool; you're giving your agent the keys to your content house so you can focus on building rather than babysitting data. You can have it fetch the exact structural metadata for a banner or generate a new draft for a promotional blog post based on your specific SEO guidelines. It takes the friction out of the content to code pipeline by making your CMS data accessible and actionable through a simple conversation. ## Tools ### publish_content_item Send a specific version of a content item to your live delivery CDN. ### update_content_item Modify an existing content item's data while ensuring it matches the current schema. ### create_content_item Create a new structured content item that follows a specific schema inside a folder. ### delete_content_item Permanently remove a content item from your repository after confirming version validation. ### get_delivery_content Verify the structural matching of content blocks on the Delivery CDN. ### list_folders See all the folders organizing your content within a given repository. ### get_content_item Pull the configuration and schema revision lock for a specific content item. ### list_content_items Get a paginated list of all content items within a specific repository. ### list_hubs List all accessible Amplience Hubs to identify your active workspaces. ### list_repositories See all content repositories located within a specific Hub. ## Prompt Examples **Prompt:** ``` Show me all the repositories in my main Hub. ``` **Response:** ``` I've scanned your active workspace. Here are the repositories found: | Repository Name | ID | | :--- | :--- | | Core Web Components | `6k33i1` | | Blog Content | `6m75o9` | | Banner Ad Images | `9q82y3` | Which one would you like me to inspect? ``` **Prompt:** ``` Get the schema for item 5tYv92. ``` **Response:** ``` I've retrieved the structural metadata for Content Item **5tYv92** ('Spring Banner 2024'): * **Schema Lock Version:** 5 * **Payload:** `{ "title": "Spring Sales!", "href": "/shop/spring" }` Let me know if you want to modify any of these fields. ``` **Prompt:** ``` Publish the banner to the live site. ``` **Response:** ``` Understood. I'm pushing the updates to the edge delivery API now. **Status:** Success **Action:** Published Content Item `5tYv92` to the live domain. Would you like me to verify the delivery URL JSON logic for you? ``` ## Capabilities ### List content hubs Discover your workspace environments and identify active hubs. ### Query content repositories See every folder and asset in a specific repository. ### Fetch content metadata Get the specific JSON and schema rules for any content item. ### Create new content items Add new blog posts or product data to your folders using schemas. ### Update existing content Modify data structures while staying within your current schema rules. ### Publish to the edge Push changes live to your delivery CDN instantly. ### Delete content items Remove old data from your repository after confirming version locks. ## Use Cases ### Updating a Sale Banner An e-commerce manager tells the agent to find the Black Friday banner and update the URL. The agent uses list_repositories and update_content_item to make it happen. ### Scaffolding a New Component A dev asks the agent to read a schema. The agent uses get_content_item to pull the validation rules so the dev can build a React component. ### Bulk Content Creation A marketer asks to create 10 blog drafts. The agent uses create_content_item to populate them with SEO guidelines. ### Verifying Live Content A dev wants to see what's live. The agent uses get_delivery_content to check the CDN blocks. ## Benefits - Stop manual JSON entry by using create_content_item to push data directly into your folders. - Speed up site updates by using publish_content_item to hit the live edge delivery API instantly. - Simplify asset discovery with list_hubs and list_repositories to see your whole architecture. - Ensure data integrity by using update_content_item to keep your content strictly typed. - Save time on frontend work by using get_content_item to grab schema locks for your code. - Clean up your workspace by using delete_content_item to remove deprecated assets. ## How It Works The bottom line is you stop manual data entry and let your agent handle the heavy lifting of CMS management. 1. Add your Hub Name and Personal Access Token to your environment. 2. Tell your agent which repository or folder you want to inspect. 3. Give commands to create, update, or publish content directly. ## Frequently Asked Questions **Can I use Amplience MCP to update live site content?** Yes, it lets your agent push updates directly to the delivery CDN. You can command your agent to modify content and publish it to the live site in one go. **How does Amplience MCP help with content schemas?** It allows your agent to read schema locks so your code stays in sync. This ensures that any data your agent creates or updates follows your strict validation rules. **Can my agent create new blog posts with this?** Yes, it can generate and push new items into your specific folders. You can even provide SEO guidelines for the agent to follow during creation. **Will Amplience MCP help with e-commerce updates?** It is perfect for e-commerce teams who need to update URLs, product metadata, and banner configurations quickly through a chat interface. **Does Amplience MCP work with Cursor or Claude?** Yes, it connects to any MCP-compatible client, including Claude, Cursor, and Windsurf, giving those tools full access to your CMS. **Can I delete old content using Amplience MCP?** Yes, it can remove items from your repository once you've validated the version. This helps keep your content architecture clean and organized. **Can the agent push updates without breaking my Amplience JSON schemas?** Yes. Before invoking the update tool, the agent utilizes context to retrieve the item's precise configuration. It parses the associated Schema ID requirements and injects the updated stringified payload adhering identically to Amplience's validation rules. **Will the integration protect my items against concurrent manipulation issues?** Yes. Our Amplience server requires the agent to explicitly pass the exact `version` lock integer on every DELETE or UPDATE request. If a human colleague alters your CMS page while the agent is typing, the AI request is robustly rejected avoiding fatal overwrites. **Can I publish a finalized post straight to the Edge Delivery API from here?** Absolutely. Once the content looks solid offline, just declare 'Publish this content item now.' The agent resolves the `publish_content_item` tool pointing to your Edge API and the post lives dynamically on your core frontend instantly.