Can my AI agent provision a new database in a specific edge location?

Yes. You can ask your agent to list available edge locations first, and then instruct it to create a new database in a logical group hosted in that region. Ensure you provide the target group name so the database is correctly allocated to your application fleet.

How can I quickly revoke database access if a token is compromised?

Simply ask your agent to invalidate or rotate the tokens for that specific database name. The AI will hit the /invalidate endpoint, blocking all old tokens instantly. Afterwards, you can ask for a fresh secure token with a 24-hour expiration.

Can the agent check if I am approaching my dataset limits?

Yes. When querying the details of a specific database, the agent retrieves storage metadata and group allocation facts. You can ask the AI to summarize your database sizes and flags to see which instances might need an upgrade or clean-up.

Turso MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Turso
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Connect your Turso account to any AI agent and take full control of your serverless SQLite infrastructure through natural conversation.

When paired with CrewAI, Turso becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Turso 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

Organizations & Locations — Identify root organizational tenants and lookup physical global Fly.io datacenter mappings
Databases & Groups — Enumerate the complete libSQL Edge Database registry and logical groups orchestrating DB locations
Database Management — Provision a massively distributed database, retrieve architectural metadata, and permanently delete instances
Security & Tokens — Mints secure connection tokens, list active execution JWTs, and rotate database keys to block old tokens instantly

The Turso MCP Server exposes 10 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 Turso to CrewAI via MCP

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

Why Use CrewAI with the Turso MCP Server

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

Turso + CrewAI Use Cases

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

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

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

Turso MCP Tools for CrewAI (10)

These 10 tools become available when you connect Turso to CrewAI via MCP:

create_database

Provide the organization slug, database name, and target group. Provision a massively distributed Serverless SQLite database

create_database_token

Mint a secure connection Token tied strictly to a specific DB

delete_database

This action is irreversible. Permanently deletes a global libSQL database

get_database_details

Introspect exact architectural traits of one target libSQL instance

list_database_groups

Get Turso logical groups orchestrating DB locations

list_database_tokens

List active Database execution JWT Tokens

list_databases

Enumerate the complete libSQL Edge Database registry

list_edge_locations

Lookup physical global Fly.io datacenter mappings (Locations)

list_organizations

Identify Turso Edge SQLite root organizational tenants

rotate_database_tokens

Revoke all pre-existing Tokens for a database

Example Prompts for Turso in CrewAI

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

"List all my Turso databases and their hostnames."

"Create a new database named 'user-cache' in the 'default' group."

"Invalidate all tokens for the 'legacy-db' database immediately."

Troubleshooting Turso MCP Server with CrewAI

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

Turso + CrewAI FAQ

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