The Cursor integration connects Jet Admin's MCP server to Cursor, so you can query your Jet Admin data sources and trigger configured actions directly from an AI coding session — without leaving your editor. Cursor can read your app's tables, fields, and records as context while you build or debug.

Because the connection goes through Jet Admin's own permission model, an agent working in Cursor only sees what its connected role allows, and any action it triggers is scoped and logged in the audit log the same as if a person had performed it. That makes it safe to let an AI agent help with real internal-tool work.

Key benefits

• Build faster with real data. Let Cursor see your actual Jet Admin records instead of guessing at schema.
• Trigger actions from your editor. Run configured Jet Admin actions without switching to the app.
• Stays within your permissions. Everything the agent does is scoped by role and recorded in the audit log.
• No extra setup. Connect once through MCP and reuse it across projects.

How to connect Jet Admin with Cursor

1. In Jet Admin, go to Data Sources (or Integrations) and select Cursor / MCP.
2. Generate an MCP connection URL or token for your Jet Admin workspace.
3. In Cursor, add Jet Admin as an MCP server using that URL or token.
4. Choose which role the connection should use, to control what data and actions are accessible.
5. Start a session in Cursor — it can now query your Jet Admin data and trigger actions directly.