Can Lyro start, stop or steer a Cursor Cloud agent?

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.

What does Lyro see if an agent ID is wrong or off limits?

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.

Whose Cursor account and permissions apply?

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.

How is reading agent conversations different from a code review tool?

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.

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 Cursor See all integrations

5actions available

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.

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
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.

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.
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.
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

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.

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.