How to Use the AiMasher MCP in CrewAI

Q: Can one CrewAI agent create a campaign in AiMasher and another agent write the content?

Yes, that's a core pattern for CrewAI. One agent calls createcampaign and passes the resulting campaign ID to a second agent through the crew's shared context. The second agent then uses that ID to call generatecontent.

Q: What's the best way to filter which AiMasher tools my CrewAI agents can use?

For precise control, use the MCPServerHTTP class from crewai.mcp. It has a toolfilter parameter that lets you explicitly provide a list of tool names, ensuring an agent can only access the specific AiMasher functions you've approved.

Deploy an autonomous marketing team using CrewAI and AiMasher. Assign roles, define tasks, and let your agents run the entire content lifecycle.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect AiMasher MCP to CrewAI

Create your Vinkius account to connect AiMasher 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 AiMasher with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assemble a Content Creation Crew

Stop thinking in single prompts. With CrewAI, you can build a team. Create a 'Campaign Manager' agent that uses AiMasher's `create_campaign` tool to start a project. It then passes the campaign ID to a 'Copywriter' agent, whose only job is to execute the `generate_content` tool. This role-based approach makes your system cleaner and more powerful. A third 'Editor' agent can then use `list_outputs` to fetch the generated text and perform a quality check, all without any human intervention.

Run Autonomous Marketing Operations

Let a crew run your social media. A 'Strategist' agent decides it's time to post about a new topic. It tasks the 'Writer' agent to use AiMasher to generate three post variations using the `generate_content` tool with different prompts. Finally, a 'Publisher' agent picks the best one and sends it to another service. This entire process, from idea to publication, is handled by your CrewAI team and the AiMasher tools.

Delegate Research and Writing to Your CrewAI Team

Build a team where one agent does the research and another does the writing. The 'Researcher' agent can gather information, then formulate a detailed brief. It delegates the writing task to a 'Content' agent, which uses AiMasher's `generate_content` tool to turn the brief into a full article. This specialization is what makes CrewAI so effective. By giving each agent specific AiMasher tools and a clear role, you build a system that can produce high-quality, long-form content on its own.

Setup guide

Set up AiMasher 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 AiMasher tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent AiMasher 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="AiMasher Analyst",
        goal="Access and analyze AiMasher data via MCP.",
        backstory="Expert analyst with direct AiMasher access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent AiMasher 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 AiMasher. 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 AiMasher 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 AiMasher MCP in CrewAI

You can pass the Vinkius URL for your AiMasher MCP Server directly into the `mcps` parameter when defining an Agent. CrewAI handles the rest, making all the AiMasher tools available to that agent.

Yes, that's a core pattern for CrewAI. One agent calls `create_campaign` and passes the resulting campaign ID to a second agent through the crew's shared context. The second agent then uses that ID to call `generate_content`.

You assign different AiMasher tools to specialized agents. A 'Planner' agent uses `list_campaigns` to see what's running, a 'Creator' uses `generate_content`, and a 'Reviewer' uses `list_outputs`. They collaborate to execute the campaign from start to finish.

For precise control, use the `MCPServerHTTP` class from `crewai.mcp`. It has a `tool_filter` parameter that lets you explicitly provide a list of tool names, ensuring an agent can only access the specific AiMasher functions you've approved.

Your prompts, templates, and generated assets are processed in strict isolation. Vinkius runs every call to the AiMasher server inside a dedicated V8 Isolate sandbox. This means your data is never co-mingled with others' and is gone the moment your request is complete.

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