GoTo Connect MCP Server for CrewAI 12 tools — connect in under 2 minutes
Connect your CrewAI agents to GoTo Connect through Vinkius, pass the Edge URL in the `mcps` parameter and every GoTo Connect 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="GoTo Connect Specialist",
goal="Help users interact with GoTo Connect effectively",
backstory=(
"You are an expert at leveraging GoTo Connect 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 GoTo Connect "
"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)
* 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 GoTo Connect MCP Server
Connect your GoTo Connect (formerly Jive) unified communications account to your AI agent and manage your business telephony directly from your workflow. Use natural language to query call histories, send and receive SMS messages, and manage your contacts without opening the GoTo desktop app.
When paired with CrewAI, GoTo Connect becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call GoTo Connect 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 Records (CDR) — Retrieve detailed call histories for specific users to audit activity or find a missed call
- SMS Messaging — Send SMS messages to clients directly from the chat and retrieve conversation histories
- Voicemail Management — List recent voicemails and check their transcription status
- Device & User Management — Look up active users, their extension numbers, and the status of their assigned devices
- Contact Management — Search through your company contacts and add new entries programmatically
The GoTo Connect 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 GoTo Connect to CrewAI via MCP
Follow these steps to integrate the GoTo Connect 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 GoTo Connect
Why Use CrewAI with the GoTo Connect MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with GoTo Connect 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
GoTo Connect + CrewAI Use Cases
Practical scenarios where CrewAI combined with the GoTo Connect MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries GoTo Connect 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 GoTo Connect, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain GoTo Connect 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 GoTo Connect against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
GoTo Connect MCP Tools for CrewAI (12)
These 12 tools become available when you connect GoTo Connect to CrewAI via MCP:
create_contact
Create a new contact
get_call_record
Get details for a specific call record
get_call_records
List call records (history) for a user
get_me
Get details for the currently authenticated GoTo user
get_user
Get details for a specific user
get_voicemail
Get details for a specific voicemail
list_contacts
List a user's contacts
list_devices
List devices associated with a user
list_sms_messages
List SMS messages for a user
list_users
List GoTo Connect users
list_voicemails
List voicemails for a user
send_sms
Send an SMS message via GoTo Connect
Example Prompts for GoTo Connect in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with GoTo Connect immediately.
"Show my recent call records."
"Send a text from my number to +15551234567 saying 'Hi, our meeting is starting in 5 mins'."
"Check if an active voicemail remains for extension 202 unhandled."
Troubleshooting GoTo Connect MCP Server with CrewAI
Common issues when connecting GoTo Connect 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
GoTo Connect + CrewAI FAQ
Common questions about integrating GoTo Connect 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 GoTo Connect 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 GoTo Connect to CrewAI
Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.
