Two routes, and the first is considerably easier.
Claude Desktop
Install it as a Desktop Extension from Settings, then Extensions, and paste your API token when prompted. No JSON to edit.
The token is stored in your operating system’s keychain rather than a plaintext configuration file, which is the main reason to prefer this route.
Before the listing is live you can sideload the .mcpb bundle from the latest release. macOS bundles are not Developer ID signed yet, so allow it under System Settings, Privacy & Security, Open Anyway if Gatekeeper blocks it.
Cursor and other clients
Add this to your client’s MCP configuration:
{
"mcpServers": {
"screenly": {
"command": "screenly",
"args": ["mcp"],
"env": {
"API_TOKEN": "your-api-token-here"
}
}
}
}Then restart the client.
Authentication
The same two options as the CLI: the API_TOKEN environment variable, or screenly login storing credentials in ~/.screenly.
The extension route uses the keychain instead of either.
Getting a token
In your workspace settings, go to the Security tab, then Tokens. It is shown once. See API tokens.