Connect an agent
AgentsThis page is how an agent learns to work with your notes. Lyt is meant to be operated by asking an agent — give it the skills, the compact manual, and, when you want typed tools, a local Model Context Protocol server.
Choose an interface
Setup installed Lyt’s instructions for the agent’s next session. Use this page to teach another agent you work with, or to connect a client that speaks MCP.
Skills route common intentions, the compact manual supplies global operating boundaries, and MCP exposes typed tools. They complement each other; they are not identical surfaces.
Install focused skills
Install the Lyt skills so you know my Lyt workflows.
Ask this of an agent you already have in front of you — it is how that agent learns the Lyt workflows.
lyt skills installSkills are ready-made instructions for the everyday asks — save this, find that, sync. Lyt installs 12 focused protocols into detected Claude Code, Codex, and generic agent skill roots.
Install the compact manual
Install the Lyt agent manual into your instructions.
lyt agent-manual --installThe manual is the standing rulebook your agent keeps in its own instructions — what it may do on its own, and what needs your say-so. The generated block teaches orientation, trust, write, publish, recovery, and update boundaries and can be reconciled on later releases.
Connect over MCP
MCP lets an agent app call Lyt directly as a set of tools, on your machine.
Start the Lyt MCP server so you can call Lyt tools directly.
lyt mcp startThe server uses standard input and output only. Configure your MCP client to launch it; Lyt does not expose an HTTP endpoint for this connection.
Add it to your client
{
"mcpServers": {
"lyt": { "command": "lyt", "args": ["mcp", "start"] }
}
}Understand the boundary
Plainly: the agent gets no more power than you have at this keyboard. And the specific actions that change what other people can see — sharing, unsharing, accepting an invitation, or abandoning a vault — refuse to run without your confirmation.
The agent receives the same read and write permissions as the local caller. It can use matching by meaning only when the local embedding model has already been downloaded — that one-time download is a separate choice, and MCP never triggers it. Approval-gated sharing, invitation acceptance, and abandonment mutations fail closed over MCP, and the gate cannot be satisfied from a tool call — it is server-side and out-of-band. A launch variable can open the dispatch side, but these operations still refuse to complete over MCP today, so run them through the confirmation-gated CLI.