How to Use the ElectricSQL (Sync Engine) MCP in Cursor

Q: Can the Cursor agent write data back using ElectricSQL (Sync Engine)?

No, this server focuses on reading data. The agent uses getshape and postshape to sync Postgres data shapes to its context, but it cannot run arbitrary write operations or modify database tables directly.

Q: How does the Cursor agent use ElectricSQL (Sync Engine) to write tests?

The agent uses getshape to pull real Postgres records into the editor. It then writes unit tests using those actual database shapes, ensuring your test suites run against realistic payloads instead of outdated mocks.

Q: What does offset=-1 mean in getshape?

Passing offset=-1 to getshape tells the ElectricSQL sync engine to return the entire initial snapshot of the requested Postgres shape. Subsequent requests use the returned offset to get only the changed rows.

Sync real-time Postgres data shapes directly into Cursor to generate code using live database context.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect ElectricSQL (Sync Engine) MCP to Cursor

Create your Vinkius account to connect ElectricSQL (Sync Engine) to Cursor 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 ElectricSQL (Sync Engine) with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Query Postgres shapes directly from the Cursor agent

The `get_shape` tool pulls live Postgres data shapes into your Cursor agent session using ElectricSQL's HTTP Sync API. The agent calls this tool with an offset of -1 to read the initial state of any table and write code against actual data. This eliminates the need to write mock data or stubs while building features. Your agent sees the real database schema and live rows, generating precise code that matches your production database structure.

Filter database subsets using this MCP Server

The `post_shape` tool allows your Cursor agent to define and request specific database subsets from Postgres on the fly. The agent sends a POST request to establish a shape, keeping its context focused only on relevant rows. By using this MCP Server, you avoid polluting Cursor's active workspace context with massive, irrelevant database dumps. The agent retrieves exactly what it needs to write, test, or debug your active file.

Keep your code context in sync with Postgres changes

The `get_shape` tool enables Cursor to track database mutations by retrieving delta updates from the ElectricSQL sync engine. The agent uses the returned offset to poll for changes, ensuring it never writes code based on stale data. This real-time visibility helps when you are debugging API endpoints that interact with Postgres. Cursor can inspect the actual database state before and after you run your local server.

Setup guide

Set up ElectricSQL (Sync Engine) MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the ElectricSQL (Sync Engine) MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent ElectricSQL (Sync Engine) transactions." If the MCP tools are loaded correctly, Cursor will call the ElectricSQL (Sync Engine) tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "electricsql-sync-engine-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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 ElectricSQL. 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 ElectricSQL (Sync Engine) 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 ElectricSQL (Sync Engine) MCP in Cursor

Create a .cursor/mcp.json file in your project root and add the MCP Server config. Specify the command and arguments to run the server, ensuring it points to your local ElectricSQL sync engine endpoint.

No, this server focuses on reading data. The agent uses `get_shape` and `post_shape` to sync Postgres data shapes to its context, but it cannot run arbitrary write operations or modify database tables directly.

The agent uses `get_shape` to pull real Postgres records into the editor. It then writes unit tests using those actual database shapes, ensuring your test suites run against realistic payloads instead of outdated mocks.

Passing offset=-1 to `get_shape` tells the ElectricSQL sync engine to return the entire initial snapshot of the requested Postgres shape. Subsequent requests use the returned offset to get only the changed rows.

All synced Postgres shapes are read directly through your local environment. Your database records never go to external servers, ensuring complete privacy.

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