Can my AI agent find a specific business card by just a first name?

Yes. Ask the agent to run the `search_biz_cards` tool with the contact's name. It will look through all digitized cards in the shared corporate database and return the matching profiles, including their company, department, and direct contact details.

Is it possible to list only contacts from a specific department?

Yes, you can ask your agent to first execute `list_departments` to view your organizational structure, and then cross-reference those entities with the cards via natural prompts to summarize card acquisitions per department.

What is the difference between business cards and persons?

Business Cards are individual scan snapshots of physical cards acquired over time. A 'Person' represents the consolidated identity created when multiple updated cards from the same individual are merged. You can query both views via `list_biz_cards` or `list_persons`.

Sansan MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: Sansan
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to Sansan through the Vinkius — pass the Edge URL in the `mcps` parameter and every Sansan tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Sansan Specialist",
    goal="Help users interact with Sansan effectively",
    backstory=(
        "You are an expert at leveraging Sansan 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 Sansan "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 Sansan MCP Server

Connect your Sansan account to any AI agent to access your organization’s entire secure network of digitized business cards. Effortlessly manage contact relationships directly from Claude, Cursor, or your preferred MCP client.

When paired with CrewAI, Sansan becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Sansan tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Business Cards — List all scanned cards, retrieve comprehensive details by card ID, and search for specific contacts by name
Personnel Records — Browse individual person profiles across all captured cards and access deep contact details
Network Organization — Inspect all available tags used for structuring and organizing business cards
Enterprise Structure — List registered Sansan users and view all distinct departments within your organization

The Sansan MCP Server exposes 8 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 Sansan to CrewAI via MCP

Follow these steps to integrate the Sansan 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 8 tools from Sansan

Why Use CrewAI with the Sansan MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Sansan 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 the 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

Sansan + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Sansan MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Sansan 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 Sansan, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Sansan 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 Sansan against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Sansan MCP Tools for CrewAI (8)

These 8 tools become available when you connect Sansan to CrewAI via MCP:

get_biz_card

Retrieves details for a specific business card

get_person

Retrieves details for a specific contact person

list_biz_cards

Lists all scanned business cards

list_departments

Lists all departments in the organization

list_persons

Lists all contact persons across cards

list_tags

Lists all tags used for organizing business cards

list_users

Lists all Sansan users in the organization

search_biz_cards

Searches for business cards by name

Example Prompts for Sansan in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Sansan immediately.

"Search for a business card with the name 'Tanaka'."

"Can you list all the tag categories in our Sansan database?"

"Get the detailed person profile for the ID 'person-12345'."

Troubleshooting Sansan MCP Server with CrewAI

Common issues when connecting Sansan to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Sansan + CrewAI FAQ

Common questions about integrating Sansan MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard 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?

Yes. Each agent has its own 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?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using 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)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.