Skip to main content

​
Quick Install

Add VexiData to Cursor Click the button above to add VexiData to Cursor automatically (requires Cursor v1 or later). You’ll be prompted to authorize access after installation.

​
Prerequisites

  • Cursor v1 or later installed
  • A VexiData account with at least one connected database

​
Manual Setup

1

Copy your MCP Server URL

Your MCP Server URL is:
https://vexidata.com/mcp
You can also find this in Settings > AI Integrations in your VexiData AI Integrations page.
2

Add VexiData as an MCP server in Cursor

  1. Open Cursor
  2. Go to Settings (gear icon) > MCP
  3. Click Add new MCP server
  4. Select SSE as the transport type
  5. Enter a name (e.g., “VexiData”)
  6. Paste your MCP Server URL
  7. Click Add
3

Authorize the connection

Cursor will open a browser window to VexiData for authorization. Review the requested permissions and click Approve.Once authorized, you’ll see VexiData listed as a connected MCP server in Cursor’s settings.
4

Start querying your data

In Cursor’s AI chat or inline editor, you can now reference your database. For example:
  • “What columns does the users table have?”
  • “Write a query to get the top 10 customers by total spend”
  • “Generate a migration to add an is_active column to the orders table”
Cursor’s AI will use VexiData to access your schema and run queries against your connected databases.

​
Manual configuration

If you prefer to configure MCP servers manually, add VexiData to your Cursor MCP configuration file (.cursor/mcp.json in your project or ~/.cursor/mcp.json globally): 
{
  "mcpServers": {
    "vexidata": {
      "url": "https://vexidata.com/mcp"
    }
  }
}
Restart Cursor after saving the file.

​
Troubleshooting

  • Check that your VexiData account has an active session — try logging in again at vexidata.com
  • Verify the MCP Server URL is correct in Cursor settings
  • Try removing and re-adding the MCP server
  • Make sure your default browser is set and working
  • Try copying the MCP URL and adding it manually via the config file method
  • Check that no browser extensions are blocking the redirect
  • Verify you have at least one database connected in VexiData under Data Sources
  • Check that your database connection is active and the schema has been analyzed
  • Try asking specifically about a table name to confirm the connection is working