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.

Amplience MCP Server for Claude Desktop 10 tools — connect in under 2 minutes

Name: Amplience
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 10 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Amplience and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "amplience": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Amplience MCP Server

Link your Amplience headless CMS to any intelligent AI agent to completely rethink how you handle your enterprise content architecture, deploying components natively through standard conversation.

Claude Desktop is the definitive way to connect Amplience to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Discover Asset Hierarchies — Freely list top-level Hubs, target specific Repositories, and fetch internal Folders to help your AI inherently understand where every graphic and article lives.
Content Retrieval — Paginate through dynamic content items, safely extracting complete metadata alongside current active schemas and validation rules.
Edit & Create Structure — Give the agent full permission to push correctly strictly-typed JSON payloads back into the system, generating or modifying blog entries and product metadata.
Manage Deployments — Permanently execute deletions (if revision locks permit) or instruct the system to fire a specific content configuration directly over to the edge delivery API to hit the live website.

The Amplience MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Amplience to Claude Desktop via MCP

Follow these steps to integrate the Amplience MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Amplience

Look for the 🔌 icon in the chat. your 10 tools are now available

Why Use Claude Desktop with the Amplience MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Amplience through the Model Context Protocol.

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Amplience + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Amplience MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Amplience MCP Tools for Claude Desktop (10)

These 10 tools become available when you connect Amplience to Claude Desktop via MCP:

create_content_item

Create a new structured content item adhering to a schema inside a folder

delete_content_item

Requires version validation before deletion. Permanently delete a content item from the repository database

get_content_item

Retrieve a specific content item configuration and its schema revision lock

get_delivery_content

Retrieve the exact structural matching verifying Delivery CDN blocks

list_content_items

Retrieve paginated content items from a specific repository

list_folders

List all folders organizing content in a given repository

list_hubs

Essential for retrieving the active workspace. List all accessible Amplience Hubs (environments)

list_repositories

List all content repositories within a specific Hub

publish_content_item

Publish a specific content item version to the live delivery CDN

update_content_item

Update an existing content item data structure matching its current schema

Example Prompts for Amplience in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Amplience immediately.

"Identify all active repositories present inside my default Amplience Hub."

"Pull the structural metadata (schema lock and payload) of item '5tYv92'."

"Publish the newly edited Content '5tYv92' to the global live network."

Troubleshooting Amplience MCP Server with Claude Desktop

Common issues when connecting Amplience to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Amplience + Claude Desktop FAQ

Common questions about integrating Amplience MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.