doublespeed MCP Addendum

Last Updated: September 1, 2026

This MCP Addendum (this "Addendum") supplements the doublespeed Terms of Service (the "Terms") and applies whenever Customer or an Authorized User accesses the doublespeed Services through doublespeed's Model Context Protocol (MCP) server, including from an AI Client such as Claude or ChatGPT. Capitalized terms not defined in this Addendum have the meanings given in the Terms. If this Addendum and the Terms conflict with respect to access through the MCP server, this Addendum controls; the Terms otherwise remain in full effect.


1. The MCP Server

doublespeed's MCP server is part of the "API" described in Section 1(h) of the Terms. It exposes a defined set of tools that let a connected AI Client read data from, and take actions in, Customer's doublespeed account, such as browsing media and templates, generating images and video, creating and editing drafts, creating review links, and queueing posts. Use of the doublespeed Services through the MCP server is Use of the doublespeed Services under the Terms.

2. Connections and Authentication

An MCP connection is authorized against a specific doublespeed user account. Everything an AI Client does through that connection is performed with that user's permissions and on Customer's behalf. Customer is responsible for which AI Clients its Authorized Users connect, for the scope of each authorization, and for revoking a connection when it is no longer needed. A connected AI Client must be treated like any other credential under Section 1(c) of the Terms: if Customer suspects a connection has been compromised, Customer will revoke it and notify doublespeed promptly.

3. Instructions from AI Clients

doublespeed treats each request arriving through an authorized MCP connection as an instruction from Customer. That includes requests the AI Client composes on its own while carrying out a broader task its user gave it. Actions taken through the MCP server have the same effect as the same actions taken in the doublespeed web application: content generation consumes Credits, queued posts publish to connected Accounts, and edits change Customer's drafts and data. Section 13(c) of the Terms (AI Agent Actions) applies to actions an AI Client takes through the MCP server. Customer is responsible for reviewing Output before directing an AI Client to publish it.

4. Data Transmitted to AI Clients

To respond to an AI Client's requests, doublespeed transmits Customer Materials, Input, and Output to that AI Client, as described in Section 1(j) of the Terms. Once transmitted, that data is handled under the AI Client provider's own terms and privacy practices, including any use by that provider to provide, maintain, or improve its own services. doublespeed does not control, and is not responsible for, an AI Client provider's handling of data. The doublespeed Privacy Notice describes doublespeed's own handling of personal information.

5. Restrictions

All use restrictions in the Terms, including Sections 1(d) (Use Restrictions) and 1(e) (Prohibited Content and Conduct), apply to use through the MCP server. In addition, Customer will not use the MCP server to circumvent any Licensed Volume, Credit limit, or rate limit, and will not use it to build or operate a product or service that provides third parties with substantially the functionality of the doublespeed Services, as described in Section 1(h) of the Terms.

6. Availability and Changes

doublespeed may add, change, or remove MCP tools, change the data they return, or suspend or discontinue the MCP server, in each case as described in Section 17(b) of the Terms. AI Clients are Third-Party Services under the Terms: doublespeed does not control them and does not warrant that any particular AI Client will remain compatible with the MCP server. doublespeed is not affiliated with, or endorsed by, any AI Client provider.

7. Changes to this Addendum

doublespeed may modify this Addendum as described in Section 17(a) of the Terms.


Questions about this Addendum: legal@doublespeed.ai