> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/settings/integrations/ai-coding-tool-integrations/cursor-integration.md).

# Cursor integration

Enabling Cursor metrics

Read more about Swarmia's other [AI coding tool integrations](/settings/integrations/ai-coding-tool-integrations.md) and [understanding the impact of AI tools](/guides/understand-the-impact-of-ai-tools.md).

## Enabling Cursor metrics

You need to have Cursor's Teams or Enterprise plan. Only team administrators can create and manage API keys. [Create a Cursor admin API key](https://cursor.com/docs/api#admin-api-ai-code-tracking-api) ([**cursor.com/dashboard/team-settings**](https://cursor.com/dashboard/team-settings) → **Advanced** → **Admin API Keys** → **Create New API Key**) and copy it to [Settings / AI assistants](https://app.swarmia.com/settings/ai-assistants) in Swarmia. We fetch 365 days of historical activity data upon connection.

## Frequently asked questions

### Why do you need an admin API key? Isn't that a bit excessive?

We build our integrations with the principle of least privilege, and we'd love to ask for fewer permissions, but the [Cursor admin API key](https://cursor.com/docs/api#admin-api-ai-code-tracking-api) requires an admin key. There's no support for separate permission scopes for different API endpoints.

You can [read more about our data access here](/resources/security-and-data-retention/data-access.md#cursor-integration).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.swarmia.com/settings/integrations/ai-coding-tool-integrations/cursor-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.