CallGear MCP Server for CrewAI 10 tools — connect in under 2 minutes
Connect your CrewAI agents to CallGear through Vinkius, pass the Edge URL in the `mcps` parameter and every CallGear tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="CallGear Specialist",
goal="Help users interact with CallGear effectively",
backstory=(
"You are an expert at leveraging CallGear 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 CallGear "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 10 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* 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 CallGear MCP Server
Connect your CallGear account to any AI agent and orchestrate your communication analytics, marketing attribution, and call tracking through natural conversation.
When paired with CrewAI, CallGear becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call CallGear 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
- Call Performance Oversight — Retrieve detailed reports of all incoming and outgoing calls, including sources, durations, and statuses.
- Marketing Attribution — Monitor advertising campaign performance and identify which sources are driving the most communications.
- Communication Analysis — Get broader reports covering calls, chats, and other interactions to ensure service quality.
- Infrastructure Coordination — Access and monitor your traffic sources, call scenarios, and tags directly from your workspace.
- User & Team Oversight — List all users in your CallGear account to maintain visibility across your team.
- Real-time Statistics — Retrieve daily site and campaign stats straight from your workspace.
The CallGear MCP Server exposes 10 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 CallGear to CrewAI via MCP
Follow these steps to integrate the CallGear 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 10 tools from CallGear
Why Use CrewAI with the CallGear MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with CallGear 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
CallGear + CrewAI Use Cases
Practical scenarios where CrewAI combined with the CallGear MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries CallGear 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 CallGear, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain CallGear 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 CallGear against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
CallGear MCP Tools for CrewAI (10)
These 10 tools become available when you connect CallGear to CrewAI via MCP:
get_account_info
Retrieve core account information
get_ad_campaigns_report
Retrieve daily aggregated statistics for advertising campaigns
get_calls_report
Retrieve a detailed report of calls for a specific period
get_communications_report
Retrieve a report covering various communication types (calls, chats, etc.)
get_site_daily_stats
Retrieve daily statistics for sites
list_ad_campaigns
List all advertising campaigns
list_call_scenarios
List all configured call scenarios
list_tags
List all call and communication tags
list_traffic_sources
List all traffic sources configured in CallGear
list_users
List all users in the CallGear account
Example Prompts for CallGear in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with CallGear immediately.
"Show the calls report from March 1st to March 7th."
"Which advertising campaigns are active right now?"
"Show daily stats for my website for the last 3 days."
Troubleshooting CallGear MCP Server with CrewAI
Common issues when connecting CallGear to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
CallGear + CrewAI FAQ
Common questions about integrating CallGear MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
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?
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?
Can CrewAI agents call multiple MCP tools in parallel?
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)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect CallGear with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect CallGear to CrewAI
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.
