Web MCP: Sign-in, permissions, and revoking access
Web MCP signs you in with your LottieFiles account. It never uses API keys, and the AI can only do what your account can already do.
How sign-in works
- Your AI app finds the LottieFiles sign-in settings automatically.
- The first time you connect, a browser window opens to the LottieFiles sign-in page. You sign in (or are already signed in) and see a consent screen naming the app asking for access.
- After you approve, the app stays signed in and refreshes access in the background. You won't be asked again unless you revoke access or your session expires.
What the AI can access
- The AI has the same access you have: no more, no less.
- It can only reach workspaces you're a member of, and features your plan includes.
- Anything you can do on LottieFiles, the AI can do too, including deleting animations. Treat the connection like a logged-in session.
How long access lasts
- Access token: 10 minutes, renewed automatically
- Idle session: Expires after 30 minutes of no use
If your session expires, your app asks you to sign in again the next time you connect.
Revoke access
- From your AI app: remove Web MCP or disconnect it. In Claude, go to Settings → Connectors and select Remove. In ChatGPT, delete the plugin in Settings → Plugins.
- Let it expire: idle sessions end after 30 minutes.
- Sign out everywhere: if you think someone misused your account, change your LottieFiles password or sign out of all sessions on lottiefiles.com.
Stay safe
- Only approve apps you recognize on the consent screen.
- Ask the AI to show changes before it runs them. See Use Web MCP: your first request, prompts, and reviewing changes.
- For automated or long-running agents, connect a LottieFiles account whose workspace access matches only what the agent should touch.