Cursor

An AI code editor with coding agents that write, edit and review code across your repositories for product teams.

Summary Features Pricing Competitors2 How to use

Cursor API

Sign in: API key. API key; API access on: Cloud Agents API: All Plans (Beta); Admin, Analytics, AI Code Tracking, Bugbot APIs: Enterprise teams only; Origin API: Early BetaSource

Checked on 2026-10-10 in the developer documentation.

How to automate Cursor

Native integrations

The docs list integrations with Slack, Microsoft Teams, Jira, Linear, Notion, GitHub, GitLab, Azure DevOps and Bitbucket. A simple first flow: tag Cursor on a Linear ticket, let a cloud agent open a pull request in GitHub, and review it before the stand-up.

API and webhooks

Cursor documents a public API with a Cloud Agents API, an Admin API, analytics endpoints and an AI Code Tracking API. Use the Cloud Agents API to start an agent from your own system, for example when a support ticket is tagged as a confirmed bug. Check the docs for webhook events before you plan an event-driven flow.

MCP server

Cursor does not run an MCP server of its own. It is an MCP client: you add servers in an mcp.json file or from the settings, and the agent can then use tools from other products. Sketch, Penpot and Upwork all document MCP servers that work with Cursor, so a design file or a hiring task can sit inside the same agent session.

Built-in automation

Cursor has Automations, plus hooks, skills and rules for repeatable behaviour. A good starting point is a rule file that states your testing and naming conventions, so every agent run follows the same standard.