Cursor Integration
Live

Cursor agents on
your GTM graph.

Cursor integration on Gyri connects Cursor Cloud Agents and IDE MCP to CRM, email, Slack, and engineering context — cited synthesis beyond the codebase.

BYOK Cursor Cloud Agents in Gyri workflows — MCP federates the IDE with CRM, email, and Slack. recall prior diligence, fetch live context, and promote cited insights beyond the codebase.

Start free trial All integrations

Related: MCP for Claude & Cursor · Workflow automation · All integrations

Federation path

Cursor Cloud Agents joins
your full stack.

Cursor Cloud Agents
Gyri graph
CRM · comms · docs
What connects

Cursor Cloud Agents data
in your graph.

Data

BYOK cursor_agent_api credential

Data

Workflow external_agent_run nodes

Data

MCP for Cursor IDE

Data

Cursor Cloud Agents API (api.cursor.com)

The problem

Cursor Cloud Agents alone
is not enough.

01

Cursor sees code — not pipeline

Composer excels in the repo — but cannot cite HubSpot stage, renewal email threads, or Zendesk themes without Gyri MCP.

02

Cloud agent output evaporates

Cursor Cloud Agent runs finish in the IDE — findings do not promote to team-wide institutional memory.

03

GTM research in the wrong tool

RevOps pastes Slack and CRM into Cursor chat — no fetch from federated graph or multihop joins with citations.

Before / after

Cursor alone vs
Cursor + Gyri.

Cursor alone @-mention files and hope. GTM context pasted manually. Session ends — context gone.
Cursor + Gyri recall team insights. fetch live CRM + email. promote cited findings to the graph.
With Gyri

Federated, cited,
agent-ready.

MCP in Cursor

IDE meets company graph

Gyri MCP in Cursor — search, graph, synthesis, and write-back with workspace permissions.

Workflow agents

Cloud agents as DAG steps

external_agent_run invokes Cursor Cloud Agents alongside stored Gyri agents and serverless compute.

recall + fetch

Context before codegen

Agents recall prior account insights and fetch live CRM rows — engineering decisions grounded in GTM reality.

promote findings

Research persists

Competitive and customer intel from Cursor promotes to the insight graph — available to Sales and CS.

Thinking verbs

Engineering meets
institutional memory.

Cursor agents use the same think verbs as Claude Desktop — recall before research, promote after.

think verb=recall

Prior cited conclusions before new IDE research

think verb=fetch

Hydrate live graph records into agent context

think verb=promote

Commit durable findings for Sales and CS

think verb=want

Signal whitespace and escalation intent

MCP for Claude & Cursor · Workflow automation

Competitor matrix

Cursor vs Cursor + Gyri

Start free trial
Use cases

Built for
GTM operators.

RevOps in the IDE

Query pipeline risk across CRM, email, and Slack from Cursor — cite every claim before updating forecasts.

Incident + GTM joins

fetch Datadog context alongside support themes and deal ARR — cited postmortem briefs in one agent session.

Workflow handoff

Trigger Cursor Cloud Agent from graph workflows — want new automations while agents run in parallel.

Works with

Federate alongside
native connectors.

Anthropic (Claude)
OpenAI
GitHub
Linear
Slack
Setup

Connect in
minutes.

Settings → API keys → Cursor Agent API — paste your Cursor API key. Use external_agent_run in workflows or connect Gyri MCP in Cursor settings.

1. Start a free trial at app.gyri.io · 2. Open Settings → API keys · 3. Create a stored agent and connect MCP for cited federated answers.

Connect Cursor Cloud Agents Setup guide

Connect Cursor to your workspace graph.

Free trial — Cursor API key, MCP, and federated GTM context in the IDE.

Start free trial Browse integrations

Frequently asked questions

How do I connect Cursor to Gyri?

Add your Cursor API key in Settings → API keys → Cursor Agent API. Connect Gyri MCP in Cursor IDE settings.

Can workflows invoke Cursor Cloud Agents?

Yes. external_agent_run nodes call Cursor Cloud Agents alongside stored Gyri agents and serverless compute.

Does Cursor get CRM context via Gyri?

Yes. MCP federates live HubSpot, Outlook, Slack, and more — recall and fetch hydrate GTM context in the IDE.