AI Provider for Cursor

Description

This plugin connects WordPress to Cursor Cloud Agents so the WordPress AI Client can generate text through the cursor provider.

This is an unofficial, third-party connector. It is not affiliated with, endorsed by, or sponsored by Cursor or Anysphere. “Cursor” is a trademark of Anysphere, Inc.

Features:

• Registers a cursor provider with the WordPress AI Client
• Text generation via Cursor Cloud Agents (no-repository agents)
• Dynamic model discovery from GET /v1/models
• API key managed by WordPress Settings → Connectors (or CURSOR_API_KEY)
• Plugin settings page for polling options, default model, and archive behavior

Requirements:

• WordPress 7.0 or higher (AI Client and Connectors API in core)
• PHP 7.4 or higher
• A Cursor API key from cursor.com/dashboard/api

External services

This plugin relies on the Cursor Cloud Agents API, operated by Anysphere, Inc. (cursor.com). Without a valid Cursor API key and an active internet connection, the plugin cannot generate text or list models.

When data is sent

Data is transmitted to Cursor when:

• WordPress or custom code uses the WordPress AI Client with the cursor provider (for example summarization, title generation, excerpts, or your own AiClient::prompt() calls).
• The plugin discovers available models for your account (for example when loading provider metadata).
• Optional: after a successful text generation, if Archive agent after run is enabled, the plugin asks Cursor to archive the finished Cloud Agent.

Saving your API key in WordPress stores it locally via Settings → Connectors. The key is sent to Cursor only inside authenticated API requests, not to the plugin author.

What is sent

• Your Cursor API key (HTTP Basic authentication on every API request).
• Prompt text built from user and assistant messages, including any system instruction and any post or content text included in the AI request.
• Optional model ID when you or calling code selects a specific model.
• Agent and run identifiers when polling run status or archiving an agent.

API endpoints used

All requests go to https://api.cursor.com:

• GET /v1/models — list models available to your account
• POST /v1/agents — create a Cloud Agent and start a text-generation run
• GET /v1/agents/{agentId}/runs/{runId} — poll run status and retrieve the generated text
• POST /v1/agents/{agentId}/archive — optional cleanup after a successful run

Service links

• Cursor website: https://cursor.com/
• Cloud Agents API documentation: https://cursor.com/docs/cloud-agent/api/endpoints
• API keys dashboard: https://cursor.com/dashboard/api
• Terms of Service: https://cursor.com/terms-of-service
• Privacy Policy: https://cursor.com/privacy

Usage may be subject to Cursor account limits and billing. This plugin does not include a Cursor subscription.

Privacy

The Cursor API key is managed by WordPress Settings → Connectors (connectors_ai_cursor_api_key) unless you configure CURSOR_API_KEY in wp-config.php or as an environment variable. Those constant and environment sources override the database value. This plugin does not read that Connectors option; WordPress core injects credentials into the AI Client.

This plugin stores only Cursor-specific behavior options in ai_provider_for_cursor_settings (default model, poll timeout, poll interval, archive after run).

When AI features use the Cursor provider, prompt content is sent to Cursor’s servers as described in External services above. This plugin does not send analytics or telemetry to the plugin author.

On uninstall, the plugin settings option is removed. The Connectors API key option is left for WordPress / Connectors to manage.

Configuration

1. Create a Cursor API key at cursor.com/dashboard/api

2. Open Settings → Connectors, find the Cursor card, and enter the API key

   • wp-config.php (recommended for production): add this line to wp-config.php above /* That's all, stop editing! */:

     define( ‘CURSOR_API_KEY’, ‘your-cursor-api-key-here’ );

• You can also set a CURSOR_API_KEY environment variable (same name). Environment and the PHP constant both override the database value.
  1. Optionally open Settings → AI Provider for Cursor to set:
• Default model ID (for example composer-2)
• Poll timeout — maximum seconds to wait for Cursor to finish
• Poll interval — how often (in seconds) WordPress asks Cursor whether the run is finished
• Archive agent after run — whether to clean up the finished Cloud Agent on Cursor’s side
  1. Confirm the Cursor connector shows as connected on Settings → Connectors