Compatible with every major AI agent and IDE
What is the ElectricSQL (Sync Engine) MCP Server?
Connect your ElectricSQL sync engine to any AI agent to stream data directly from Postgres into your conversation context. This server leverages the Electric HTTP Sync API to fetch 'shapes' of data efficiently.
What you can do
- Real-time Sync — Fetch data from Postgres tables with support for initial snapshots and incremental updates using log offsets.
- Shape Management — Define specific subsets of data (shapes) using SQL-like WHERE clauses and precise column selection.
- Live Streaming — Enable long-polling or Server-Sent Events (SSE) to keep your agent updated as data changes in the database.
- Complex Filtering — Use POST-based subset snapshots to handle complex WHERE clauses without hitting URL length limits.
- Pagination & Limits — Efficiently browse large datasets with built-in limit, offset_rows, and order_by support.
How it works
- Subscribe to this server
- Provide your Electric Service URL (e.g., your local or cloud Electric endpoint)
- Start querying your Postgres data directly from Claude, Cursor, or any MCP client
Who is this for?
- Developers — build AI-powered tools that need live access to application data without complex backend plumbing.
- Data Engineers — inspect and sync specific database 'shapes' for analysis or debugging via natural language.
- Product Teams — monitor real-time system state or user activity directly within the AI chat interface.
Built-in capabilities (2)
Use offset=-1 for initial sync. Sync a shape of data out of Postgres via GET
Sync a shape of data out of Postgres via POST (Subset Snapshots)
Why CrewAI?
When paired with CrewAI, ElectricSQL (Sync Engine) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ElectricSQL (Sync Engine) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
ElectricSQL (Sync Engine) in CrewAI
ElectricSQL (Sync Engine) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ElectricSQL (Sync Engine) to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for ElectricSQL (Sync Engine) in CrewAI
The ElectricSQL (Sync Engine) 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. All 2 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
ElectricSQL (Sync Engine) for CrewAI
Every tool call from CrewAI to the ElectricSQL (Sync Engine) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I perform an initial sync of a database table?
Use the get_shape tool and set the offset parameter to -1. This triggers ElectricSQL to send the full initial snapshot of the specified table.
What should I do if my SQL WHERE clause is too long for a standard URL?
You should use the post_shape tool. It sends the filtering criteria in the request body, which prevents '414 Request-URI Too Long' errors when using complex logic.
Can the AI agent receive updates automatically when data changes in Postgres?
Yes! By setting the live parameter to true in get_shape, the agent can establish a long-polling connection to stream incremental changes as they happen.
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.
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.
Explore More MCP Servers
View all →
Troops
7 toolsAutomate HR and recruitment workflows via Troops — manage job offers, candidates, contracts, and timesheets directly from your AI agent.

MyTime
10 toolsManage business operations via MyTime — track appointments, staff, and services directly from your AI agent.

Chess.com Global Intelligence
12 toolsThe definitive server for Chess.com — track player ratings, historical games, and daily puzzles via AI.

Skalin
12 toolsManage accounts, contacts, and customer health on Skalin with AI agents.
