Preamble and Precedence

Use of any MCP Connector is subject to (i) these MCP Connector Terms and (ii) the applicable Order Form as agreed by the Customer (the "Agreement"). Capitalized terms not defined here have the meaning given in the Agreement. If these MCP Connector Terms conflict with the Agreement, These MCP Connector Terms control.

The MCP Connector is optional. Customer is not required to enable it, and the Software delivers its core functionality without it. By enabling, installing, or connecting to an MCP Connector, Customer accepts these MCP Connector Terms.

1. Definitions

  • "AI Client" means any third-party AI application, agent, model, or platform (for example Anthropic Claude, Microsoft Copilot, ChatGPT, or Google Gemini) that is licensed by Customer directly from the AI Client provider, operated directly by Customer through its Authorized Users, and connects to an MCP Connector. An AI Client does not include a Third-Party Intermediary. AI Clients are not developed, controlled, or operated by Litera.
  • "AI Integration" means Customer's connection or use of an AI Client with an MCP Connector, including any use that causes MCP Requests, MCP Responses, or Customer Data to be transmitted to or processed by an AI Client, or that results in AI Outputs.
  • "AI Output" means any response, recommendation, document, action, or other content generated by an AI Client. AI Outputs are not generated, authored, or controlled by Litera.
  • "Customer Data" has the meaning in the Agreement and includes documents, matter data, client information, and other content in or accessible through the Software.
  • "Software" means the specific Litera on-premise or cloud software product identified in an Order Form, and all Updates thereto.
  • "MCP" means the Model Context Protocol, an open standard for connecting AI Clients to external tools and data.
  • "MCP Connector" means the Litera-provided component that implements MCP to expose defined tools, resources, or data of a Software to an AI Client, whether hosted by Litera or deployed in Customer's environment.
  • "MCP Request" and "MCP Response" mean, respectively, a tool call, query, or instruction submitted to an MCP Connector, and the data or result returned by it.
  • "State-Changing Action" means any action that creates, modifies, annotates, shares, exports, sends, or deletes data or records in or from a Software.
  • "Authorized User" means an individual Customer permits to use the Software and connect an AI Client to an MCP Connector.
  • "Third-Party Intermediary" means any person or platform, other than Customer's own Authorized Users, that connects or enables a connection to an MCP Connector on behalf of or for the benefit of Customer or its users, or that provides AI functionality to Customer through such a connection, including any legal AI platform, workflow or agent vendor, reseller, aggregator, integrator, or other intermediary, whether or not Customer licenses or pays for it.

2. License and Permitted Use

2.1 License. Subject to Customer's valid license to the Software and compliance with these MCP Connector Terms, Litera grants Customer a limited, non-exclusive, non-transferable, non-sublicensable, revocable right, for the term of that license, to access and use the MCP Connector solely for Customer's own internal business purposes with that Software, and only directly by Customer’s Authorized Users through an AI Client. Where the MCP Connector is deployed in Customer's environment, this includes the right to install and operate it there.

2.2 Restrictions. Customer will not (a) distribute, resell, or host an MCP Connector for third parties or use it on a standalone basis; (b) reverse engineer, decompile, or attempt to derive source code, models, or methods from an MCP Connector or MCP Responses, except as mandatory law permits; (c) use an MCP Connector, MCP Responses, or the Software to develop, train, or improve a competing product, service, or AI model; (d) circumvent any access control, rate limit, or technical restriction; or (e) use an MCP Connector in a way that damages, overburdens, or impairs the Software or Litera's infrastructure.

2.3 Affiliates and contractors. Customer may permit its affiliates, contractors, and managed service providers to use an MCP Connector as Authorized Users acting under Customer's direction and through an AI Client that Customer itself licenses and operates, only for Customer's internal benefit and on terms at least as protective of Litera as these MCP Connector Terms. This Section does not permit any affiliate, contractor, or managed service provider to connect an AI Client that it, rather than Customer, licenses or operates, or to act as a Third-Party Intermediary. Customer remains responsible for their acts and omissions.

2.4 Ownership. Litera and its licensors retain all rights in the MCP Connector, its tools, schemas, and documentation. Customer retains all rights in Customer Data. As between the parties and to the extent permitted by law, Customer owns AI Outputs, excluding any Litera technology embedded in them. Litera makes no claim to AI Outputs, and their copyright status is governed by applicable law and the AI Client provider's terms.

2.5 No third-party or intermediary access. MCP Connectors may be used only by Customer directly, through an AI Client that Customer itself licenses and operates. Customer will not, and will not permit any person to, use an MCP Connector through, or make an MCP Connector available to, any Third-Party Intermediary, including by connecting a legal AI platform or any other intermediary or aggregator that accesses an MCP Connector on Customer's behalf, by sharing or delegating credentials or access tokens to one, or by configuring one to call an MCP Connector. These MCP Connector Terms grant no rights to any Third-Party Intermediary. Any such access requires a separate written agreement between Litera and the applicable third party, and nothing in these MCP Connector Terms obliges Litera to enter into one.

3. Third-Party AI Clients

3.1 Customer's choice. Subject to Section 2.5, Customer decides whether and which AI Client to connect. Litera does not provide, test, certify, or endorse any AI Client and makes no commitment that an MCP Connector will work with any particular AI Client or version.

3.2 Third-party terms and fees. Customer is solely responsible for (a) the AI Client provider's terms, acceptable use policy, and privacy and security terms; (b) any fees, token charges, or API costs; and (c) any processing, retention, or use of data (including for model training) by the AI Client provider. Litera is not a party to any agreement between Customer and an AI Client provider.

3.3 Data leaves Litera's control. When an AI Client retrieves an MCP Response, Customer Data protected inside the Software by authentication and role-based access may be transmitted to and processed in an environment outside Litera's control. Litera's security, confidentiality, and data-processing commitments in the Agreement do not extend to Customer Data once it is delivered to an AI Client or to Customer-operated infrastructure.

3.4 Changes by third parties. AI Client providers may change their interfaces, models, or terms at any time. Litera is not responsible for any disruption or outcome caused by those changes.

4. AI Outputs and Human Review

4.1 No Litera control. Litera does not generate, monitor, or validate AI Outputs. AI Outputs are probabilistic and may be inaccurate, incomplete, outdated, or misleading. MCP Responses may also be incomplete, capped, truncated, or stale.

4.2 Customer review. Customer is solely responsible for reviewing and validating AI Outputs and MCP Responses, and for any decision or action taken in reliance on them, before relying on or implementing them. AI Outputs are not a substitute for professional judgment.

4.3 No legal advice. The MCP Connector, the Software, and AI Outputs do not provide legal, financial, or other professional advice. Litera is not a law firm. Customer's attorneys and other professionals remain solely responsible for their work product and for compliance with their professional and ethical duties, including competence, supervision, confidentiality, and candor to tribunals.

4.4 Prompt injection. Content that an AI Client reads, including documents and MCP Responses, may contain instructions that manipulate the AI Client into unintended actions. Customer is responsible for client-side controls, including tool-approval settings and limits on which Connectors an AI Client may use. Litera is not responsible for detecting or remediating such manipulation by an AI Client.

5. Human Oversight of State-Changing Actions

5.1 Approval. Before an AI Client performs a State-Changing Action, Customer will ensure that an Authorized User has approved it or that it falls within a category Customer has deliberately pre-authorized. Customer is solely responsible for pre-authorized actions, including any standing or programmatic approval.

5.2 Production safeguards. Customer will not grant an MCP Connector write or delete permissions in a production environment without human oversight. Litera recommends testing in a non-production environment first, limiting automated actions in scope, and making them reversible where possible.

5.3 Litera-provided controls. Where Litera makes available controls such as confirmation prompts, read-only modes, or tool allow-lists, Customer is responsible for configuring them, and for any decision to disable, override, or bypass them. Where Litera offers destructive tools, they remain disabled unless Customer affirmatively enables them.

5.4 Agentic use. Customer acknowledges that agentic use, where an AI Client acts across multiple steps without real-time review of each step, carries a higher risk of unintended consequences. Customer is responsible for any such use.

6. Security, Access, and Credentials

6.1 Least privilege. Customer will grant an MCP Connector and each AI Client only the access, scopes, and credentials needed for a defined purpose, and will issue, store, rotate, and revoke credentials securely. Customer is responsible for all activity under its credentials.

6.2 Authorized users only. Customer will permit only Authorized Users and approved service identities to connect AI Clients to an MCP Connector, and will inform them of these MCP Connector Terms and of the limits of AI Outputs.

6.3 Customer-deployed Connectors. Where an MCP Connector runs in Customer's environment, Customer is responsible for hosting, securing, monitoring, and updating it. For production use, Customer will place it behind Customer-controlled network boundaries, use encrypted transport and authentication, and not expose it to the public internet. Litera's access to a Customer-deployed MCP Connector is limited to what Customer provides.

6.4 Security incidents. Customer will promptly notify Litera at legal@litera.com of any suspected compromise of credentials or misuse of an MCP Connector that could affect the Software.

7. Data, Confidentiality, and Privilege

7.1 Customer Data. Customer Data accessed through an MCP Connector remains Customer's, and the Agreement's confidentiality, security, and data-processing terms continue to apply to Customer Data that Litera receives or processes. Litera-hosted MCP Connectors: Litera processes MCP Requests and MCP Responses only to provide the MCP Connector and as the Agreement permits. Litera does not use Customer Data or MCP traffic to train generative AI models without Customer's written opt-in.

7.2 Customer's decisions on data. Customer determines which Software data an MCP Connector may expose, which AI Clients may receive it, and whether that is lawful. This includes personal data, regulated data, client confidences, privileged material, and data subject to protective orders, export controls, or client outside counsel guidelines. Customer is responsible for obtaining any required client, third-party, or data subject consents and notices, and for appropriate transfer safeguards.

7.3 Privilege and ethical duties. Customer is responsible for assessing whether sending information to an AI Client could waive privilege, breach a duty of confidentiality, or conflict with a client engagement terms or applicable professional rules, and for choosing AI Clients and settings (for example, enterprise AI Clients with no-training and no-retention commitments) accordingly. Litera is not responsible for any such waiver or breach arising from Customer's connection of an AI Client.

7.4 Personal data. As between the parties, and for Customer-directed AI Integrations, Customer is the controller (or business) of personal data sent to an AI Client. Litera acts only as a processor (or service provider) where, and to the extent, it processes personal data on Customer's behalf under the Agreement or its data processing addendum.

7.5 Usage data. Litera may collect and use technical and usage data about MCP Connector operation (for example tool call counts, error rates, and performance), in aggregated or de-identified form, to operate, secure, support, and improve the Software. This does not include the content of Customer Data.

8. Nature of the MCP Connector; Support

8.1 Evolving feature. MCP is a developing standard. Litera may add, change, restrict, or remove MCP Connector tools, schemas, response formats, and versions, and compatibility between versions may be limited. Customer is responsible for keeping its AI Clients and, for Customer-deployed Connectors, its MCP Connector on supported versions and for installing security updates.

8.2 Support. Unless the Agreement or an order states otherwise, support for MCP Connectors is limited to standard support for installation and defects in the MCP Connector itself and does not extend to AI Clients, prompts, AI Outputs, or Customer's integration design. MCP Connectors may be excluded from the end-of-life and end-of-support policies for the Software.

8.3 Throttling and Usage limits. Litera may, at any time, with or without notice, and in its sole discretion, set, change, or enforce rate limits, quotas, concurrency limits, and other usage thresholds on MCP Connectors, and may throttle, limit, queue, delay, or reject any MCP Request, including any that exceeds them. Customer is responsible for AI Client behavior that generates excessive or abnormal call volume, including loops and retries, and for use that exceeds normal, human-directed interaction with the Software.

8.4 Fees. Litera may, at any time, introduce or change fees for access to MCP Connectors, meter or charge for MCP Requests or usage above stated thresholds, or change the packaging of MCP Connector access, on thirty (30) days' notice. Access to an MCP Connector without charge during any initial or promotional period does not entitle Customer to continued free access.

8.5 No service levels or availability commitments. Unless Litera expressly agrees otherwise in writing, MCP Connectors are provided without any commitment as to availability, uptime, performance, latency, throughput, or response times, and any service level agreement, uptime commitment, or service credit in the Agreement does not apply to MCP Connectors. Litera may interrupt, suspend, modify, or discontinue any MCP Connector or tool at any time.

9. Prohibited and High-Risk Uses

Customer will not use an MCP Connector (a) in violation of law, including applicable AI, privacy, export, and sanctions laws; (b) to process data Customer has no right to use; (c) to make automated, unsupervised changes to records of legal, regulatory, or financial significance; (d) in high-risk or life-critical settings, or in any way classified as prohibited or high-risk under the EU Artificial Intelligence Act or similar law; or (e) with an AI Client Customer has not evaluated and approved for the data involved. Customer is responsible for its own compliance with AI laws, including transparency and human oversight obligations that apply to it as a deployer.

10. Suspension, Monitoring, and Termination of MCP Access

10.1 Suspension. Litera may limit, suspend, or revoke access to an MCP Connector, or an AI Client's access, on notice where practicable, if Litera reasonably believes that use presents a security, legal, or operational risk to Litera, the Software, or other customers, or breaches these MCP Connector Terms, including any access in breach of Section 2.5.

10.2 Customer-deployed Connectors. On Litera's written request in those circumstances, Customer will promptly disable the affected MCP Connector and confirm in writing that it has done so.

10.3 Self-certification. On Litera's request, not more than once per year, Customer will confirm in writing within ten (10) business days that its use of MCP Connectors complies with these MCP Connector Terms.

10.4 Termination. Customer may stop using an MCP Connector at any time. The license in Section 2 ends automatically when Customer's license to the Software ends, and Litera may terminate it on written notice for Customer's uncured material breach of these MCP Connector Terms. After termination, Customer will cease use and, within thirty (30) days, uninstall and delete all copies of any Customer-deployed MCP Connector.

11. Disclaimer of Warranties

TO THE MAXIMUM EXTENT PERMITTED BY LAW, EACH MCP CONNECTOR, MCP RESPONSE, AND AI INTEGRATION IS PROVIDED "AS IS" AND "AS AVAILABLE." LITERA DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND ANY WARRANTY THAT AN MCP CONNECTOR OR AI INTEGRATION WILL BE UNINTERRUPTED, ERROR-FREE, SECURE, OR COMPATIBLE WITH ANY AI CLIENT, OR THAT MCP RESPONSES OR AI OUTPUTS WILL BE ACCURATE, COMPLETE, LAWFUL, OR SUITABLE FOR ANY PURPOSE. THIS SECTION SUPPLEMENTS, AND DOES NOT REPLACE, THE DISCLAIMERS IN THE AGREEMENT.

12. Liability

To the maximum extent permitted by law, Litera and its affiliates, licensors, and suppliers are not liable for any loss, damage (direct, indirect, consequential or any other damage), cost, or expense of any kind, whether in contract, tort (including negligence), breach of statutory duty, or otherwise, arising out of or related to Customer’s or its Authorized Users’ access to or use of any MCP Connector or AI Integration, including any loss or damage arising from: (a) AI Outputs, MCP Responses, or any action taken or not taken in reliance on them; (b) the acts, omissions, or failures of any AI Client or AI Client provider; (c) Customer Data after it is delivered to an AI Client or otherwise made available through an MCP Connector; (d) any action an AI Client performs through an MCP Connector under Customer’s credentials, scopes, or approvals; or (e) Customer’s configuration choices, including granted scopes and disabled controls. Customer’s use of MCP Connectors and AI Integrations is at its sole risk.

13. Changes to These Terms

Litera may update these MCP Connector Terms for security, legal, regulatory, or product reasons. If Customer does not agree to an update, its sole remedy is to stop using the MCP Connector before the update takes effect. Continued use afterward is acceptance. Updates do not alter the Agreement itself, which changes only as it provides.

14. General

14.1 These MCP Connector Terms are governed by the law, and subject to the jurisdiction and dispute resolution terms, in the Agreement.

14.2 These MCP Connector Terms and the Agreement are the entire agreement on their subject matter. No waiver is effective unless in writing and signed by Litera.

14.3 If a provision is unenforceable, it is enforced to the extent possible and the rest remains in effect.

14.4 Sections 2.2, 2.4, 3, 4, 7.4, 7.5, 11, 12, and 14, and any provision that by its nature should survive, survive termination or expiry.

Last updated: October 2026. Version 1.0