Can Lyro create or edit an issue in Leiga?

Not with this toolkit. Create Project is the only write it exposes; the issue actions, Get Issue Detail by Number and Get Issue Schema, are both reads. Lyro can report on an issue and the fields configured for its type, but the edit itself still happens in Leiga.

Why does Lyro read the issue schema before answering?

Get Issue Schema returns the full custom-field configuration for a chosen issue type. Leiga workspaces name and use their fields differently, so Lyro checks the schema first and reports the fields your team configured rather than assuming a standard set.

Which projects can Lyro see?

Exactly the ones the authenticated user can. List Projects returns the projects available to that account in paginated form, and Get Project Information adds owner and member detail for one of them. Connecting a more limited Leiga account is how you narrow what Lyro reaches.

Can Lyro set up a Leiga webhook?

It can tell you which event types are valid. Get Webhook Type List returns the webhook types available for configuration, but no action in the toolkit registers or removes a subscription, so the webhook itself is created in Leiga.

Leiga MCP integration

Lists projects and opens one in detail, creates projects from templates, and pulls issue detail with the custom-field schema behind it.

Connect Leiga See all integrations

10actions available

Three actions you can hand over today

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

Get issue detail by number
Lyro retrieves full details about a specific Leiga issue using its issue number. Your team gets context on related bugs or features without switching tools.
Create project
Lyro creates a new project in Leiga during strategic planning conversations. Your team starts collaborating on new initiatives instantly.
Get project information
Lyro pulls detailed project information from Leiga by ID when status is requested. Your team leader gets a complete project snapshot in the conversation.

See all 10 actions

How businesses use Leiga + Lyro

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

See what projects are running
Lyro pages through every project the connected account can reach and opens one of them for its full metadata, including who owns it and who is on it.
List ProjectsGet Project Information
Start a project from an existing template
Lyro browses the project templates available and the structured overview template behind one, then creates the project once the details have been agreed in the conversation.
Get Project Template ListGet Project Overview TemplateCreate Project
Answer a question about one issue
Lyro fetches an issue by its number for the complete detail, and reads the custom-field schema for that issue type so the fields it reports are the ones your workspace actually configured.
Get Issue Detail by NumberGet Issue Schema
Look up the files, versions and hooks around a project
Lyro pages through the files in a directory, lists the versions available for a platform before a deployment, and returns the valid webhook event types when an integration is being set up.
Get File ListGet Version ListGet Webhook Type List

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 Leiga actions it has and picks the ones a request needs.

01
Connect Leiga
Authorize the Leiga 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 Leiga 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

Leiga · Lyro

Everything else about Leiga

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

Not with this toolkit. Create Project is the only write it exposes; the issue actions, Get Issue Detail by Number and Get Issue Schema, are both reads. Lyro can report on an issue and the fields configured for its type, but the edit itself still happens in Leiga.

Every action available in Leiga

All 10 actions your agent can call on Leiga, straight from the live MCP connection.

Create project
Create a new project in Leiga.
Get file list
Retrieve a paginated list of files in a specified directory.
Get issue detail by number
Fetch detailed information about a specific issue using its issue number.
Get issue schema
Retrieve the issue custom-field schema.
Get project information
Fetch detailed information about a specific project by its ID.
Get project overview template
Retrieve the project overview template.
Get project template list
Retrieve a list of project templates.
Get version list
Fetch list of versions for a specific platform.
Get webhook type list
Retrieve the list of available webhook types.
List projects
List all projects available to the authenticated user.