AI Context by MCP Studio — n8n Node 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.
• "Node" means the "AI Context by MCP Studio" community node distributed as the npm package n8n-nodes-mcp-studio, together with the credential type it registers.
• "n8n" means the workflow automation software the Node runs inside, which is published by a third party and is not ours.
• "Instance" means the installation of n8n on which the Node is installed.
• "You" means the person installing, configuring, or operating the Node, and the organisation on whose behalf they do so.
• "MCP Studio" means our hosted service at appatools.com/mcp-studio, which the Node calls.
• "API Key" means an MCP Studio API key configured in the Node’s credential.
• "Terms" means this document.

2. Acknowledgment

These Terms govern your use of the Node. You accept them by selecting the acceptance option in the Node’s credential form, which n8n will not let you save until you do, and in any event by using the Node.

The Node is a client for MCP Studio and does nothing on its own. Everything it does happens in your MCP Studio account, under the MCP Studio Terms of Service, which you accepted when that account was created. Those Terms continue to apply and these add to them rather than replace them. Where the two conflict on a matter specific to the Node, these Terms control.

You represent that you are at least 18 years old and that you have authority to install software on the Instance and to bind its operator to these Terms.

3. Licence

The Node is distributed under the MIT licence, and that licence governs your rights in the code itself, including the right to copy and modify it. Nothing in these Terms narrows it.

These Terms cover something the MIT licence does not: your use of our hosted service through the Node. The code is open; the service it calls is ours to run.

If you modify the Node, you may not present the modified version as ours or use our name or logo to suggest we published or endorsed it.

4. An MCP Studio Account Is Required

The Node requires an MCP Studio account and an API Key. Your plan on that account determines what the Node can do: how many MCP servers you may create, how many sources each may have, and how many MCP requests you may make each month. The Node does not carry its own allowance and installing it grants you nothing extra.

Requests the Node makes count against your account exactly as if you had made them from the MCP Studio web application. A workflow that runs on a schedule will consume your monthly allowance on that schedule, and an automation loop can exhaust it quickly. Setting sensible triggers and limits in your workflows is your responsibility.

5. Your API Key and Instance Security

An API Key authenticates as your MCP Studio account. It can create and delete MCP servers, add and remove sources, and read your analytics. Anything done with it is treated as done by you.

Configuring the credential stores the key on the Instance, under n8n’s credential encryption and n8n’s access controls, not ours. This is the part worth pausing on: on a shared Instance, everyone who can build or edit a workflow can generally use a saved credential, even if they cannot read the key itself. If that set of people is not the set you would give account access to, use a dedicated MCP Studio account for the Instance instead of your own.

You are responsible for securing the Instance, for who can reach it, and for the key’s confidentiality once it is there. We cannot see your Instance and cannot detect misuse of a key on it. Revoke a key from your MCP Studio account settings the moment you suspect it has been exposed; revocation is immediate.

6. What the Node Sends Us

The Node sends us only what the operation you configured requires: the URLs and labels of sources you add, the names and descriptions of servers you create, and the query text of searches you run, along with your API Key for authentication. Workflow data you do not pass into a Node parameter is not sent to us.

Take care with expressions. A parameter filled from earlier workflow data will send that data to us, and a query built from, for example, an inbound support email will include the contents of that email. Whatever reaches a query parameter is recorded in your MCP Studio request telemetry under the retention period described in the MCP Studio Terms.

The Node does not phone home, does not send us your workflows, and does not report on your Instance.

7. We Are Not n8n

n8n is published by a third party and we are not affiliated with, endorsed by, or acting for them. "n8n" is their trademark and is used here only to identify the software the Node is compatible with.

We are not responsible for n8n itself, for your Instance, for how n8n stores credentials, or for a change in n8n that breaks the Node. n8n’s own terms govern your use of n8n, and community nodes are installed at your own risk under those terms. Support for the Node comes from us; support for n8n does not.

A version of n8n may stop working with a version of the Node. We publish which versions we support and we are not obliged to maintain compatibility with any particular one.

8. Using the Node as an AI Agent Tool

The Node can be attached to an n8n AI Agent as a tool, which means a language model decides when to call it and with what arguments. If you do that, the model is choosing what to send us and, depending on the operations you expose, may create or modify things in your MCP Studio account.

Those calls are still yours. Expose only the operations the agent needs, and do not give an agent a credential with more reach than the task requires.

9. Acceptable Use

You agree not to use the Node to do any of the following.

• Break the law, or help anyone else break it.
• Index, store, or retrieve content you 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 creating multiple accounts to obtain more free capacity than one account allows.
• 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.
• Resell, sublicense, or provide the service to third parties except through the MCP Studio SDK under its own terms.
• 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.

10. Third-Party Services and AI Output

The service depends on third parties, and you should know which ones before you rely on it. We use OpenAI to generate the embeddings that make your 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. Your content is processed by these providers to the extent the feature you are using 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 the content you connect and returns them to AI clients. It does not verify that the content is correct, current, or complete, and it cannot. If the documentation you index is wrong, the answers built on it will be wrong. Where a feature uses a language model — building a custom tool, describing an uploaded image, 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. Do not use it as the sole basis for a decision with legal, financial, medical, or safety consequences.

11. Availability and Changes

The Node is published to npm and we may release new versions, change its operations, or deprecate it. Installed versions keep working until you update them, and we do not push updates to your Instance.

The Node depends on the MCP Studio API. We may change that API, and an older version of the Node may stop working as a result. We do not offer a service level agreement for either.

12. Intellectual Property

The service and everything in it other than Your Content — the software, the interface, 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 use the service as it is provided. They grant you nothing else. Our trademarks and trade dress may not be used in connection with any product or service without our prior written consent.

13. 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 documentation. It covers what you tell us about our product.

14. Term and Termination

These Terms apply for as long as the Node is installed on an Instance you operate or you use it to call MCP Studio. You may stop at any time by removing the credential and uninstalling the package.

We may revoke an API Key or refuse requests from it if you breach these Terms or the MCP Studio Terms. Because the Node holds only a key, that is what termination looks like here: the installed code stays on your Instance and stops being able to do anything.

15. 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 Node and the MCP Studio account it calls 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, or loss of goodwill, 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.

16. "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 any other software or service, 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.

17. 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.

18. 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.

19. 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.

20. 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.

21. 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 note it in the package release notes and the node documentation. 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. Nothing obliges you to accept a change you disagree with.

22. Contact Us

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