• TidioReply faster to tickets across all channels
  • LyroHire AI to handle customer servicecheck
  • Hubi AIRun on-brand marketing with an AI coworker
  • LabsTidio LabsGet a custom AI solution built by experts
  • Master AgentOrchestrates every channel
  • AI Voice AgentResolves calls on its own
  • Lyro for Zendesk
  • Lyro for Freshdesk
  • Lyro for Salesforce
  • Lyro for HubSpot
Browse all integrationsarrow_forward
  • Borrowell83% resolved
  • GameBoost86% automated
  • Cove Smart70% self-service
  • Secureframe59% automated
See all customer storiesarrow_forward
  • AI in E-Commerce in 2026Free report on the new shopping funnel
  • Shadow AIFree report on the hidden AI habit
  • AI in Insurance in 2026Free report on AI in insurance
See all reportsarrow_forward
  • Features
  • Pricing
Talk to salesGet started
Lyro wordmark

Product

  • Features
  • Master Agent
  • AI Voice Agent
  • Integrations
  • Pricing
  • Copilot

Resources

  • Blog
  • Customer Stories
  • Reports
  • AI in Ecommerce Report
  • Docs

Company

  • Contact
  • Book a Demo

Legal

  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement

4.7/5on G2G2 logo

SOC 2 Type II · GDPR · CCPA

© 2026 Lyro by Tidio. All rights reserved.

Cursor

Cursor MCP integration

Pages through Cursor Cloud agents and their status, reads one agent's message history, and confirms models, repos and key ownership.

Connect CursorSee all integrations

5actions available

  1. Home/
  2. Integrations/
  3. Cursor

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Get agent conversation

    Lyro retrieves the conversation history for a specific cloud agent. Support teams debug agent behavior and troubleshoot issues without accessing external logs.

  • List github repositories

    Lyro lists GitHub repositories accessible to the authenticated user. Agents quickly reference code repositories during technical support conversations.

  • List agents

    Lyro retrieves a paginated list of all Cursor Cloud agents. Support teams manage and monitor multiple autonomous agents from a single interface.

See all 5 actions

How businesses use Cursor + Lyro

Each card is one request a support team gets, and the Cursor actions Lyro runs to close it.

  • task_alt

    Report on what the Cloud agents are doing

    Lyro pages through every Cursor Cloud agent with its status, then opens one agent's conversation history to read the messages exchanged, so a stalled run is explained rather than just flagged.

    List AgentsGet Agent Conversation
  • storage

    Confirm what the account can actually reach

    Lyro lists the AI models available for API requests alongside the GitHub repositories the connected account has access to, which is the pair of checks behind most failed-to-start agent questions.

    List Available ModelsList GitHub Repositories

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Cursor actions it has and picks the ones a request needs.

  1. 01

    Connect Cursor

    Authorize the Cursor account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Cursor actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free

Cursor · Lyro

What can you do in Cursor without me setting anything up?

These, right away:

  • Get agent conversation
  • Get API key info
  • List agents

Great, let's start with the first one.

Ask Lyro anything...

FAQ

Everything else about Cursor

Setup, permissions, and the limits of what Lyro can do inside Cursor.

  • No. Every action in this toolkit reads: List Agents, Get Agent Conversation, List Available Models, List GitHub Repositories and Get API Key Info. Launching an agent or replying to one still happens in Cursor, so Lyro reports on the work rather than running it.

  • Get Agent Conversation returns a 404 both when the agent does not exist and when access is denied, so the two cases look identical from the outside. Listing agents first is the reliable way to tell a missing agent from a permissions problem.

  • The API key you connect. Get API Key Info returns the key's name, creation date and owner email, and List GitHub Repositories only shows repositories that owner can reach through their Cursor account, so scope follows the key rather than the person asking.

  • There is no code diff here. Get Agent Conversation returns the messages between the user and the Cloud agent, which is useful for understanding what an agent was told and what it reported back, not for inspecting the changes it made. Those stay in Cursor and in your repository.

Every action available in Cursor

All 5 actions your agent can call on Cursor, straight from the live MCP connection.

  • Get agent conversation

    Retrieve the conversation history for a specific cloud agent.

  • Get API key info

    Retrieve API key information including the key name, creation date, and owner email.

  • List agents

    Retrieve a paginated list of all Cursor Cloud agents.

  • List available models

    Retrieve the list of available AI models in Cursor.

  • List github repositories

    List GitHub repositories accessible to the authenticated user.

The tools Cursor sits next to

Same connection, same setup. Pick the next one your team already uses.

  • Bitbucketarrow_outward

    Bitbucket

    Searches code across a workspace, opens branches and pull requests, comments and merges after review, and reports which pipeline run broke.

  • Convexarrow_outward

    Convex

    Creates projects and deployments, batches query functions to read app data, issues and audits deploy keys, and reports log streams.

  • GitHubarrow_outward

    GitHub

    Searches issues and pull requests, files new ones from a conversation, labels and assigns them, and reads repository docs to ground an answer.

  • New relicarrow_outward

    New relic

    Runs NRQL queries and reads the numbers back, checks open alert violations, wires notification channels onto policies, and marks deployments on the timeline.

  • Scrapingbeearrow_outward

    Scrapingbee

    Extracts named fields with CSS or XPath rules, fetches rendered HTML or a screenshot, and routes blocked requests through a stealth proxy.

  • Uptimerobotarrow_outward

    Uptimerobot

    Reports live monitor status, separates planned maintenance from real outages, and adds monitors and status pages on request.

Browse every integration
Support agent working at a laptop next to the Lyro mascot

Ready to connect Cursor?

Authorize the account and your agent has all 5 actions from the first conversation.

Connect CursorTalk to sales
Connect CursorTalk to sales
Support agent working at a laptop next to the Lyro mascot