2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 12 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Fellow Specialist",
    goal="Help users interact with Fellow effectively",
    backstory=(
        "You are an expert at leveraging Fellow 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 Fellow "
        "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)
Fellow
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 Fellow MCP Server

Connect your Fellow.app account to any AI agent and take full control of your meeting management, collaborative agendas, and action item tracking through natural conversation.

When paired with CrewAI, Fellow becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Fellow 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

  • Meeting Note Orchestration — List all meeting notes and retrieve full structured content including agenda items, discussion points, and decision metadata natively
  • Action Item Auditing — List and filter all tasks across meetings to track descriptions, assignees, and due dates for cross-meeting accountability flawlessly
  • Recording Management — Browse meeting recordings and retrieve video/audio details including time-limited download or stream URLs securely
  • AI Transcription Retrieval — Fetch full transcripts with speaker attribution and timestamps to review critical discussions or extract specific insights limitlessly
  • Task Lifecycle Control — Mark action items as complete or archive them to manage your active workspace and notify relevant stakeholders synchronously
  • Identity Oversight — Retrieve the authenticated profile identity including name, email, and workspace contexts to verify permission limits natively
  • Data Invalidation — Irreversibly vaporize specific meeting notes or recordings findable by ID to manage your organizational records strictly

The Fellow 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 Fellow to CrewAI via MCP

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

01

Install CrewAI

Run pip install crewai

02

Replace the token

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

03

Customize the agent

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

04

Run the crew

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

Why Use CrewAI with the Fellow MCP Server

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

01

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

02

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

03

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

04

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

Fellow + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

Fellow MCP Tools for CrewAI (12)

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

01

archive_action_item

Archive an action item, removing it from active views without deleting it

02

complete_action_item

Use when a task has been finished. Mark an action item as complete

03

delete_note

Confirm with the user before executing — this cannot be undone. Permanently delete a meeting note by ID

04

delete_recording

Confirm with the user before executing. Permanently delete a meeting recording by ID

05

get_action_item

Use to inspect a single task. Retrieve details of a specific action item by ID

06

get_current_user

Use to verify which account is connected. Retrieve the authenticated Fellow user profile

07

get_note

Essential for reviewing a specific meeting. Retrieve the full content and metadata of a specific meeting note by ID

08

get_recording

Use to access a specific recording. Retrieve details of a specific meeting recording

09

get_transcript

Use for detailed review, compliance documentation, or extracting specific discussion points. Retrieve the full transcript of a meeting recording

10

list_action_items

Use for cross-meeting task tracking and accountability. List all action items across all meetings

11

list_notes

Use as the primary entry point to browse all meeting documentation. List all meeting notes in the Fellow workspace

12

list_recordings

Use to browse all recorded meetings. List all meeting recordings captured by Fellow

Example Prompts for Fellow in CrewAI

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

01

"Show me all my pending action items"

02

"Get the notes for the meeting 'Product Sync' from last Tuesday"

03

"List the last 3 meeting recordings"

Troubleshooting Fellow MCP Server with CrewAI

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

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Fellow + CrewAI FAQ

Common questions about integrating Fellow MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect Fellow to CrewAI

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.