← BookleeCONTENT HISTORY
WHAT CHANGED
Update to Booklee
Snapshot Oct 28, 2026 · 13:14 UTC · version 1.0.24
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Booklee and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Connect Booklee, complete sign-in and consent, and show the access granted to this agent.",
"included_files": [],
"name": "setup",
"skill_md_contents": "---\nname: setup\ndescription: Connect Booklee, complete sign-in and consent, and show the access granted to this agent.\n---\n\n# Connect Booklee\n\nUse the Booklee MCP server already selected for this host. Before calling a\ntool, make sure the user is in a new chat on the host where the package was\ninstalled and has typed `@` and selected **Booklee**. Selecting a skill or\nstarter prompt without selecting the plugin does not load its MCP server. Do\nnot create a cloud environment, ask for credentials, or construct an OAuth URL\nyourself.\n\nStart by calling `get_access_context` with `{}`. If the client requests\nauthentication, let the user complete both Booklee sign-in and the\n**Connect an app to Booklee** consent page. The user must choose the requested\ncapabilities and organization or location targets and click **Allow** or\n**Connect**. Sign-in alone does not create a connection.\n\nAfter the client reports that consent completed, call `get_access_context`\nagain. Explain the account, role, capabilities, organizations, locations, and\nplatform access returned by Booklee. Current Booklee permissions remain\nauthoritative; a connection cannot grant a role or target the account does not\nhave.\n\nIf the client reports that the Booklee connector is unavailable, explain that\nthe selected host has not loaded the MCP server. Ask the user to open the\nBooklee plugin's Manage/Settings page for that host, enable or reconnect the\n`booklee` MCP server, start a new chat, and select **Booklee** with `@` before\nretrying. Do not claim that access is connected without a successful\n`get_access_context` result. If the model itself reports that it is at\ncapacity, the user must switch to an available model before retrying.\n\nNever ask for a password, cookie, mobile token, access token, or consent URL.\nTo review or revoke an existing connection, direct the user to\nhttps://booklee.app/mcp/connections.\n"
}SHA-256 of public snapshot: b3fa2283f832f6065e7dd08dbc924b3cb89eeab891e779674649765b144ea97b