How to Use the Close MCP in CrewAI

Q: How do I register the Close MCP Server with CrewAI?

Pass your Vinkius server URL directly into the mcps list when initializing your CrewAI agents. The framework automatically parses the available tools and makes them accessible to your specialized agents.

Q: Can I filter which Close MCP tools a specific CrewAI agent can use?

Yes, you can use MCPServerHTTP from crewai.mcp along with a toolfilter to limit exposure. This prevents your research agents from accessing sensitive functions like pipeline configurations.

Deploy specialized CrewAI agent teams to manage your Close sales pipelines.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Close MCP to CrewAI

Create your Vinkius account to connect Close 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 Close with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

CrewAI Multi-Agent Lead Qualification

This Close MCP Server exposes `list_close_leads` so your CrewAI research agents can scan and qualify new prospects. A dedicated analyst agent reads the raw lead data, while a separate communication agent drafts personalized outreach. The research agent uses `get_lead_details` to extract background information on high-value contacts. By dividing the labor, your crew processes entire lead lists without human supervisors needing to coordinate the steps.

Collaborative Opportunity Management

This tool provides shared access to sales deals via `list_close_opportunities` for your specialized negotiation agents. One agent tracks deal progression while another calculates commission forecasts based on pipeline values. When a deal stalls, the monitoring agent calls `get_opportunity_details` to identify blockages. The crew shares this context dynamically, allowing the escalation agent to intervene before the opportunity expires.

Autonomous Pipeline and Task Coordination

This feature allows your operational agents to organize CRM schedules using `list_close_tasks` to coordinate daily work. A coordinator agent reads the task queue, while a worker agent executes the actual customer follow-ups. The crew references `list_close_pipelines` to understand which stages require immediate attention. Each agent works toward a shared objective, keeping your entire Close database organized without manual input.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

Pass your Vinkius server URL directly into the `mcps` list when initializing your CrewAI agents. The framework automatically parses the available tools and makes them accessible to your specialized agents.

Yes, you can use `MCPServerHTTP` from `crewai.mcp` along with a `tool_filter` to limit exposure. This prevents your research agents from accessing sensitive functions like pipeline configurations.

The framework utilizes shared memory, meaning once one agent calls `get_lead_details`, the resulting context is accessible to other crew members. This prevents duplicate API calls and coordinates your team's actions.

Yes, you can configure your crew to execute tasks sequentially or hierarchically. For instance, a lead-checking agent calls `list_close_leads` before passing the results to an outreach agent.

All CRM data, including lead profiles, pipelines, and tasks, passes through the MCP server running on Vinkius. We run every agent session in an ephemeral V8 Isolate sandbox to keep your proprietary sales pipelines completely segmented and private.

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