How can I check the latest lead that submitted a form?

Use the `get_latest_submission` tool. It automatically retrieves the single most recent entry across all your forms, allowing you to respond instantly.

Can the agent filter out spam submissions?

Yes. Use the `mark_as_spam` tool with a Submission ID to flag suspicious entries. You can also use `mark_as_not_spam` to restore entries that were incorrectly flagged.

Is it possible to re-send data to my CRM if it failed?

Yes. Use the `refire_webhooks` tool by providing the Submission ID. This manually triggers any webhooks associated with that form, ensuring your external integrations receive the data.

Basin MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: Basin
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Basin through Vinkius, pass the Edge URL in the `mcps` parameter and every Basin 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="Basin Specialist",
    goal="Help users interact with Basin effectively",
    backstory=(
        "You are an expert at leveraging Basin 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 Basin "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 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 Basin MCP Server

Empower your AI agent to orchestrate your entire lead capture workflow with Basin, the powerful form backend for modern websites. By connecting Basin to your agent, you transform static submission data into a natural conversation. Your agent can instantly audit new form entries, identify and flag spam, retrieve specific lead details, and even manually refire webhooks without you ever touching a dashboard. Whether you're managing a single contact page or a complex lead generation network, your agent acts as a real-time submission manager, ensuring your inbound data is always clean and actionable.

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

What you can do

Submission Management — List all form submissions across your account or dive deep into specific entry details via natural language.
Spam Control — Instantly mark suspicious entries as spam or unmark false positives to maintain a high-quality lead database.
Form Oversight — List all forms in your Basin account and retrieve detailed metadata for each to map your data collection points.
Webhook Triggers — Manually refire webhooks for specific submissions to ensure your downstream integrations are correctly updated.
Real-time Auditing — Retrieve the single latest submission instantly to respond to new leads with zero delay.

The Basin MCP Server exposes 12 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 Basin to CrewAI via MCP

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

Why Use CrewAI with the Basin MCP Server

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

Basin + CrewAI Use Cases

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

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

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

Basin MCP Tools for CrewAI (12)

These 12 tools become available when you connect Basin to CrewAI via MCP:

delete_submission

Permanently delete a submission

get_account_check

Verify Basin connection

get_form

Get details for a specific form

get_latest_submission

Retrieve the single most recent submission

get_submission

Get full details for a specific submission

list_form_submissions

Helper to list submissions for a specific form

list_forms

List all forms in your Basin account

list_submissions

List all submissions across all forms

mark_as_not_spam

Convenience tool to unmark a submission as spam

mark_as_spam

Convenience tool to mark a submission as spam

refire_webhooks

Manually trigger webhooks for a specific submission

update_submission

Update submission metadata (e.g. mark as spam)

Example Prompts for Basin in CrewAI

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

"Show me the latest submission from my contact forms."

"Mark submission ID 'sub_abc123' as spam."

"List all forms in my Basin account."

Troubleshooting Basin MCP Server with CrewAI

Common issues when connecting Basin 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

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

Basin + CrewAI FAQ

Common questions about integrating Basin 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.