60fps MCP Terms of Use
Last updated: 29 July 2026
These terms cover the 60fps MCP server at mcp.60fps.design. Using it means you accept them. They sit alongside the 60fps PRO terms, which cover your subscription itself.
60fps is operated as a sole proprietorship from Bengaluru, India. Contact: admin@60fps.design.
What the MCP is
The 60fps MCP server lets an AI tool search the 60fps library and read the motion breakdown behind an interaction while you work. It is read only. It cannot change anything in your account, and it cannot write to 60fps.
It is currently in beta. Tools, responses and limits may change, and it may be unavailable at times.
Who can use it
The MCP is included with an active 60fps PRO subscription. If your subscription ends, is cancelled, is refunded, or a payment fails, MCP access ends with it.
You must be 18 or older to subscribe and use the MCP. If you are using it for an employer or client, you confirm you are allowed to accept these terms on their behalf.
What you may use it for
You may use the MCP for your own work, for the internal work of the business you work for, and to build your own products with. That means searching while you design or build, pulling references into your own projects, and asking your AI tool to help you understand or recreate an interaction.
Your license key
Your key is personal. It identifies your subscription, and it works on two devices at a time so you can use it on, say, a laptop and a phone. Connecting through an app such as Claude or ChatGPT does not use up one of those slots.
Do not share your key, publish it, or hand it to other people or organisations. If we see a key being used in a way that looks shared, we may reset it, limit it, or end access.
Keep your key safe. If it leaks, ask Gumroad for a new one, and tell us so we can retire the old one.
Fair use
There are limits so one user cannot degrade the service for everyone. Today that is 120 requests a minute per license. Go past it and you get an HTTP 429 with a Retry-After header telling your tool how long to wait. These numbers may change, and we will keep them published.
You agree not to:
Work around the limits, the device cap, or the license check
Bulk download or systematically copy the library, whether by hand or with a script
Rebuild, mirror, cache or re-host the library or any substantial part of it
Resell, sublicense or lease access to the MCP, or put it behind your own product or API
Use content from the MCP to build a standalone reference library, or any product that stands in for 60fps or competes with it
Use the MCP to train, fine tune, test, benchmark or evaluate a machine learning model
Remove or obscure any attribution or proprietary notice
Probe, attack, or disrupt the service
The references, and who owns what
The library contains recordings of real apps made by other companies. Those apps, their interfaces, brands, logos, copy and assets belong to those companies, not to 60fps, and nothing here gives you a right to use them.
What you get is access to 60fps as a reference: to study interactions, understand how they behave, and apply what you learn to your own work. The curation, descriptions, motion breakdowns, filters, and the library as a compiled whole are ours, and remain ours.
So, plainly: build your own version of a motion. Do not copy an app's brand, copy, icons, or assets, and do not present someone else's interface as your own.
Nothing here limits any right you have under fair dealing or fair use in your own country.
If you own an app and want a reference removed, email admin@60fps.design and we will take it down.
Accuracy, and AI generated content
Much of what the MCP returns is generated by AI. The descriptions, motion breakdowns, filters, search keywords and SwiftUI code are produced by a model reading the video, and they can be wrong, incomplete, or out of date.
Treat all of it as a starting point to check, not a fact to rely on. 60fps_get_motion_code returns starter code, not a finished component, and you are responsible for what you ship, including reviewing it, testing it, and making sure it fits your own product.
The code we generate is yours to use in your projects. It describes motion, and it carries no right to the app it was derived from.
What your AI tool does
The MCP responds to whatever your AI tool asks. We do not control that tool, its output, or what it does with our response. Its own terms and privacy policy apply to it.
If you build the MCP into something other people use, you are responsible for their use of it, and your agreement with them must protect 60fps at least as much as these terms do.
Availability
We aim to keep it up and publish status at status.60fps.design. We do not promise a particular uptime, and the MCP may go down for maintenance, for a problem, or because something upstream broke. Being in beta, expect the occasional rough edge.
Payment, refunds and cancellation
Subscriptions are billed by Gumroad, on the terms shown at purchase. There are no refunds except where the law requires one, or where we decide to give one.
You may cancel at any time in Gumroad. Cancelling takes effect at the end of the period you have already paid for, and access continues until then.
Suspending or ending access
We may suspend or end MCP access if these terms are broken, if a key is being shared, if the service is being abused, or if we are required to. Where it is reasonable to do so, we will tell you first.
You can stop at any time by removing the connector or deleting the config entry.
No warranty
The MCP is provided as is. We do not warrant that it will be uninterrupted or error free, that any reference or generated output is accurate, or that it fits your purpose. To the extent the law allows, we exclude implied warranties including merchantability, fitness for a particular purpose, and non-infringement.
Liability
To the extent the law allows, 60fps is not liable for indirect or consequential loss, lost profits, lost business, lost goodwill, or lost data arising from your use of the MCP. Our total liability for any claim is limited to what you paid for your subscription in the 12 months before the claim.
Nothing here limits liability that cannot legally be limited.
Your responsibility to us
You agree to cover 60fps against claims, losses and reasonable costs arising from your use of the MCP, from anything you build with it, or from your breach of these terms. That includes a claim by an app owner that your use of a reference infringed their rights.
If part of this does not hold
If any part of these terms turns out to be unenforceable, that part is treated as removed and the rest still applies.
Changes
We may update these terms. If a change matters, we will note it here and update the date. Carrying on using the MCP after a change means you accept it.
Governing law
These terms are governed by the laws of India, and the courts at Bengaluru have exclusive jurisdiction over any dispute arising from them.
Contact
admin@60fps.design