Tempo API and MCP Terms

Last updated: 14 September 2026 (v. 1.0)

These Tempo API and MCP Terms (these “API Terms”) govern Customer’s access to and use of the Tempo API and the Tempo MCP Server. They form part of the Agreement between Customer and Tempo Software Inc. (“Tempo”) governing Customer’s use of the Hosted Services, and apply to all access to and use of the API and MCP Server by Customer and its Users.

Where the MCP Server is enabled, these API Terms are also accepted on Customer’s behalf by an Administrator, or another person authorised by Customer, by indicating acceptance at the point of enablement. The person accepting represents that they are authorised to bind Customer.

If Customer does not agree to these API Terms, it must not enable the MCP Server and must not access or use the API.

1. Definitions

1.1 “API” means the Tempo application programming interfaces made available by Tempo, as described in the Documentation.

1.2 “MCP Server” means the Tempo Model Context Protocol server, which exposes Customer Data to AI Clients connected by Customer.

1.3 “AI Client” means any third-party AI assistant, agent, application or other client that Customer or a User connects to the API or MCP Server. “AI Provider” means the third party that operates an AI Client or any model it uses.

1.4 “Administrator” means a User who (a) holds the administrative permission required to enable the MCP Server, as described in the Documentation, and (b) is authorised by Customer to implement and manage Customer’s use of the API and MCP Server, including to accept these API Terms on Customer’s behalf.

1.5 “Credentials” means OAuth credentials, registered OAuth clients, and Tempo API tokens used to authenticate to the API or MCP Server.

1.6 “Agreement” means the signed agreement between Customer and Tempo governing the Hosted Services or, in the absence of one, the Tempo End User License Agreement at www.tempo.io/eula (the “EULA”). “Hosted Services” and “Usage Data” have the meanings given in the Agreement.

1.7 “Documentation” means the technical documentation for the API and MCP Server published by Tempo, including the API reference at apidocs.tempo.io and the product documentation at help.tempo.io, as updated from time to time, together with any successor or replacement location Tempo designates.

1.8 “Customer Data” means data that Customer or a User submits to or records in the Hosted Services, and data derived from it by the Hosted Services, in each case to the extent accessible through the API or MCP Server. Customer Data does not include Usage Data.

1.9 “User” means an individual authorised by Customer to use the Hosted Services.

1.10 Where the Agreement defines a term used in these API Terms, the definition in the Agreement prevails.

2. Relationship to the Agreement

2.1 These API Terms supplement and form part of the Agreement. Customer’s use of the API and MCP Server remains subject to the Agreement in all respects not addressed here.

2.2 In the event of a conflict, the order of precedence is: (a) the signed agreement between the parties, if any; (b) these API Terms, as to subject matter specific to the API and MCP Server; and (c) the EULA.

2.3 Where Tempo processes personal data on Customer’s behalf, the Tempo Data Processing Agreement at www.tempo.io/data-processing-agreement continues to apply and is not varied by these API Terms.

3. Enablement and Administration

3.1 The individual enabling the MCP Server represents that they are an Administrator, that they are authorised by Customer to implement and manage Customer’s use of the API and MCP Server, and that they are authorised to accept these API Terms and bind Customer. Tempo is entitled to rely on those representations and on the administrative permission held by that individual at the time of enablement.

3.2 Customer is solely responsible for deciding whether to enable the MCP Server or use the API, for obtaining any internal approvals required, and for determining that such use is appropriate for its data and its regulatory environment.

3.3 An Administrator may disable the MCP Server at any time. Disabling prevents further access, but does not affect Customer Data already transmitted to an AI Client, which Tempo cannot recall, retrieve or delete.

4. Authentication and Access

4.1 Access to the API and MCP Server is available through the following methods, as described in the Documentation:

(a) per-user OAuth 2.0 credentials (the default method);

(b) OAuth credentials for an OAuth client registered against Customer’s instance, including where Customer permits clients to register automatically; and

4.2 The availability of a particular method may be subject to configuration by an Administrator.

4.3 Access is bound to the permissions of the authenticating User. A User can access only the Customer Data that User is already permitted to access in the applicable Hosted Services. Enabling the MCP Server does not grant any additional User permissions.

4.4 Customer responsibility for permissions. Customer is responsible for configuring and maintaining its Tempo and Atlassian permissions so that each User’s access is appropriate.

4.5 Credentials. Customer is responsible for safeguarding all Credentials, for provisioning and promptly deprovisioning access, and for all activity conducted using its Credentials, whether or not authorised by Customer. Customer must notify Tempo promptly via Support Portal or at security@tempo.io on becoming aware of any compromise or unauthorised use.

4.6 Registered OAuth clients. Customer is responsible for all OAuth clients registered against its instance and for all activity conducted under them, including where a client is registered automatically by an AI Client or on a User’s behalf rather than by an Administrator. Tempo may refuse, suspend, revoke or expire any client registration at any time, including on security grounds or where a registration appears unused, abusive or unauthorised, without liability to Customer.

5. Customer-Directed Transfer to AI Clients

5.1 In connection with the API and MCP Server, Tempo does not select, operate, control, endorse or vet any AI Client or AI Provider. Tempo transmits no Customer Data to any AI Client through the API or MCP Server unless Customer or a User connects that AI Client.

5.2 By connecting an AI Client, Customer instructs and directs Tempo to make the requested Customer Data available to that AI Client. Each such transfer occurs at Customer’s direction.

5.3 Once Customer Data is transmitted to an AI Client, it is processed by the relevant AI Provider under Customer’s own arrangements with that provider. The AI Provider is not a Tempo subprocessor, and Tempo is not responsible for the AI Provider’s security, retention, disclosure, or use of that Customer Data, including any use for model training or improvement.

5.4 Customer is responsible for: (a) entering into appropriate terms with its AI Provider; (b) its own compliance obligations in respect of the transfer, including under applicable data protection law and any notice or consent requirements; and (c) determining whether particular categories of Customer Data are appropriate to transfer.

5.5 Customer acknowledges that Tempo cannot retrieve, delete, restrict or otherwise control Customer Data after transmission to an AI Client, and that requests for deletion or restriction in respect of such Customer Data must be directed to the AI Provider.

6. AI Outputs

6.1 “Output” means any output generated by an AI Client in response to a query submitted through the API or MCP Server. Each Output is produced by the AI Client and its underlying model, not by Tempo. Tempo does not generate, review or validate any Output.

6.2 Outputs are non-deterministic. An Output may be inaccurate, incomplete, outdated or misleading, may misinterpret a query or a date range, and may differ between AI Clients, between models, and between identical queries.

6.3 Customer is solely responsible for the verification of each Output against the applicable Hosted Services before relying on it for any future use.

6.4 Tempo makes no representation or warranty as to the accuracy, completeness or fitness of any Output. This is in addition to the disclaimers in the Agreement.

7. Write Operations

7.1 The write operations available through the API or MCP Server, if any, are as described in the Documentation. Tempo may add to, modify or withdraw them in accordance with clause 9.

7.2 Customer is responsible for all data created, modified or deleted through the API or MCP Server, including where initiated by a User, by an application operated by or for Customer, or by an AI Client, and including any data derived from an Output.

7.3 Tempo does not review, validate or verify data written through the API or MCP Server, and is not responsible for its accuracy or for any consequence of it being written, including any effect on approvals, billing, invoicing, payroll or reporting.

7.4 Customer is responsible for determining which Users, applications and AI Clients may perform write operations, and for verifying any Output before it is used as the basis for a write operation.

8. Acceptable Use

8.1 Customer will use the API and MCP Server in accordance with the Documentation and any rate, volume or concurrency limits Tempo applies. Tempo may set and modify such limits, and may throttle requests that exceed them.

8.2 Customer will not, and will not permit any third party or AI Client to:

(a) circumvent or attempt to circumvent any rate limit, authentication, permission or access control;

(b) reverse engineer, decompile or attempt to derive the source code or underlying structure of the API or MCP Server;

(c) extract, replicate or retain Customer Data at a scale or frequency inconsistent with the Documentation, or place an unreasonable load on the API or MCP Server;

(d) introduce malicious code, or conduct any denial-of-service or similar attack; or

(e) use the API or MCP Server unlawfully or in breach of the restrictions in the Agreement.

9. Availability, Changes and Deprecation

9.1 Tempo may add to, modify, version, deprecate or discontinue any part of the API or MCP Server, including any read or write capability. Where a change is not backward compatible, Tempo will endeavour to communicate it through the Documentation in advance, where reasonably practicable.

9.2 No service level agreement applies to the API or MCP Server unless expressly agreed in a signed agreement. Availability of the API and MCP Server is not a warranted characteristic of the Hosted Services.

10. Suspension

10.1 Tempo may suspend or disable access to the API or MCP Server, in whole or in respect of a particular User, Credential, registered client or AI Client, with immediate effect where Tempo reasonably considers it necessary to address a security risk, suspected unauthorised access, excessive or abusive use, or a breach of these API Terms or the Agreement. Tempo will endeavour to notify Customer promptly where it does so.

11. Warranties

11.1 The API and MCP Server are provided “AS IS”. To the maximum extent permitted by law, Tempo disclaims all warranties in respect of the API and MCP Server, including that they will be uninterrupted, error-free or secure, or that any particular endpoint, tool or capability will remain available. The warranty disclaimers in the Agreement apply equally to the API and MCP Server.

11.2 Tempo gives no warranty in respect of any AI Client, AI Provider or Output, and no warranty that the API or MCP Server will be compatible with any particular AI Client.

12. Liability

12.1 Tempo’s liability arising out of or relating to the API and MCP Server is subject to the limitations and exclusions of liability in the Agreement. These API Terms do not create any additional liability for Tempo, and do not increase any cap on liability in the Agreement.

12.2 Without limiting clause 12.1, Tempo has no liability for:

(a) the acts or omissions of any AI Client or AI Provider;

(b) any Output, or any decision made or action taken in reliance on an Output;

(d) any OAuth client registered against Customer’s instance;

(e) any Customer Data after it has been transmitted to an AI Client; or

(f) any data created, modified or deleted through the API or MCP Server, including by an AI Client.

12.3 Customer will defend and indemnify Tempo against third-party claims arising from Customer’s connection or use of an AI Client, or from Customer’s breach of clause 4.5, 5, 7 or 8.

13. Term and Termination

13.1 These API Terms apply for as long as Customer accesses or uses the API or MCP Server. Customer may end them by disabling the MCP Server and ceasing use of the API.

13.2 These API Terms terminate automatically on termination or expiry of the Agreement. Clauses 5.3 to 5.5, 6, 7, 11, 12 and 14 survive.

14. General

14.1 Changes. Tempo may update these API Terms from time to time. The current version is published at www.tempo.io/api-mcp-terms (or applicable successor page) with a “Last updated” date. Continued use of the API or MCP Server after an update constitutes acceptance. Where a change is material, Tempo may require renewed acceptance by an Administrator.

14.2 Governing law. These API Terms are governed by the governing law, jurisdiction and venue provisions of the Agreement.

14.3 Miscellaneous. If any provision of these API Terms is held unenforceable, it will be limited or severed and the remainder will remain in effect. No failure or delay by Tempo in exercising any right is a waiver of it.