Cursor is an AI-powered code editor built on VSCode. The API provides access to Cloud Agents, Admin, Analytics, and AI Code Tracking features.
Cursor is an AI-powered code editor built on VSCode. The API provides access to Cloud Agents, Admin, Analytics, and AI Code Tracking features. On Nagent, Cursor is exposed as a fully-configurable developer tools integration that any agent can call — 5 actions, and API key authentication. No code is required to wire Cursor into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Cursor to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Cursor into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Cursor, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CURSOR_GET_AGENT_CONVERSATIONTool to retrieve the conversation history for a specific cloud agent. Use when you need to view the messages exchanged between the user and the agent. Returns error with status 404 if the agent is not found or access is denied.
Input parameters
Unique identifier for the cloud agent. Must be a valid agent ID in UUID format with 'bc-' prefix (e.g., 'bc-550e8400-e29b-41d4-a716-446655440000'). Agent IDs can be obtained from the List Agents action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CURSOR_GET_METool to retrieve API key information including the key name, creation date, and owner email. Use when you need to verify API key details or validate authentication.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CURSOR_LIST_AGENTSTool to retrieve a paginated list of all Cursor Cloud agents. Use when you need to view existing agents, their status, or iterate through agents with pagination.
Input parameters
Number of cloud agents to return. Must be between 1 and 100.
Pagination cursor from the previous response to fetch the next page of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CURSOR_LIST_MODELSTool to retrieve the list of available AI models in Cursor. Use when you need to discover which models are available for API requests.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CURSOR_LIST_REPOSITORIESTool to list GitHub repositories accessible to the authenticated user. Use when you need to retrieve all repositories the user has access to through their Cursor account.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 76 agents privately built on Nagent that already use Cursor.
Build on Nagent
Connect Cursor to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Cursor, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Cursor is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Cursor is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Cursor steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Cursor event fires, the agent kicks off automatically.
Every Cursor action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Cursor ships with 5 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Cursor together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Cursor-based workflows tailored to your business.