Guide
Cursor Integrations: Slack, Linear, Jira, Notion, Xcode and Git Hosts
Cursor integrations fall into three groups: work intake surfaces like Slack, Linear, Jira and Notion; repository providers such as Azure DevOps and Bitbucket; and developer-tool integrations like Xcode and Cursor Blame. Use them when the agent needs the same work queue, source host, build tool or review signal your team already uses.
On this page
Which Cursor integration should I start with?
Start with the system that already owns the task. If work starts in Slack, Linear, Jira or Notion, route the agent from that conversation or issue. If the blocker is source access, connect the repository provider. If the work is native iOS, connect Xcode through MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. before you ask the agent to build or test.
- Job
- Start work from a conversation
- Cursor integration
- Slack
- What it gives the agent
- Mention
@cursorwith a prompt and launch a Cloud Agent from the Slack thread.
- Job
- Delegate issue work
- Cursor integration
- Linear or Jira
- What it gives the agent
- Assign an issue to Cursor or mention
@Cursorso a Cloud Agent works from the ticket context.
- Job
- Turn docs and specs into work
- Cursor integration
- Notion
- What it gives the agent
- Delegate pages, tasks and comments to agents that run on the Cursor SDK runtime.
- Job
- Connect non-GitHub repositories
- Cursor integration
- Azure DevOps or Bitbucket
- What it gives the agent
- Let Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. clone code, work on branches and open pull requests against those hosts.
- Job
- Run native iOS checks
- Cursor integration
- Xcode
- What it gives the agent
- Expose builds, tests, SwiftUI previews and Apple documentation search through Xcode's MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. server.
- Job
- Review authorship
- Cursor integration
- Cursor BlameAn augmented git blame that records line-level human and agent co-authorship, so you can trace which code was written by AI versus a person.
- What it gives the agent
- Show AI versus human contribution signals in git history for review and compliance conversations.
| Job | Cursor integration | What it gives the agent |
|---|---|---|
| Start work from a conversation | Slack | Mention @cursor with a prompt and launch a Cloud Agent from the Slack thread. |
| Delegate issue work | Linear or Jira | Assign an issue to Cursor or mention @Cursor so a Cloud Agent works from the ticket context. |
| Turn docs and specs into work | Notion | Delegate pages, tasks and comments to agents that run on the Cursor SDK runtime. |
| Connect non-GitHub repositories | Azure DevOps or Bitbucket | Let Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. clone code, work on branches and open pull requests against those hosts. |
| Run native iOS checks | Xcode | Expose builds, tests, SwiftUI previews and Apple documentation search through Xcode's MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. server. |
| Review authorship | Cursor BlameAn augmented git blame that records line-level human and agent co-authorship, so you can trace which code was written by AI versus a person. | Show AI versus human contribution signals in git history for review and compliance conversations. |
Pick the integration by where the missing context or action already lives.
How do Slack, Linear, Jira and Notion change agent intake?
These integrations are intake surfaces. They let a team start an agent from the artifact that already describes the work: a Slack thread, a Linear issue, a Jira work item or a Notion page. That keeps the prompt close to the discussion, but it does not remove review. The agent still needs a clear repo, branch, model choice and merge gate.
Mention @cursor with a prompt. Use it for follow-ups born in a thread, then review the agent run and pull request before merge.
Delegate an issue or mention Cursor in comments. Good tickets become better agent briefs, so keep acceptance criteria and repo context in the issue.
Use it when specs, tasks or review comments live in Notion. The integration is built on the Cursor SDK runtime, so treat it like a programmed agent surface.
Teams already has a dedicated guide on this site. The pattern is the same as Slack: mention Cursor, pin repo/branch/model when needed, then review the run.
What do Azure DevOps and Bitbucket add?
Repository-provider integrations decide where Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. and review tooling can actually operate. GitHub and GitLab are not the whole market; Azure DevOps and Bitbucket matter for teams whose code and pull requests already live there. Connect the host before promising cloud-agent work on those repositories.
- Provider
- Azure DevOps
- Documented scope
- Connects Azure DevOps Services repositories so Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. can clone code, work on branches and open pull requests.
- Adoption note
- Cursor labels the integration public beta.
- Provider
- Bitbucket
- Documented scope
- Connects Bitbucket Cloud repositories for Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. and BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs..
- Adoption note
- Cursor labels the integration public beta.
| Provider | Documented scope | Adoption note |
|---|---|---|
| Azure DevOps | Connects Azure DevOps Services repositories so Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. can clone code, work on branches and open pull requests. | Cursor labels the integration public beta. |
| Bitbucket | Connects Bitbucket Cloud repositories for Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. and BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs.. | Cursor labels the integration public beta. |
Public beta means test the full branch, PR and review path before making it a team default.
Where do Xcode and Cursor Blame fit?
Xcode and Cursor BlameAn augmented git blame that records line-level human and agent co-authorship, so you can trace which code was written by AI versus a person. solve different problems. Xcode gives the agent access to native build and test actions it cannot infer from code alone. Cursor Blame gives reviewers an authorship signal after code exists, so they can see where AI-assisted changes entered the history.
- Xcode: Xcode 26.3+ exposes a built-in MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. server. Cursor's agent can read and edit files, trigger builds, run tests, capture SwiftUI previews and search Apple documentation.
- Cursor BlameAn augmented git blame that records line-level human and agent co-authorship, so you can trace which code was written by AI versus a person.: extends git blame with AI-versus-human authorship signals, useful for review, debugging and compliance conversations.
Integrations move context and actions closer to the agent. They do not decide what ships. Keep the same tests, pull-request review and owner approval you would require if a developer had made the change by hand.
Frequently asked questions
Does Cursor support Slack, Linear and Jira?
Yes. Cursor documents integrations for Slack, Linear and Jira that let teams start Cloud Agents from those work surfaces. Mention Cursor or delegate the issue, then review the resulting agent run and pull request.
Can Cursor Cloud Agents work with Azure DevOps or Bitbucket?
Yes, with current caveats. Cursor documents Azure DevOps Services support for Cloud Agents and Bitbucket Cloud support for Cloud Agents and Bugbot. Both docs identify the integrations as public beta, so test branch, PR and review behavior before a broad rollout.
What does the Xcode integration let Cursor do?
Xcode 26.3+ exposes a built-in MCP server. Cursor's agent can use it to read and edit files, trigger builds, run tests, capture SwiftUI previews and search Apple documentation from the agent workflow.
What is Cursor Blame for?
Cursor Blame adds AI-versus-human authorship signals to git history. Use it in review and compliance conversations when you need to understand where AI-assisted code entered a codebase.
Sources & last verified
- Cursor Slack integration
- Cursor Linear integration
- Cursor Jira integration
- Cursor Notion integration
- Cursor Azure DevOps integration
- Cursor Bitbucket integration
- Cursor Xcode integration
- Cursor Blame
- Cursor Microsoft Teams
Cursor ships frequently. Facts verified against primary sources on June 30, 2026.