MCP Studio SDK Terms of Service

1. Interpretation and Definitions

Capitalised words have the meanings set out below, and carry the same meaning in the singular and the plural.

• "Company", "we", "us", and "our" mean Appa Tools LLC.
• "Service" means the MCP Studio SDK: the developer portal at appatools.com/mcp-studio-sdk, the embeddable widget it produces, and the credentials and APIs that connect the two.
• "Developer", "you", and "your" mean the person using the Service, and the organisation on whose behalf that person is using it.
• "End User" means a person who uses the Embed inside your application. They are your customer, not ours.
• "Embed" means the widget the Service renders inside your application, through which an End User creates and manages MCP servers.
• "Client Credentials" means the client identifier and client secret issued to your developer account.
• "Configuration" means the settings you choose in the portal that control what the Embed exposes: tools, source types, colours, fonts, layout, and analytics.
• "MCP Studio" means our hosted service at appatools.com/mcp-studio, where the MCP servers created through the Embed are run.
• "MCP Studio Terms" means the Terms of Service governing MCP Studio, published at appatools.com/mcp-studio/terms.
• "Terms" means this document.

2. Acknowledgment

These Terms govern your use of the Service and form the agreement between you and the Company. Your access to and use of the Service is conditioned on your acceptance of them.

You accept these Terms by selecting the acceptance checkbox on the sign-in page before your account is created. We record the version you accepted and the time you accepted it. If we publish a new version of substance, you will be asked to accept it at your next sign-in, and you will not be signed in until you do.

You represent that you are at least 18 years old. We do not knowingly permit anyone under 18 to use the Service.

If you are using the Service on behalf of an organisation, you represent that you have authority to bind that organisation to these Terms, and "you" means both you and that organisation.

3. Beta Status

The Service is currently in beta. Features may change, be removed, or behave unexpectedly, and availability is not guaranteed. Beta access may be provided free of charge or at a reduced rate, and that pricing is not a commitment to future pricing.

This deserves more weight here than it would in a product used alone, because the Embed sits inside software your own customers rely on. A change to the Embed is a change your End Users see, and it will reach them before it reaches your release notes. Pin your integration to what you have tested, watch the release notes, and do not build a critical path through a beta service without a way to fall back.

4. Your Developer Account

You sign in with GitHub or Google. We do not hold a password for you, so the security of your developer account is the security of the provider account you sign in with. Protect it accordingly, and tell us immediately if you believe your account has been accessed without your permission.

You must give us accurate information and keep it current. You are responsible for everything done under your account, including changes to your Configuration, changes to your plan, and anything done with your Client Credentials.

One developer account represents one integration. If you operate several products, the cleanest arrangement is one account per product, because the plan, the ceilings, the Configuration, and the billing all attach to the account rather than to an application.

5. Client Credentials

Your client identifier names your integration and is not secret. Your client secret is, and it is the only thing standing between your plan and anyone who finds it.

Do not ship the client secret in client-side code. It does not belong in a JavaScript bundle, a mobile binary, a public repository, or a browser network request, all of which are readable by anyone who cares to look. Keep it on your server and keep it out of version control.

Anything done with your Client Credentials is treated as done by you, including servers created, sources indexed, requests served, and charges incurred. We cannot distinguish a call made by your backend from a call made by someone who copied your secret out of a bundle.

If you believe the secret has been exposed, rotate it from the portal immediately. Rotation takes effect at once, which means any integration still using the old secret stops working, and that is the intended behaviour rather than a side effect to work around.

6. Your End Users

The Embed runs inside your product, and your End Users are your customers. Your relationship with them is yours to define and yours to stand behind. We have no contract with them arising out of your integration, and we are not a party to whatever you have agreed with them.

You are responsible for having your own terms of service and privacy policy, for making them available to your End Users, and for making sure they cover what the Embed actually does in your product. If your privacy policy does not mention that content your End Users connect is fetched, stored, and indexed by a third party, it is incomplete, and correcting that is your obligation rather than ours.

Do not misrepresent who processes the data

You may present the Embed as part of your product, brand it with your colours, and describe the feature in your own words. That is what the Service is for. What you may not do is describe it in a way that leads an End User to believe their content stays with you when it does not. Content connected through the Embed is fetched by our infrastructure, stored on our systems, and processed by our providers. An End User who would have declined had they known that is an End User you have misled, and the resulting complaint is one you will be answering.

Content your End Users connect

When an End User connects a source through the Embed, we index it on your instruction, under your Client Credentials, against your plan. You represent and warrant that you have the rights, permissions, and consents needed for us to do that, including any consent required from the End User themselves and any right needed for the content they connect.

We do not and cannot verify it. We see a URL and a set of credentials arriving from an integration we have authorised, which is exactly what a legitimate request looks like, so the assurance has to come from you.

Where their servers live

MCP servers created through the Embed are created in MCP Studio and run there, and the MCP Studio Terms govern them and the content indexed into them. Those Terms are not replaced by these, and where an End User holds their own MCP Studio account, that account is theirs.

We may contact an End User directly where we need to: about abuse originating from their servers, about a legal demand concerning their content, or about a security matter affecting them. We would rather route such things through you and normally will, but a rule that we must never reach the affected person is not one we can commit to.

7. Embed and Configuration

The Embed renders inside your application, in a page you control, alongside your own interface. You decide where it appears and when your End Users see it.

Your Configuration decides what it exposes: which MCP tools are offered, which source types can be connected, the colours and fonts, the layout, and which analytics your End Users receive. Changing a Configuration changes what every End User sees on their next load, so treat it as a release rather than a preference.

Configuration values are validated before they are stored, for length and for content that would execute in a browser. Script tags, javascript: URLs, and event handler attributes are rejected. This exists because your Configuration is rendered inside your own application, where an injected script would run against your users and your origin rather than ours.

You must load the embed script from the URL we publish and use it as it is delivered. Do not modify it, re-host a modified copy, or call the underlying APIs in a way designed to bypass a plan limit, remove an attribution, or defeat a refusal the Service returned. A limit you can edit out of a script is not a limit, and the numbers in your plan assume you have not.

8. Plans, Limits, and How They Are Counted

Two ceilings apply to your integration, and they are counted on different axes. Reading one as the other is the mistake worth avoiding, because the two behave very differently as you grow.

• MCP servers are counted per End User. The limit applies to one person inside your Embed, so one customer filling their allowance has no effect on anyone else.
• MCP requests are counted across your whole footprint: every request made to every server created through your Embed, by every End User, added together.

On the free plan, each End User may create one MCP server, and your integration may serve 1,000 MCP requests per calendar month in total. On SDK Pro, at $499 per month, each End User may create ten MCP servers, and your integration may serve 5,000 MCP requests per calendar month in total.

There is no cap on how many End Users you may have on either plan. Requests are the pooled limit because requests are what cost us money to serve, and pooling them on that axis is exactly what allows servers to be counted per person without the plan becoming unbounded.

Your End Users remain subject to their own MCP Studio account limits on top of both of these. Either ceiling can refuse a request, and the one that refuses first is whichever is reached first.

The ceilings are enforced in MCP Studio, at the moment a server is created or a request is served. A request beyond a limit is refused rather than charged for, unless you have turned on overage as described below. We also apply operational limits that protect the Service as a whole, including rate limits and crawl budgets; these may change without notice. We will not reduce a published plan limit you are paying for without telling you first.

9. Usage Beyond Your Plan

Both ceilings are hard stops unless you turn on overage. Overage is opt-in and never on by default, because capacity nobody asked for must not turn into an invoice.

Turning it on requires three things, and each of them refuses on its own: the opt-in, a monthly budget in United States dollars greater than zero, and a payment method on file. The budget is required rather than optional. Usage-based billing with no ceiling is how one End User pointing an automation loop at their server produces an invoice you never agreed to, and you would be right to call that our fault.

One budget covers both kinds of overage. It is checked before a request is served, not after, because a request that has already been answered cannot be withdrawn. When the budget is spent, the ceilings become hard stops again for the rest of the month.

Additional MCP requests are metered and reported to our payment processor as they are served. Additional MCP servers, meaning servers beyond what your plan grants an End User, are billed at $25 per server per month as a quantity set once a day rather than at the moment a server is created. A count taken daily reflects what actually existed, whereas charging on creation would bill in full for a server made and deleted the same afternoon.

Turning overage off cancels the overage subscription immediately rather than at the end of the period. MCP Studio stops serving past your ceilings as soon as that change reaches it, and charging you for headroom that is already gone would be indefensible.

If an overage invoice goes unpaid for fourteen days, overage is disabled and your plan ceilings become hard stops again. Your servers, your Configuration, and your End Users’ work are not affected.

Your End Users are never shown your budget, your usage, or your bill. What you have agreed to spend is between you and us.

10. Analytics and Request Telemetry

You may subscribe to analytics tiers at the integration level, and the tier you hold is granted to the End Users who deploy servers through your Embed. They do not buy it separately, and they receive what you have paid for rather than what their own MCP Studio account would otherwise entitle them to.

The Service records each MCP request made to servers created through your Embed: which tool was called, the query text, how long it took, whether it succeeded, and up to a few hundred characters of each passage that was returned. This is recorded for every integration regardless of tier, so that subscribing to a tier shows you the history you already have rather than starting from nothing.

Because query text and returned passages are recorded, you should assume that whatever your End Users type into the Embed and whatever their sources contain may appear in that telemetry, and your privacy policy should say so.

Telemetry is retained for a defined period rather than indefinitely. Query text and returned passages are removed after 90 days on the free tier, and the remaining request records are deleted after 395 days. We also use PostHog to understand how the portal itself is used, which is separate from request telemetry and covered by our Privacy Policy.

11. Billing and Refunds

Payments are processed by Stripe. We do not see or store your card details. Current pricing is on the pricing page and is part of these Terms by reference.

Subscriptions are charged monthly in advance and renew until cancelled. You may cancel at any time from the billing portal. Cancellation takes effect at the end of the period you have already paid for, and we do not pro-rate a partial month.

If a payment fails, your access continues while we and Stripe attempt to recover it, because Stripe retries for several days and your End Users did nothing wrong. If it is still unpaid after fourteen days, paid capability is removed and your integration returns to the free plan.

A downgrade removes capability. It does not delete your Configuration, your credentials, your End Users’ MCP servers, their sources, or the analytics history already recorded. Destroying a customer’s work over a failed card is not recoverable, and a card can fail for reasons that have nothing to do with intent.

We may change pricing. A change to the price of an existing subscription takes effect at your next renewal and we will tell you before it does.

12. Acceptable Use

You agree not to use the Service, and not to permit your End Users to use the Embed, to do any of the following.

• Break the law, or help anyone else break it.
• Index, store, or retrieve content you or your End User do not have the right to use, including content behind a paywall, licence, or confidentiality obligation that does not permit it.
• Index content whose owner has asked you not to, or whose terms of use prohibit automated collection.
• Circumvent, disable, or interfere with any limit, quota, rate limit, or access control, including by modifying the embed script or by calling our APIs directly to obtain capacity a refusal denied you.
• Create more than one developer account in order to obtain more free capacity than one account allows.
• Resell or provide bare MCP Studio capacity to third parties without adding your own product around it. The Service exists so you can build a feature on top of it, not so that you can act as a reseller of our servers and requests under a different name.
• Probe, scan, or test the vulnerability of our systems, or attempt to access an account, MCP server, or data that is not yours.
• Send us content containing malware, or content designed to damage or gain unauthorised access to any system.
• Impersonate any person or organisation, including us, or present the Service in a way that misstates who operates it.
• Place a load on our systems that degrades the Service for other users, including through automated request loops.

We may suspend or terminate access for a violation of this section without prior notice, because the alternative is leaving the violation running while we send an email. Where a violation originates from a single End User rather than from you, we will try to tell you first so that you can address it yourself.

13. Third-Party Services and AI Output

The Service depends on third parties, and you should know which ones before you build on it. We use OpenAI to generate the embeddings that make content searchable, Anthropic for features that build tools or describe uploaded images, Neon for database hosting, Vercel for compute and hosting, Stripe for payments, Resend for email, and PostHog for product analytics. Content connected through your Embed is processed by these providers to the extent the feature in use requires it.

We do not control those providers and are not responsible for their acts or omissions. If one of them changes its terms, its pricing, or its availability, the affected feature may change or stop working.

Accuracy of retrieved content and AI output

The Service retrieves passages from connected content and returns them to AI clients. It does not verify that the content is correct, current, or complete, and it cannot. If the documentation indexed through your Embed is wrong, the answers built on it will be wrong. Where a feature uses a language model, for example building a custom tool, describing an uploaded image, or summarising content, the output is generated and may be inaccurate or misleading even when the underlying content is not.

You are responsible for reviewing anything the Service returns before acting on it, and for setting your End Users’ expectations about it. Do not present it, and do not let your product imply, that it is a sole basis for a decision with legal, financial, medical, or safety consequences.

14. Availability, Changes, and Data Loss

We aim to keep the Service available, but we do not offer a service level agreement and we do not guarantee uptime. The Embed, indexing, crawling, and search may be delayed, degraded, or unavailable.

Design your integration so that this is survivable. An outage on our side becomes an outage inside your product, and the End User sees your interface rather than ours, so handle a failed load and a refused request in your own copy instead of leaving a blank panel.

We may add, change, or remove features, including features of the Embed and options in the Configuration. Where a change removes something you depend on we will try to give reasonable notice, but in beta we may not be able to.

We take backups. We do not guarantee against loss or corruption of data, including of an index. An index is derived from the sources it was built from and is rebuildable from them, which is why we treat it as replaceable and you should too.

15. Intellectual Property

The Service and everything in it, including the portal, the embed script, the APIs, the documentation, the name, and the logo, is and remains the property of Appa Tools LLC and its licensors, and is protected by copyright, trademark, and other laws of the United States and other countries.

These Terms grant you a limited, non-exclusive, non-transferable, revocable right to embed and use the Service as it is provided, for as long as your account is in good standing. They grant you nothing else, and in particular they do not transfer any right in the embed script or the underlying platform.

Your product, your brand, and the content your End Users connect are yours. Our trademarks and trade dress may not be used to suggest that we endorse, sponsor, or operate your product beyond a factual statement that it is built on MCP Studio.

16. Your Feedback to Us

If you send us feedback, suggestions, or ideas about the Service, you assign all rights, title, and interest in that feedback to us. If that assignment is ineffective for any reason, you grant us a non-exclusive, perpetual, irrevocable, royalty-free, worldwide licence to use, reproduce, disclose, sublicense, distribute, modify, and exploit it without restriction and without owing you anything.

This is not a claim on your source code or your product. It covers what you tell us about ours.

17. Term and Termination

These Terms apply for as long as you use the Service.

You may stop at any time by removing the Embed from your application. You may also request deletion of your developer account from your account settings. Requesting deletion cancels every live subscription you hold immediately, schedules your account for permanent deletion 24 hours later, and revokes your integration in MCP Studio.

Understand what that revocation does before you request it. It stops the MCP servers your End Users created through your Embed from being served, so it is a change your customers will notice within minutes. Deletion is irreversible and there is no cancel path. If your End Users hold their own MCP Studio accounts, tell them before you delete yours.

We may suspend or terminate your access immediately and without prior notice if you breach these Terms, if we are required to by law, or if continuing to serve your integration would expose us or our providers to material risk.

Sections covering your End Users, your representations about connected content, intellectual property, feedback, limitation of liability, the disclaimer, indemnification, governing law, and dispute resolution survive termination.

18. Limitation of Liability

To the maximum extent permitted by applicable law, the entire liability of Appa Tools LLC and its suppliers under any provision of these Terms, and your exclusive remedy for all of it, is limited to the greater of the amount you actually paid us for the Service in the twelve months before the claim arose, or one hundred United States dollars.

To the maximum extent permitted by applicable law, we and our suppliers are not liable for any indirect, incidental, special, consequential, or punitive damages whatsoever, including damages for lost profits, lost revenue, lost data, business interruption, loss of goodwill, or claims made against you by your own End Users, arising out of or in any way related to your use of or inability to use the Service, even if we have been advised of the possibility of those damages and even if the remedy above fails of its essential purpose.

Some jurisdictions do not allow the exclusion of implied warranties or the limitation of liability for incidental or consequential damages. In those jurisdictions our liability is limited to the greatest extent permitted by law.

19. "AS IS" and "AS AVAILABLE" Disclaimer

The Service is provided to you "AS IS" and "AS AVAILABLE", with all faults and defects and without warranty of any kind. To the maximum extent permitted by applicable law, we disclaim all warranties, whether express, implied, statutory, or otherwise, including all implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement, and any warranties arising out of course of dealing or usage of trade.

We make no representation or warranty that the Service will meet your requirements, achieve any intended result, be compatible with your application or any other software, operate without interruption, meet any performance or reliability standard, be free of errors, or that any error will be corrected. We do not warrant the accuracy, reliability, or currency of any content the Service retrieves or generates.

Some jurisdictions do not allow the exclusion of certain warranties or limitations on a consumer’s statutory rights, so some or all of the above may not apply to you. In that case the exclusions apply to the greatest extent enforceable under applicable law.

20. Indemnification

You agree to indemnify and hold harmless the Company and its officers, employees, and suppliers from any claim, demand, loss, liability, or expense, including reasonable legal fees, arising out of your application, your Configuration, the content connected through your Embed, your breach of these Terms, or your violation of any law or of anyone else’s rights.

This includes claims brought by your End Users, whether about how you described the Embed, about content they connected through it, about your own terms and privacy policy, or about your handling of their data. They are your customers, and a dispute with them is yours to answer.

21. Governing Law

The laws of the State of Illinois, United States, excluding its conflict of law rules, govern these Terms and your use of the Service. Your use may also be subject to other local, state, national, or international laws.

22. Dispute Resolution

If you have a concern or dispute about the Service, you agree to try to resolve it informally first by contacting us at zair@appatools.com. Most problems are a misunderstanding about how something works, and we would rather fix that than argue about it.

If a dispute cannot be resolved informally, you and Appa Tools LLC agree that it will be brought exclusively in the state or federal courts located in the State of Illinois, United States, and you and we each consent to the personal jurisdiction of those courts.

European Union users

If you are a consumer resident in the European Union, you keep the benefit of any mandatory provisions of the law of the country in which you live, and nothing above removes them.

23. United States Legal Compliance

You represent and warrant that you are not located in a country subject to a United States government embargo or designated by the United States government as a terrorist-supporting country, and that you are not listed on any United States government list of prohibited or restricted parties.

24. Severability and Waiver

If any provision of these Terms is held unenforceable or invalid, that provision will be modified and interpreted to accomplish its objective to the greatest extent possible under applicable law, and the remaining provisions continue in full force.

Our failure to exercise a right or to require performance of an obligation under these Terms does not affect our ability to do so later, and waiving a breach does not waive any later breach.

25. Changes to These Terms

We may modify or replace these Terms at any time. Each version carries a version identifier, shown at the top of this page.

When we make a change of substance we publish the new version here and ask you to accept it the next time you sign in. We do not treat continued use as silent agreement to a materially different agreement.

If you do not agree to a new version, stop using the Service and, if you wish, request deletion of your account. Because that revocation reaches your End Users, give yourself time to tell them rather than doing both in the same afternoon.

26. Contact Us

Questions about these Terms go to zair@appatools.com. A person reads that address.