MCP Terms

Last updated: August 17, 2026

These MCP Terms (these “MCP Terms”) apply to your (“you”, “your” or “Customer”) access to and use of the MCP Features. They supplement your existing agreement with ElevenLabs or, if no separate agreement exists, the ElevenLabs Terms of Service (either, the “Underlying ElevenLabs Agreement”). Your use of MCP Features is also subject to our Prohibited Use Policy and our Privacy Policy, and your use of ElevenAgents remains subject to our ElevenAgents Terms, which these MCP Terms supplement. Capitalized terms used but not defined in these MCP Terms have the meanings set forth in the Underlying ElevenLabs Agreement. 

If you do not have a signed written agreement with ElevenLabs, you accept these MCP Terms by enabling or using an MCP Feature, and you may not use the MCP Features if you do not agree to them or lack the authority to agree.

1. MCP Features. 

A. MCP. “MCP” means the Model Context Protocol, an open standard for providing context and tools to AI models. 

B. The MCP Features. These MCP Terms apply to the following functionality, each, an “MCP Feature” and in each case whether enabled through the ElevenLabs dashboard, our API, or an SDK:

i. connecting an MCP server operated by you or a third party (an “External MCP Server) to the Services, so that a Customer AI Agent may use the tools or data that server exposes; and

ii. connecting an MCP-compatible application or assistant that you use, operate, or authorize (an “MCP Client”) to the MCP server we make available (the “ElevenLabs MCP Server”), so that the MCP Client may read, create, configure, or delete resources in your workspace.

Establishing either connection is a “Connection.” This Section 1.2 describes the MCP Features and does not create any representation, warranty, or other commitment as to their features or availability. 

2. Availability. We may introduce or change fees or usage limits applicable to the MCP Features on notice in accordance with the Underlying ElevenLabs Agreement. The MCP Features are not available where you have elected Zero Retention Mode or require HIPAA compliance, and enabling an MCP Feature does not change that, except as we expressly agree in writing.

3. Open Source. The MCP Features leverage material open sourced by third parties. Nothing in these MCP Terms limits any rights you may have under, or grants you rights that supersede, the terms of the applicable open-source license. 

4. Enablement and Attribution.

A. Workspace Enablement. The MCP Features are disabled by default and are enabled at the workspace level, and enablement is not limited to workspace administrators.

B. Attribution. Enabling an MCP Feature, agreeing to these MCP Terms, or establishing a Connection, whether by you or by any person using your workspace or credentials, is attributed to you and binds you.

C. Your Controls. You are responsible for determining which of your Authorized Users (or, under the ElevenLabs Terms of Service, which users of your account) may enable an MCP Feature, establish or modify a Connection, or approve a tool call.

5. External MCP Servers.

A. Your Selection. You select each External MCP Server, and you are responsible for it, for its operator, and for everything it does in connection with the Services.

B. Your Responsibilities. Without limiting Section 3.1, you are responsible for:

i. vetting, configuring, and monitoring each External MCP Server, and for its security, availability, lawfulness, and behavior;

ii. setting tool-approval controls appropriate to the risk of each tool, including requiring approval before the execution of any tool that writes, deletes, transmits, or otherwise alters data;

iii. the data your Customer AI Agents transmit to and receive from each External MCP Server, and for limiting that data to what the relevant tool requires;

iv. implementing guardrails against prompt injection and other manipulation originating from an External MCP Server, its tool definitions, or the content it returns;

v. securing all credentials, secrets, tokens, headers, and connection details used for a Connection, and using encrypted transport; and

vi. promptly notifying us at legal@elevenlabs.io if you become aware of any vulnerability, compromise, or unauthorized access affecting an External MCP Server that is or has been connected to the Services.

C. Change by the Operator. The tools and capabilities an External MCP Server exposes are determined by its operator and may change without notice to you or to us, and you bear the consequences of any such change.

6. ElevenLabs MCP Server. If you connect an MCP Client to the ElevenLabs MCP Server, you authorize that MCP Client to act on your behalf within the scope you grant at sign-in. You are responsible for the MCP Client you select, for the persons you permit to connect it, for reviewing tool calls before approving them (including destructive actions such as deleting an agent), and for revoking access when it is no longer required.

7. Authorized Action. Establishing a Connection authorizes the Services to take actions on your behalf, and authorizes an MCP Client to act on your behalf within the scope you grant, including with respect to data processing, software manipulation, and system interactions. Actions taken through a Connection are treated as your actions, and you are responsible for them. You will not permit any data that you are prohibited from submitting to us under the Underlying ElevenLabs Agreement or the ElevenAgents Terms, including Prohibited Data and protected health information, to be transmitted to us through a Connection.

8. Third-Party Services. External MCP Servers and MCP Clients are third-party services. We do not provide, operate, endorse, verify, vet, or secure them, and we have no obligation to monitor, support, or troubleshoot them. Any reference to a third-party MCP server, MCP client, or directory in the Documentation is provided for convenience only and is not a recommendation or approval. No operator of an External MCP Server and no provider of an MCP Client is our subcontractor, subprocessor, or agent, and we are not responsible for its acts or omissions.

9. Scope of Our Security and Data Commitments. Our security commitments under the Underlying ElevenLabs Agreement, including the Information Security Exhibit and the DPA, apply to Customer Content or Content, as applicable, for purposes of the Underlying ElevenLabs Agreement, within systems we control. They do not apply to any External MCP Server or MCP Client, or to Customer Content or Content once transmitted to either at your direction. Retention, redaction, and related privacy options for agent conversations are described in the Documentation and configured by you. 

10. Your Content. Data, information, and material you provide through an MCP Feature, and any Output generated in connection with an MCP Feature, constitutes Content or Customer Content, as applicable, for purposes of the Underlying ElevenLabs Agreement, and may be used by us as provided in that agreement. You represent that you have all rights, consents, and authority (including any privacy consent required by applicable law) necessary to enable each Connection, to permit access to the relevant data sources, services, systems, and technology, and to allow us to transmit data to, receive data from, and process data received from them as contemplated by these MCP Terms.

11. Indemnification. In addition to, and without limiting, your indemnification obligations under the Underlying ElevenLabs Agreement, you will indemnify, defend (at our option), and hold harmless ElevenLabs and our affiliates, officers, directors, employees, and agents from and against any Claims, and all related Losses, arising out of or relating to: (a) your selection, configuration, or use of an External MCP Server or MCP Client; (b) any data transmitted to or received from either; or (c) any act or omission of an operator of an External MCP Server, or a provider of an MCP Client, that you have connected to the Services.

12. General.

A. Model-Specific Terms. Your access to and use of particular models in connection with the MCP Features may be subject to additional terms we post for those models (“Model-Specific Terms”), which supplement and form part of these MCP Terms.

B. Beta Services. To the extent we designate an MCP Feature as alpha, beta, pilot, preview, or a similar designation, the Beta Services provisions of the Underlying ElevenLabs Agreement, or the Beta Services Addendum, apply to it, provided that in the event of a conflict these MCP Terms prevail as to that MCP Feature. Your decision to purchase or use the Services was not and is not contingent on the delivery of any MCP Feature. 

C. Order of Precedence. If there is a conflict, the following order applies to your access to and use of the MCP Features: (a) any term of the Underlying ElevenLabs Agreement or an Order Form that expressly addresses the MCP Features; (b) the Model-Specific Terms; (c) these MCP Terms; and (d) the remainder of the Underlying ElevenLabs Agreement. Except as expressly set forth herein, the MCP Terms do not modify the confidentiality, indemnification, or limitation of liability provisions of the Underlying ElevenLabs Agreement.

D. Updates. We may update these MCP Terms. Updates take effect when we post them, except that, if you have a signed written agreement with ElevenLabs, an update that materially reduces your rights takes effect 30 days after we notify you, or at your next renewal if earlier. Updates required by law, or that we reasonably determine are necessary to address a legal, safety, or security risk, take effect immediately.