Cursor Integrations: Workspace, Work Intake, Git Hosts and Xcode

Start with the system that already owns the task. If work starts in Slack, Microsoft Teams, Linear, Jira or Notion, start the agent from that thread, issue or page. If the missing context sits in Gmail, Drive or Calendar, install only that Google Workspace pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition.. If the agent can't reach your code, connect the repository host. Native iOS work goes 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. Press Enter for the full definition. server.

That order follows where work starts, not the order you connect things in. Every intake integration ends in a Cloud Agent run, and its setup needs a connected repository provider before it finishes. If you have already connected GitHub or GitLab to Cursor, that step is done. If your code lives in Azure DevOps or Bitbucket, start with the repository-provider row.

Those runs also need a plan that includes 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. Press Enter for the full definition.. Cursor's Cloud Agents help page lists Premium or higher, a Cursor Teams or Enterprise plan, or a legacy paid plan, and says Free and Plus don't include them. Cursor's Notion page says Cursor in Notion is available to all Cursor users with a Notion Business or Enterprise plan. It doesn't mention the Cloud Agents limit, even though each Notion agent runs as a Cloud Agent.

Most tools outside this table connect through MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. instead. The setup guide has the click path for each route.

They let a team start an agent from the record that already describes the work: a Slack thread, a Linear issue, a Jira work item or a Notion page. The prompt stays next to the discussion that produced it, but review doesn't change. The agent still needs a clear repository, branch and model, and its pull request still needs a merge gate.

Cursor's Slack integration changed on 2026-07-17, and the changes help you steer a run after it starts. That day's changelog says Cursor now replies with a plan before it begins and updates its status as it works, so a wrong direction gets caught in the thread instead of in the diff. Cursor's current Slack docs narrow the plan step. Cursor posts it when you are fixing a bug or when implementation details would help, and straightforward requests skip it.

The same update lets a run start in a named multi-repo environment instead of a single default repository. When a task needs a repo outside that environment, Cursor shows a Switch repository button. The changelog says Cursor then picks up where it left off. Cursor's current Slack docs describe a fresh start instead: the button launches a new agent with the same request on the new target, from that target's default branch, and the first agent's changes don't carry over.

The update also lets Cursor read from and post to other Slack channels and threads. During a task, it can pull context from elsewhere in the workspace and post updates back to the original thread or the relevant channel.

Check the prerequisites before you choose. Notion needs a Notion Business or Enterprise plan and GitHub connected on the Cursor side. Jira needs a Cursor Teams or Enterprise plan, a commercial Jira Cloud site with Rovo enabled, and someone who is both a Jira admin and a Cursor team admin to install it.

This is where the advice at the top of this page stops holding. The Microsoft Teams install names all four repository providers, but Notion's requirements name GitHub. A team whose code lives only in Bitbucket can connect Slack and Linear and still find Notion out of reach. The click path for each is in the setup guide.

How many intake surfaces to connect depends on team size, and on a small team we would connect one. A second surface splits the record of what was asked: half the briefs in Linear, half in a Slack thread nobody can find a month later. Bigger organizations have a real reason for two, because support conversations live in Slack while roadmap work lives in Linear or Jira, and different people own them. Decide first which surface counts as the record, then link the other one into it.

Cursor released separate Google Drive, Gmail and Google Calendar plugins on August 3, 2026. Through them, an agent reads live workspace context instead of text you paste into the prompt. Each pluginA Cursor marketplace package that bundles MCP servers and skills (sometimes sub-agents and hooks); one click installs all of it into your Cursor instance. Press Enter for the full definition. has its own set of actions, so a Drive-only workflow doesn't also get permission to send mail or change an event.

The plugins install separately, from the Marketplace or the Customize page. Their listings at cursor.com/marketplace/cursor/gmail, /google-drive and /google-calendar are marked Verified by Cursor, and each gives a one-line install, such as /add-plugin gmail. The MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. definitions behind them are published in the cursor/plugins GitHub repo.

The write verbs in that table are real actions. Gmail can send, Drive can create and reorganize files (and, per its listing, share them), and Calendar can create or update events, all as the connected account. Ask for the sources and a proposed action first, then approve the external change as a separate step. The Google Workspace pluginsSeparate Cursor plugins for Gmail, Google Drive and Google Calendar that let an authorized agent read or change workspace data. Press Enter for the full definition. guide covers installation, workflows and permission boundaries.

They decide whether 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. Press Enter for the full definition. and BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. can work where your code already lives. For teams whose code and pull requests sit in Azure DevOps or Bitbucket, GitHub and GitLab support doesn't help. Connect the host before you promise cloud-agent work on those repositories.

To test that path, run one real task end to end on a repository nobody is waiting on. Then read the pull request it opens, not the agent's summary of it. A beta label mostly costs you certainty about where to look when a run fails, so let the first failure happen somewhere quiet. Both hosts carry the label today, so this holds whichever one you connect.

If review is why you are connecting, both hosts now support BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition.. Cursor's help center lists it for GitHub, GitLab, Azure DevOps and Bitbucket. Not every Bugbot feature follows: Bugbot autofix doesn't support Azure DevOps yet, so check the host's integration page for the feature you need.

Because Cursor picks the repository from defaults as well as from your message, and somebody else may have set those defaults. Name the repository in your message. In Slack and Microsoft Teams, a repository you name outranks every default.

Before you change any settings, open cursor.com/agents and check that a run exists at all, because a mention that never started an agent is a different problem.

Each integration resolves the repository in its own documented order. Microsoft Teams tries explicit repo, env, branch and model options, then names in the message text, then repositories you used recently, then the dashboard default. Slack tries the message content, then your recent agent activity, then routing rules, then the channel default, then the default repository. Linear and Jira publish their own orders on their integration pages.

In Slack, recent activity ranks above the channel default. So the repository you used last can win over the one the channel points to, and two people can get different repositories from the same sentence. If one channel keeps sending everyone's agents to the same wrong repo, suspect a routing rule or the channel default. Anyone on your Cursor team can change a channel's default with @Cursor settings, and Cursor replies under that message with who made each change.

Team-level Slack settings sit outside the thread. On Enterprise, the audit log records changes to the team's Slack default repository, branch and model, and to summary sharing (including in external channels). Check it before you rewrite the prompt again.

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. Press Enter for the full definition. solve different problems. Xcode gives the agent 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 26.3 and later expose 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. Press Enter for the full definition. server. Through it, Cursor's agent can read and edit files, trigger builds, run tests, capture SwiftUI previews and search Apple documentation. It needs a paid Cursor plan. The sidecar loop is in the mobile engineering guide.
• 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. Press Enter for the full definition. extends git blame with AI-versus-human authorship for review, debugging and compliance conversations. It is an Enterprise feature, and it stays off until a team admin turns it on.

The agent can write Swift without the bridge. What the bridge adds is the loop after the writing: the agent builds, runs tests and captures previews through Xcode, then reads the results. In Cursor's workshop on mobile development, the presenter described Xcode's build logs as a little more detailed than a terminal build's. The same workshop put the permission prompts at about five when the bridge connects, repeated each time Xcode opens. Cursor's Xcode docs mention a permission dialog but give no count.

On Enterprise, turn 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. Press Enter for the full definition. on before anyone asks for it, because of what the audit log leaves out. The audit log records security events and administrative actions, not prompts or generated code, so it cannot tell you which lines an agent wrote. Blame shows that line by line. Cursor's AI code tracking also reports AI line counts through an API and the Analytics dashboard.