Dinobase integrates with Cursor via MCP. Once connected, Cursor's AI agent can query all your synced business data while you code.
dinobase install cursorInstalls Dinobase via uv, runs dinobase init, and writes CLI usage instructions to AGENTS.md in your current directory. Then add your connectors:
dinobase add stripe --api-key sk_test_...
dinobase add hubspot --api-key pat-...
dinobase syncSee Connectors for the full list of 100+ supported connectors, and Syncing & Scheduling for background sync options.
Cursor's agent can then run shell commands like dinobase info, dinobase describe stripe.customers, and dinobase query "SELECT ..." to answer questions about your data.
To re-run the setup step: dinobase install cursor from your project root (safe to run multiple times — replaces the existing block).
The agent will:
- Run
dinobase infoto discover available data - Run
dinobase describe <table>to understand columns and types - Run
dinobase query "<sql>"to execute SQL (DuckDB dialect) - For mutations (UPDATE/INSERT),
queryreturns a preview — the agent runsdinobase confirm <id>to execute
If you prefer MCP, run dinobase mcp-config cursor to get the JSON config, then add it to .cursor/mcp.json in your project root.
| Command | Description |
|---|---|
dinobase info |
Database overview — connectors, tables, row counts |
dinobase describe <table> |
Table schema, column types, and sample data |
dinobase query "<sql>" |
Execute SQL queries (DuckDB dialect) |
dinobase refresh [connector] |
Re-sync a connector to get fresh data |
dinobase confirm <id> |
Execute a pending mutation |
dinobase cancel <id> |
Cancel a pending mutation |
- Getting Started — Full setup walkthrough
- Connectors — Add your business data
- Querying Data — SQL patterns and cross-connector joins
- Syncing & Scheduling — Keep data fresh
- Schema Annotations — Add context for AI agents
- MCP Integration — How the MCP server works
- MCP Tools Reference — Detailed tool schemas