Can my agent list all content generated for a specific campaign in GRIN?

Yes. Use the 'list_content' tool with filters for the specific campaign. Your agent will retrieve the posts, stories, and media links associated with that activation flawlessly.

How do I track the ROI of an influencer via chat?

You can use the 'list_conversions' tool. Your agent will retrieve sales and attributed conversion data for specific creators, providing a clear overview of their performance natively.

Can I check the status of product seeding orders through the agent?

Absolutely. Use the 'list_orders' tool. Your agent will fetch the fulfillment statuses for all products sent to creators, ensuring your seeding logistics are on track flawlessly.

GRIN MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: GRIN
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to GRIN through Vinkius, pass the Edge URL in the `mcps` parameter and every GRIN tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="GRIN Specialist",
    goal="Help users interact with GRIN effectively",
    backstory=(
        "You are an expert at leveraging GRIN tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in GRIN "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

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

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 GRIN MCP Server

Connect your GRIN Creator Management account to any AI agent and take full control of your influencer marketing workflows through natural conversation.

When paired with CrewAI, GRIN becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call GRIN tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

CRM Orchestration — List and retrieve detailed creator profiles, social handles, and custom properties natively
Campaign Management — Monitor active influencer campaigns and track specific creator activations flawlessly
Content Oversight — Access and review the library of posts, stories, and media generated by your creators synchronously
Performance Tracking — Retrieve conversion data and ROI metrics attributed to specific influencers flawlessly
Logistics & Seeding — Manage product seeding orders and fulfillment statuses sent to creators natively
Partnership Navigation — List and verify formal brand-creator relationships and manage payouts synchronously

The GRIN MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI 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 GRIN to CrewAI via MCP

Follow these steps to integrate the GRIN MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from GRIN

Why Use CrewAI with the GRIN MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with GRIN through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

GRIN + CrewAI Use Cases

Practical scenarios where CrewAI combined with the GRIN MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries GRIN for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries GRIN, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain GRIN tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries GRIN against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

GRIN MCP Tools for CrewAI (12)

These 12 tools become available when you connect GRIN to CrewAI via MCP:

get_campaign

Get details for a specific campaign

get_contact

Get details for a specific creator

get_me

Get details for the current GRIN account

list_activations

Track creator participations within a campaign

list_campaigns

List active and past influencer campaigns

list_contacts

List all creators/influencers in the CRM

list_content

Access the library of posts and stories generated by creators

list_conversions

Track sales and ROI attributed to influencers

list_orders

Manage product seeding and fulfillment orders

list_partnerships

Manage formal brand-creator relationships

list_payments

List and manage creator payouts

update_contact

Update properties for a specific creator

Example Prompts for GRIN in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with GRIN immediately.

"List my influencer campaigns in GRIN"

"Show the conversion data for @janesmith"

"Check the status of seeding order #GF-88392"

Troubleshooting GRIN MCP Server with CrewAI

Common issues when connecting GRIN to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

GRIN + CrewAI FAQ

Common questions about integrating GRIN MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.