How to Use the Close CRM (Inside Sales CRM & Automation API) MCP in CrewAI

Q: How do I give my CrewAI agents access to Close CRM (Inside Sales CRM & Automation API)?

Pass your Vinkius MCP Server URL into the mcps parameter when defining your agent in CrewAI. For more control, you can use MCPServerHTTP to filter which specific tools, like createlead or deletelead, each agent can access.

Q: Can different agents in a crew share information from Close CRM?

Yes, that's what CrewAI is designed for. One agent can use listleads to find a record, and then pass the lead's ID and data into the shared context for another agent to use with updatelead.

Deploy an autonomous sales team to manage Close CRM with CrewAI. Assign roles, share context, and let your agents run the pipeline.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Close CRM (Inside Sales CRM & Automation API) MCP to CrewAI

Create your Vinkius account to connect Close CRM (Inside Sales CRM & Automation API) 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 CRM (Inside Sales CRM & Automation API) with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assemble Your AI Sales Crew

Create a team of specialized CrewAI agents to manage your sales pipeline. An "Inbound Specialist" agent can monitor for new signups using `list_form_submissions` and then use `create_lead` to get them into Close CRM. Then, a "Sales Analyst" agent can take over. It uses `search_data` to enrich the new lead, checks for existing `list_contacts`, and then uses `create_task` to assign it to a human for follow-up. Each agent has a clear job.

Autonomous Pipeline Management with CrewAI

Set your CrewAI agents loose on your pipeline. One agent can be tasked with finding stale deals by running `list_opportunities` with a date filter. When it finds one, it can pass it to another agent. A "Closer" agent could then analyze the stale deal, pull `list_notes` and `list_emails` for context, and then decide the next best action, like adding a task or sending a follow-up. This happens automatically.

Delegate Reporting to an Agent

Assign reporting to an agent on your crew. A "Reporting Bot" can be programmed to run `activity_report` every morning and summarize the findings. It can also pull `list_calls` and `list_sms` to see who is making contact. Because CrewAI agents can collaborate, the Reporting Bot can pass its findings to a "Strategy Bot". That agent can then analyze the data and suggest changes, like which automated `list_sequences` are performing best.

Setup guide

Set up Close CRM (Inside Sales CRM & Automation API) 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 CRM (Inside Sales CRM & Automation API) tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

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

    task = Task(
        description="List recent Close CRM (Inside Sales CRM & Automation API) 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 CRM. 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 CRM (Inside Sales CRM & Automation API) 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 CRM (Inside Sales CRM & Automation API) MCP in CrewAI

Pass your Vinkius MCP Server URL into the `mcps` parameter when defining your agent in CrewAI. For more control, you can use `MCPServerHTTP` to filter which specific tools, like `create_lead` or `delete_lead`, each agent can access.

Yes, that's what CrewAI is designed for. One agent can use `list_leads` to find a record, and then pass the lead's ID and data into the shared context for another agent to use with `update_lead`.

You can get pretty close. A crew could manage the entire lead lifecycle: `create_lead` from a form, `update_lead` with new info, `create_opportunity` when it's qualified, and even `delete_lead` if it's junk.

Your agents can create, list, and manage tasks for your human team. An agent could use `list_tasks` to see what's overdue, and then use `create_task` to assign a new, high-priority follow-up to a salesperson.

The server only touches the specific data your agents request, like Lead, Opportunity, and Task objects. Your Vinkius URL is the key; it authenticates your requests. The server itself is ephemeral and runs in a zero-trust sandbox, so your data isn't stored.

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