How to Use the GoTo Meeting MCP in CrewAI

Q: Can CrewAI agents collaborate on GoTo Meeting tasks?

Yes. You can have one agent list upcoming sessions with listmeetings and another agent analyze that list to identify scheduling conflicts.

Q: How do I filter GoTo Meeting tools in CrewAI?

Use the toolfilter parameter in your agent configuration. This limits the agent to only the tools it needs, such as createmeeting and deletemeeting.

Q: Can I use CrewAI to audit GoTo Meeting history?

Yes. Give your audit agent access to listmeetinghistory to track usage patterns and report back on meeting frequency across your team.

Deploy a specialized crew of autonomous agents to manage GoTo Meeting scheduling and monitoring across your entire organization.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect GoTo Meeting MCP to CrewAI

Create your Vinkius account to connect GoTo Meeting to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup GoTo Meeting with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous GoTo Meeting scheduling with CrewAI

Assign a dedicated scheduling agent to run `create_meeting` whenever your research agent identifies a need for a call. The agents work in sequence, ensuring the meeting is booked without human intervention. Your crew handles the entire lifecycle. One agent gathers the details, another initiates the booking, and the system confirms the time back to the user.

Session monitoring for CrewAI crews

Use a monitor agent to periodically run `list_meetings` and report status back to your primary coordinator. If a meeting is missing or delayed, the monitor notifies the team immediately. This keeps your operations running without manual oversight. The agents watch the schedule and flag issues before they become problems for your team.

Retrieve GoTo Meeting details for analysis

Task your analysis agent with calling `get_meeting_details` to pull specific participant and metadata info. This allows the crew to provide a summary of every session after it concludes. Your agents turn raw API responses into actionable insights. They process the session details and generate reports based on the criteria you set.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

Yes. You can have one agent list upcoming sessions with `list_meetings` and another agent analyze that list to identify scheduling conflicts.

Use the tool_filter parameter in your agent configuration. This limits the agent to only the tools it needs, such as `create_meeting` and `delete_meeting`.

The server uses a zero-trust architecture. We only handle the specific meeting metadata required to execute the tool, and all data is wiped from the memory buffer after the task completes.

The MCP Server manages the connection to the API. If you hit a rate limit, the server reports it, and your agents can be programmed to wait before retrying.

Yes. Give your audit agent access to `list_meeting_history` to track usage patterns and report back on meeting frequency across your team.

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