en flagEN
Book a demo
en flagEN
Book a demo
Request Demo

MCP Server Terms

These MCP Server Terms apply to your use of the Document360 MCP Server. By enabling the MCP Server, or by connecting an AI client to it, you accept these MCP Terms.

  • Last updated 04/11/2026
  • Version v1.0

These MCP Server Terms (“MCP Terms”) apply to your use of the Document360 MCP Server. “We”, “us” and “our” mean Document360 Limited, the provider of the Document360 Service. “You” and “your” mean the customer organisation that uses Document360, including your Service Users.

These MCP Terms supplement the Document360 Terms of Service, or any separate agreement you have signed with us (the “Agreement”). The Agreement continues to govern your use of Document360. If there is a conflict, these MCP Terms apply in relation to the MCP Server only.

By enabling the MCP Server, or by connecting an AI client to it, you accept these MCP Terms. If you accept them on behalf of an organisation, you confirm that you have authority to bind it.

1. What the MCP Server is

1.1 The Document360 MCP Server lets an AI client you authorise (such as Claude, ChatGPT or Copilot) read and act on your Document360 knowledge base using the Model Context Protocol. It works only within the permissions of the Service User who connects it.

2. Who can use it

2.1 The MCP Server is available on the plans shown in your Order Form and only where API access is enabled for your project.

2.2 Some tools may be offered as preview or beta features. These may change or be withdrawn at any time and come with no warranty.

2.3 You may use the MCP Server only for your own internal business purposes. You may not resell it, sublicense it, or use it to provide services to others.

3. Your AI client is a third-party service

3.1 You choose which AI clients to connect. Each AI client is provided by a third party under its own terms and privacy policy. It is not part of Document360.

3.2 When you connect an AI client, you instruct us to send your content, including any Personal Data in it, to that AI client in response to its requests.

3.3 Once your content reaches the AI client, the AI client provider’s terms apply. We are not responsible for how it stores, uses, shares or trains on that data.

3.4 AI client providers are not our sub-processors. You are responsible for reviewing their terms, setting their data retention and training options, and putting any agreements you need in place with them.

3.5 You are responsible for every AI client your Service Users connect, including personal or consumer accounts. Use our admin controls, where available, to limit which Service Users and projects can use the MCP Server.

4. How we handle your data

4.1 We keep logs of MCP activity to run, secure and support the MCP Server and to give you usage reports. Personal Data in those logs is handled under our Data Processing Agreement.

4.2 We do not use your content, Personal Data, Service User metadata or MCP activity logs to improve the MCP Server. To improve it, we use only technical error logs that contain no Service User metadata or content.

4.3 We do not see your conversations with your AI client. We only process the information the AI client sends to us in a request.

4.4 We do not use your content, or anything received through the MCP Server, to train AI models.

5. Permissions and actions

5.1 Every request runs with the identity and permissions of the Service User who connected the AI client. The MCP Server never grants extra access.

5.2 Anything an AI client does through the MCP Server, including creating, editing, publishing or deleting content, counts as an action by that Service User and by you, unless it was caused by our own breach.

5.3 Set up roles and permissions carefully before enabling the MCP Server. Review and confirm any action that changes or deletes content, where your AI client supports it.

5.4 If an AI client changes or deletes your content, you may be able to restore it using Document360’s version history or backup features. What you can restore depends on the editor your project uses and the limits of those features.

5.5 We label our tools to help AI clients ask for confirmation, but we cannot guarantee an AI client will respect those labels.

6. Prompt injection

6.1 Content in your knowledge base, imported files or reader feedback may contain hidden instructions that trick an AI client into doing something you did not intend. To reduce this risk:

  • 6.1.1 use AI clients that meet your own security, privacy and vendor approval requirements;
  • 6.1.2 turn on human confirmation for actions where available;
  • 6.1.3 limit MCP access to the Service Users and projects that need it; and
  • 6.1.4 revoke access promptly if you suspect misuse.

7. Security and access

7.1 Keep your MCP Credentials secure. Do not share them between Service Users or store them where unauthorised people can see them.

7.2 Admins can turn the MCP Server on or off per project. Removing a Service User or lowering their role also removes or limits their MCP access.

7.3 We may revoke Credentials for security reasons. If we do, we will let your admins know without undue delay, unless that would put security at risk or the law prevents it.

7.4 We will protect the MCP Server to the same standard as the rest of Document360, manage changes to our tools through our change process, notify you of security incidents affecting it, and make MCP activity records available to your admins.

8. Acceptable use

8.1 The acceptable use rules in the Agreement apply. In addition, you must not use the MCP Server or any AI client to:

  • 8.1.1 bypass or test roles, permissions or other access controls;
  • 8.1.2 get around rate limits or usage limits;
  • 8.1.3 plant instructions in content to manipulate someone else’s AI client;
  • 8.1.4 send any regulated data to an AI client in breach of the Agreement;
  • 8.1.5 knowingly send passwords, API keys, payment card data or ID numbers through MCP requests;
  • 8.1.6 connect an AI client that you are not allowed to use under its provider’s terms or your own policies;
  • 8.1.7 give third parties access to the MCP Server; or
  • 8.1.8 probe, scan or test the vulnerability of the MCP Server, except with Document360’s prior written permission.

9. Usage limits

9.1 The MCP Server is subject to usage and service performance terms expressed in our Agreement. We may slow down, queue or reject requests that go over those limits or that affect the service.

10. Pricing

10.1 The MCP Server is currently included in Document360’s Business and Enterprise plans at no additional charge. However, in relation to MCP Server, we reserve the right to amend our pricing and other terms from time to time on reasonable notice.

11. Suspension

11.1 We may suspend MCP access, in whole or for a specific AI client, Service User, Credential or project, without suspending the rest of the Document360 Service. We will only do this where reasonably needed to protect security or availability, prevent harm, or deal with a breach of section 8. Where practicable, we will tell you, keep the suspension as limited as possible, and restore access once the issue is resolved.

12. AI Outputs

12.1 Content an AI client creates and saves to Document360 becomes your content. We do not review it and make no promises about its accuracy, completeness or legality. Our commitments about Document360’s own built-in AI features do not apply to it. Review AI-generated content before you publish, share or rely on it.

13. Changes and directory listings

13.1 We may add, change or remove tools, supported protocol versions, sign-in methods and supported AI clients, with reasonable notice where practicable.

13.2 If and when we publish new MCP tools as part of a Document360 release, you may choose to get the latest tools from our MCP server by refreshing the tool list.

13.3 Listings of our MCP Server in third-party directories (such as the Anthropic Connectors Directory or the ChatGPT Directory) are controlled by those providers, who may change or remove them.

14. Disclaimers and liability

14.1 The MCP Server is provided “as is” and “as available”. Unless your Order Form says otherwise, it is not covered by any service level agreement or uptime commitment.

14.2 We are not liable for: what an AI client or its provider does with your data; actions taken with valid MCP Credentials; actions caused by prompt injection; AI-generated Outputs; or outages caused by changes made by an AI client provider.

14.3 Our overall liability remains subject to the limits in the Agreement. Nothing in these MCP Terms limits liability that cannot be limited by law.

15. Your responsibility for claims

15.1 You agree to and will defend and indemnify us against third-party claims arising from: actions taken with your MCP Credentials (except where section 14 says we are responsible); a breach of section 8; your use of an AI client or its handling of your data; or AI-generated Outputs. The claims procedure in the Agreement applies.

16. Ending use

16.1 When the Agreement ends, or the MCP Server is disabled for a project, all related MCP Credentials are revoked.

16.2 Data already sent to an AI client stays with that provider. You are responsible for arranging its deletion with them.

16.3 Sections 3, 12, 14, 15 and 16 continue to apply after these MCP Terms end.

17. Trademarks

17.1 Claude is a trademark of Anthropic PBC. ChatGPT is a trademark of OpenAI. Copilot is a trademark of Microsoft Corporation. Other names belong to their owners. Mentioning an AI client does not mean we are partnered with or endorsed by its provider.

18. Reporting security issues

18.1 Security vulnerabilities in the MCP Server may be reported to [email protected]. Document360 will investigate reports with reasonable care.

19. Changes to these terms and contact

19.1 We may update these MCP Terms from time to time and will change the “Last updated” date when we do. For material changes, we will give notice as described in the Agreement. Continued use of the MCP Server after a change takes effect means you accept the updated terms.

19.2 Questions about these MCP Terms? Contact [email protected].

Document360 AI