How to Use the RenderMe MCP in CrewAI

Q: Can I limit which CrewAI agents can use RenderMe render tools?

Yes, by using MCPServerHTTP and configuring a toolfilter. This lets you expose read-only tools like listvideotemplates to your planner agent, while reserving createvideorenderjob for your executive agent.

Q: How is the security of my RenderMe video templates managed in CrewAI?

All interactions with listvideotemplates and project files are secured using single-token endpoint authentication. Your API keys are injected at the Vinkius MCP gateway level, meaning your CrewAI Python environment never handles or exposes raw credentials.

Run a crew of specialized video agents that design, check, and render templates using CrewAI and RenderMe.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect RenderMe MCP to CrewAI

Create your Vinkius account to connect RenderMe to CrewAI — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup RenderMe with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Specialized video production teams in CrewAI

This MCP Server exposes `list_video_templates` and `list_uploaded_assets` to distribute video production tasks across a crew of specialized CrewAI agents. Stop asking a single agent to do everything. By dividing the labor, your CrewAI agents coordinate through shared memory. One agent picks the template, another matches the media, and a third runs the actual render using `create_video_render_job`.

Automated quality control loops

This MCP Server exposes `get_render_job_status` and `get_account_render_stats` to run automated quality control loops. Let a supervisor agent oversee your video generation pipeline. While your creative CrewAI agent calls `create_video_render_job`, a separate monitoring agent can poll status to watch for errors. If a job fails, the monitoring agent reads the logs and tasks the creative agent to adjust template parameters via `get_template_details`.

Selective tool exposure for security

Exposing write tools to your entire agent network is risky and expensive. Using this MCP Server lets you control execution costs by filtering access to high-impact operations. You can use the CrewAI `tool_filter` in your `MCPServerHTTP` configuration to restrict which agents can access write tools. Give your creative agents access to `create_video_render_job`, while restricting your research agents to read-only tools like `list_video_projects` and `list_video_templates`.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

The easiest way is to pass your Vinkius server URL directly in the agent's `mcps` array during initialization. CrewAI automatically fetches and registers all 12 tools, making them instantly available to that specific agent.

Yes, by using `MCPServerHTTP` and configuring a `tool_filter`. This lets you expose read-only tools like `list_video_templates` to your planner agent, while reserving `create_video_render_job` for your executive agent.

Agents use shared memory to pass asset and template IDs. For example, your media agent calls `list_uploaded_assets` and passes the selected image ID to your production agent, who then calls `create_video_render_job`.

Yes, the MCP server supports stdio, SSE, and Streamable HTTP. CrewAI can connect to the RenderMe server locally via stdio or remotely using a hosted HTTP endpoint on Vinkius.

All interactions with `list_video_templates` and project files are secured using single-token endpoint authentication. Your API keys are injected at the Vinkius MCP gateway level, meaning your CrewAI Python environment never handles or exposes raw credentials.

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