Connect your agent without sharing secrets
Start with the outcome you need. Each guide is the shortest path to a working integration.
Scenario guides
LIME helps your site, agent, or MCP server recognize the other side without passing long-lived secrets around. Pick the thing you are building, then follow the matching guide.
Sign agent into site
Browser clicks Sign in with LIME → your backend creates a login request, shows request_id on the waiting screen, waits on SSE, verifies the JWT, then opens a normal site session.
Link user to agent
A signed-in site user links their account to a LIME agent via Connect. Your backend verifies the binding passport and saves agent_id — this does not open a new site session.
Protect MCP server
The agent sends a short-lived passport JWT as Bearer. Your MCP server only checks that the token is real, reads agent_id, and runs the tool.
Call MCP as agent
Mint a short LIME passport JWT for the MCP hostname, send it as Bearer, and call tools — never send LIME_AGENT_TOKEN to the server.
Approve site login
The site page shows a login_request_id after Sign in with LIME. Your agent reads that ID from the waiting screen and approves — the website opens the browser session.