Connect your data to Cursor

Query your databases and explore schemas without leaving your code editor.

What Cursor can do with Sequel

Schema exploration in your editor

Ask Cursor to describe your database schema, find the right table for a feature, or understand relationships between tables — all without switching to another tool or reading through migrations.

Query data while you code

Need to check actual data while implementing a feature? Ask Cursor to pull examples from your connected databases. No more copy-pasting connection strings into a separate SQL client.

Catch data issues before they ship

Run queries against your staging or production database from inside the editor. Validate assumptions about data shape, volume, or edge cases while the code is still in front of you.

Example prompts

Everything you can ask Cursor about your data.

Ask in plain English. Sequel turns it into a query, runs it read-only, and Cursor hands back the answer. No SQL, no dashboards, no CSV exports.

Connect Cursor
What you can ask Cursor
  • What columns does the `users` table have and what are the constraints?
  • Show me 5 example rows from the `orders` table
  • How many records are in each table in our production database?
  • Find all foreign key relationships for the `subscriptions` table
  • What's the average query response time for our most common API endpoints?

Setup

Add Sequel to Cursor

Drop the Sequel MCP server into Cursor, then ask it anything about your connected data. Sequel is read-only by default and shows each query before it runs.

.cursor/mcp.json

{
  "mcpServers": {
    "sequel": {
      "url": "https://api.sequel.sh/mcp",
      "headers": {
        "Authorization": "Bearer sql_your_api_key"
      }
    }
  }
}

Install

Install Sequel MCP in Cursor

Pick your app and Sequel installs itself: a one-click link where the client supports it, that client’s own few steps where it doesn’t. Every route signs in with your Sequel account over OAuth, so there is no API key to copy and nothing to keep in sync.

Already have an MCP client?

https://api.sequel.sh/mcp

Add it as a remote (streamable HTTP) server and sign in when prompted. Skills come with it; nothing else to install. Manual setup per client

Add Sequel to Cursor

One click: the button above opens Cursor with Sequel pre-filled, and Cursor signs you in with your Sequel account. There is no key to paste.

Data sources

Connect any source to Cursor

Frequently asked questions

Does this work with Cursor Agent and Cursor Chat?

Yes. Once the MCP config is in your .cursor/mcp.json, Sequel tools are available in both Cursor Chat and Cursor Agent. The agent can call multiple tools in sequence to answer complex questions.

Should I use a project-level or global MCP config?

Use a project-level .cursor/mcp.json for team repos so all collaborators share the same MCP setup. For personal access, add the config globally at ~/.cursor/mcp.json instead.

Can Cursor modify my database through Sequel?

Sequel's query tools are read-only by default. The workbench tool can run Python code, which could write to files, but it runs in an isolated sandbox without direct database write access.

How do I share the Sequel MCP config with my team?

Commit .cursor/mcp.json to your repo. Each team member needs their own Sequel API key — replace the value of the Authorization header with their personal key from Settings → API Keys.

Put your data inside Cursor

Connect in minutes — then ask across all your data, not just one source.