How to Use the Chorus.ai (ZoomInfo) MCP in CrewAI

Q: Does CrewAI support sequential workflows with the Chorus.ai (ZoomInfo) MCP Server?

Yes, that's the primary model. You can define a Process.sequential workflow where agents execute tasks one after another. For example, one agent finds meetings, the next analyzes them, and the last one sends a report.

Deploy autonomous agent crews on CrewAI to monitor, analyze, and report on your Chorus.ai sales calls.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Chorus.ai (ZoomInfo) MCP to CrewAI

Create your Vinkius account to connect Chorus.ai (ZoomInfo) 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 Chorus.ai (ZoomInfo) with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assemble a Competitive Intelligence Crew

Don't just run one agent. Deploy a team. A 'Scout' agent can run `list_chorus_meetings` daily to find new calls. It passes the list to a 'Scanner' agent, which gets the full text of each one using `get_meeting_transcript`. An 'Analyst' agent then takes the transcripts, checks them against a list from `list_tracked_competitors`, and flags any mentions. Finally, a 'Reporter' agent compiles the findings into a daily email brief. Each agent has one job, and CrewAI manages the handoff.

Automate Sales Coaching with a Crew

Build an autonomous coaching system. A 'Monitor' agent can use `list_chorus_users` to identify junior reps and watch for their new meetings. When one is found, it tasks a 'Reviewer' agent to pull `get_meeting_moments` and check for key phrases or missing playbook items. If the 'Reviewer' flags a call, it's passed to an 'Alerter' agent that notifies the appropriate sales manager. This is a complete, autonomous process that runs without any human input, all orchestrated by CrewAI.

Run Autonomous Onboarding with this MCP Server

Let a crew of agents handle new hire onboarding. One agent's only job is to run `list_chorus_users` and look for new team members. When it finds one, it triggers a 'Curator' agent. The 'Curator' then uses `list_meeting_playlists` to find the best introductory calls and assembles a personalized training list for the new hire. The crew works together to create a consistent onboarding experience, completely on its own.

Setup guide

Set up Chorus.ai (ZoomInfo) 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 Chorus.ai (ZoomInfo) tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

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

    task = Task(
        description="List recent Chorus.ai (ZoomInfo) 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 Chorus.ai. 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 Chorus.ai (ZoomInfo) 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 Chorus.ai (ZoomInfo) MCP in CrewAI

Agents in CrewAI share a context or 'memory' for the duration of a task. An agent can call `list_chorus_meetings`, and the resulting list of meetings is available to the next agent in the crew to process with `get_meeting_details` or `get_meeting_transcript`.

Yes. When you define your agents in CrewAI, you can use the `tool_filter` option in the MCP Server configuration. This lets you grant the 'Scout' agent access to only `list_chorus_meetings`, while the 'Analyst' gets `get_meeting_transcript`, enforcing role separation.

Yes, that's the primary model. You can define a `Process.sequential` workflow where agents execute tasks one after another. For example, one agent finds meetings, the next analyzes them, and the last one sends a report.

The easiest way is to pass the Vinkius MCP URL directly into the `mcps` list when creating your Agent. CrewAI will automatically fetch the available tools and make them ready to use.

This server processes meeting metadata, full transcripts, and user lists from your Chorus.ai account. Each tool call is handled by an independent, ephemeral function inside Vinkius's sandbox. The connection is secured by a single auth token, and the data is only held in memory long enough to be passed to your CrewAI agent.

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

Vercel AI SDK sdk-typescript