Integrations · Cursor
Guild agents create and drive Cursor cloud coding agents, submit prompts, and retrieve pull request outcomes without any manual intervention. API keys are stored and injected by Guild’s credential proxy, so agent code never sees the secret. Credential policies and audit let you control exactly which operations each agent may perform.
Book a demo
See how teams govern agents that use Cursor.
Talk to sales
Get access to Guild, then connect Cursor to your first agent.
What the Cursor integration exposes
The integration provides tools to create agents and enqueue their initial runs, retrieve durable agent metadata for idempotent recovery, fetch per-run and total token usage, list available models, and archive, unarchive, or permanently delete agents. A dedicated get-run tool lets a Guild agent poll run status until a result is ready.How it works
1
Generate a Cursor API key
Go to cursor.com/dashboard/integrations to generate an API key. The key starts with “crsr_” and must be converted to base64 before use.
2
Connect the credential in Guild
In Guild, go to Access & setup > Credentials, click Connect, select cursor-cloud-agents, and paste the base64-encoded key into the API Key field. See Credentials for workspace, member, and agent-scoped options.
3
Import tools in your agent
Import CursorCloudAgentsTools from the integration package and spread it into your agent’s tools object. Use pick() from the SDK tools to include only the tools your agent needs.
Why Cursor agent access needs governing
Cursor tools can create agents, enqueue runs, and permanently delete resources. Guild stores the API key server-side and injects it through its credential proxy, so agent code never handles the secret directly. You can scope a credential to one workspace, one member, or one installed agent, ensuring the key is never shared beyond its intended audience. Credential policies let you write ALLOW and DENY rules that the proxy enforces before any request reaches Cursor. A DENY rule always wins over an ALLOW rule, so you can block destructive operations like delete while permitting reads and runs. Unscoped rules apply to every agent and workspace that uses the credential; scoped rules target a single agent or workspace, letting you give different agents different permissions on the same key.About the Cursor integration
This integration gives Guild agents programmatic control over Cursor cloud coding agents. Agents can create new Cursor agents, submit prompts, monitor run status, and retrieve pull request outcomes. Token usage tracking per run is also available. The integration isguildai~cursor-cloud-agents.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Get an API key
Go to cursor.com/dashboard/integrations to generate an API key. The key starts with “crsr_”. You need to change it to base64 and paste it on credentials API KEY.
2
Connect Cursor
In Guild, go to Access & setup > Credentials, click Connect, select cursor-cloud-agents, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thecursor_cloud_agents_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~cursor-cloud-agents:
Frequently asked questions
Can my Guild agent track how many tokens a Cursor run used?
Can my Guild agent track how many tokens a Cursor run used?
Yes. The cursor_cloud_agents_get_agent_usage tool returns per-run and total token usage for an agent.
Does the integration receive webhook events from Cursor?
Does the integration receive webhook events from Cursor?
No. The catalog entry for guildai~cursor-cloud-agents lists no webhook events, so agents must poll run status using the get-run tool.
How does Guild keep my Cursor API key out of agent code?
How does Guild keep my Cursor API key out of agent code?
Guild’s credential proxy stores the key and adds it as a bearer token in the Authorization header on each outbound request. Agent code never sees the secret. See Credentials for details on how the proxy works.
Can I limit one agent to read-only Cursor operations and let another create and delete agents?
Can I limit one agent to read-only Cursor operations and let another create and delete agents?
Yes. Credential policies support ALLOW and DENY rules scoped to individual agents, so you can permit only list and get operations for one agent while allowing create and delete for another, all on the same connected credential. See Credential policies for rule syntax.
Put a governed agent on Cursor this week
Book a demo
See how teams govern agents that use Cursor.
Talk to sales
Get access to Guild, then connect Cursor to your first agent.