Developer Tools · Integration
Cursor
Add Cursor to your product for your customers, and give your AI agents governed access to it.
Cursor exposes two different APIs on api.cursor.com and they authenticate differently. The Admin API uses a team key created by a team admin and sent as HTTP basic auth with the key as the username and an empty password, covering GET /teams/members plus posted queries for daily usage data, filtered usage events and spend. Date ranges on the usage endpoints are epoch milliseconds and are capped at roughly ninety days, so longer histories have to be paged month by month and stitched together. The Background Agents API under /v0/agents takes a bearer token instead and launches an agent against a GitHub repository and branch, returning an id whose status and conversation you then poll. Usage rows are per member per day rather than per request, so cost attribution to a project has to come from your own mapping. The category nouns of services, builds and deployments are the least-wrong fit; the real objects are team members, usage events and agent runs. fastn keeps each customer's keys, handles the connection upkeep and limits which agents may launch runs or read spend.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Cursor team so usage and spend are read with their admin key.
Chart per-seat Cursor usage next to your own engineering metrics and flag unused seats.
Alert a finance owner when a team's Cursor spend crosses a threshold within a billing period.
Launch a background agent against a repository from your own workflow and track its status to completion.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent pull the last ninety days of usage events and summarise seat activity, with every admin read audited per tenant.
Have an agent launch a background agent on an approved repository and report the resulting conversation status.
Allow an agent to read members and spend without permission to change team membership.
Example prompt
Which of our Cursor seats have had no activity in the last thirty days?
Set up Cursor in 4 steps
- 01Enable the Cursor connector from your fastn dashboard.
- 02Have each customer authorise their own Cursor account, so calls run under their credentials rather than a shared key.
- 03Decide which services, builds and deployments your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Cursor integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Cursor integration without building it. Your customers connect their own Cursor account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Cursor update is not your on-call problem.
- One integration serves your product and your agents. The same governed Cursor connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
GitHub
Azure DevOps
Google CloudOften used alongside
Tools the same teams tend to run next to Cursor, across other categories.
Slack
Snowflake
Airtable
PostgreSQLCursor integration FAQ
How do I add a Cursor integration to my product?
Enable the Cursor connector in your fastn dashboard, then let each customer authenticate their own Cursor account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Cursor client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Cursor account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Cursor account and only ever sees their own services, builds and deployments. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Cursor integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent pull the last ninety days of usage events and summarise seat activity, with every admin read audited per tenant.
Who maintains the Cursor integration?
fastn does. When Cursor changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to Cursor events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in Cursor?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the Cursor integration?
A common starting point: let a customer connect their own Cursor team so usage and spend are read with their admin key. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Cursor integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Cursor does not change your per-connector cost. You can start free with 3 connected accounts.
Add Cursor to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.