Connect agents to the work.
Lydo gives approved agents a structured way to understand a Space: its boards, tickets, files, notes, and decisions, so they can operate from the same source of truth as your team, not just an API.
Turn a link into structured context.
Hand an agent a Lydo URL, a Space slug, a board, or a ticket id like LYDO-42 and get back the structured context it needs, no chaining required.
Let agents find where the work lives.
List boards, read items, inspect a Space, and search notes and transcripts, so an agent can orient itself instead of guessing.
Operate inside approved scopes.
Agents work within the permissions, roles, and admin policy of the Space. Writes land in an approval queue unless a human opts them out.
Coding, ops, support, research.
Connect the agents you already run to the same source of truth as your team, so they work from the company context instead of starting cold.
One command from a ticket to context.
The Lydo CLI and the MCP server let a coding or ops agent resolve a Space, read a board,
post progress on a card, and start from the same context your team sees. Authenticate
once with lydo login; the agent works within your permissions.
- Resolve a Lydo URL, slug, or ticket into structured context
- List and read boards, items, notes, and transcripts
- Post and update progress on a card, in an approval queue
Governed by the Space
Connections inherit the Space's roles and admin policy. A Space that turns on Confidential Mode closes its connections, MCP and the CLI included, until the Space re-authorizes them. Access is the Space's to grant, not a bot's to take.
Give your agents a map of the work.
Early access is rolling out. Bring your agents to the context your team already built.