How to Use the Amplience MCP in CrewAI

Q: How do I restrict certain Amplience tools in CrewAI?

Use MCPServerHTTP from crewai.mcp and apply a toolfilter. This lets you expose read-only tools to researchers while keeping publishing tools restricted to moderators.

Deploy CrewAI autonomous agents to manage your Amplience CMS, using this MCP Server to research and publish content.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Amplience MCP to CrewAI

Create your Vinkius account to connect Amplience to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Amplience with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assign CrewAI agents to audit

Stop manually checking your headless CMS configurations across different regions. You can assign a dedicated researcher agent to map out the entire architecture. It starts by running `list_hubs` to find active workspaces and follows up with `list_repositories` to index the storage buckets. The researcher shares this mapped context with the rest of the crew. Another agent takes that memory and uses `list_folders` to categorize campaigns, then pulls the actual records using `list_content_items`. Your team gets a complete audit without anyone clicking through a dashboard.

Build an autonomous pipeline

Content creation works best when separated into specialized roles. A writer agent analyzes market trends and drafts new product copy. It then executes `create_content_item` to insert a perfectly structured record into the designated folder via this MCP Server. An editor agent immediately picks up the draft from shared memory. It pulls the exact configuration using `get_content_item` to verify the schema revision lock. If the text needs tweaking, the editor fires `update_content_item` to fix the data structure before sending it down the line.

Manage live CDN deployments

You never want a junior agent pushing directly to production. A senior moderator agent acts as the gatekeeper for your live delivery CDN using this MCP integration. When a campaign is ready, this moderator calls `publish_content_item` to deploy the specific version safely. Cleanup is just as important for maintaining a healthy database. The moderator can also prune expired seasonal promotions by executing `delete_content_item`. It then verifies the current live state by checking the delivery CDN blocks with `get_delivery_content`.

Setup guide

Set up Amplience MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Amplience tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Amplience Analyst",
    goal="Access and analyze Amplience data via MCP.",
    backstory="Expert analyst with direct Amplience access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Amplience transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Amplience Analyst",
        goal="Access and analyze Amplience data via MCP.",
        backstory="Expert analyst with direct Amplience access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Amplience transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Amplience. 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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Amplience now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Amplience MCP in CrewAI

Add the Vinkius endpoint URL directly to the mcps array when defining your Agent. The crew automatically discovers all available tools.

Yes. Because they share memory, one agent can list hubs while another updates content items, working together without stepping on each other's toes.

Use MCPServerHTTP from crewai.mcp and apply a tool_filter. This lets you expose read-only tools to researchers while keeping publishing tools restricted to moderators.

The server handles standard HTTP endpoints. You simply pass the URL and let the framework handle the underlying connection.

Your crew reads delivery CDN blocks and schema data securely. Vinkius hosts the connection in a stateless V8 Isolate Sandbox. No proprietary ecommerce copy leaks into shared environments or training datasets.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript