MCP Additional Terms
These MONJI+ MCP Additional Terms (the “MCP Additional Terms”) apply to the use of the MCP Integration Feature of MONJI+ provided by ALAKI Inc. (“Provider”) and supplement the MONJI Terms of Service applicable to the global version of MONJI+ (the “Terms”).
Capitalized terms not defined in these MCP Additional Terms have the meanings given to them in the Terms or, where applicable, the Data Processing Addendum (the “DPA”).
1. Purpose and Relationship with Other Terms
- These MCP Additional Terms govern the use of functionality that uses the Model Context Protocol (“MCP”) to connect the Service with generative AI services, AI clients, and other external tools (the “MCP Integration Feature”).
- These MCP Additional Terms supplement the Terms and apply to Customer and its Users when using the MCP Integration Feature.
- In the event of any conflict between these MCP Additional Terms and the Terms with respect to the MCP Integration Feature, these MCP Additional Terms will control. However, to the extent of any conflict concerning the processing of Personal Information, the DPA will control.
- Before using the MCP Integration Feature, each User must review and accept these MCP Additional Terms through Provider’s applicable authentication and authorization flow. Use of the MCP Integration Feature is also subject to Customer’s administrative settings and role-based permissions as described in Section 3.
- These MCP Additional Terms do not expand the geographic availability of the Service or the MCP Integration Feature. All geographic, territorial, payment-related, sanctions-related, and data-related restrictions set forth in the Terms and the Restricted Regions List continue to apply to the MCP Integration Feature, including restrictions relating to use in, from, or for the benefit of Restricted Regions and restrictions on submitting or processing Personal Information of individuals located in Restricted Regions.
2. MCP Integration Feature
- The MCP Integration Feature allows a User to connect a generative AI service, AI client, or other external tool selected by the User and authorized through Provider’s authentication and authorization process (an “AI Client”) and to allow that AI Client to access information available within MONJI+.
- An AI Client may access only information that the relevant User is otherwise authorized to view through the Service.
- As of the effective date of these MCP Additional Terms, the MCP Integration Feature is read-only. An AI Client cannot use the MCP Integration Feature to create, modify, delete, approve, change the status of, or otherwise alter information within MONJI+.
- The specific information, operations, access permissions, AI Client, account, and other details available through a connection will be displayed through the applicable authentication and authorization screen, settings screen, help documentation, or other method designated by Provider.
3. Authentication, Authorization, and Role-Based Permissions
- Customer administrators may control whether the MCP Integration Feature is available to Users based on roles or other permission settings provided by the Service, including permissions applicable to Members and Guests.
- A User may use the MCP Integration Feature only to the extent such use is permitted under Customer’s applicable administrative settings and role-based permissions.
- Where Customer has permitted MCP use for a User or the User’s applicable role, the User may select an AI Client and individually authorize a connection through Provider’s authentication and authorization flow.
- Before authorizing a connection, the User must review the AI Client, the applicable MONJI+ account, the access permissions and operations being requested, and any other information displayed on the authorization screen, and must expressly authorize the requested access.
- Any access permission or operation not displayed and authorized through Provider’s applicable authentication and authorization flow is not granted to the AI Client.
- An AI Client may not access any Team, Project, Feedback, Customer Content, or other information beyond the scope that the relevant User is otherwise authorized to access through MONJI+.
- Use of the MCP Integration Feature does not grant a User any right or permission within MONJI+ that the User did not already possess.
- If Provider introduces a new category of access permission or operation for the MCP Integration Feature, that new permission or operation will not automatically be granted to an existing AI Client connection unless the User separately and expressly authorizes it.
- A User may revoke an authorized AI Client connection through the method designated by Provider.
- Customer and Users are responsible for appropriately safeguarding authentication credentials, authorization information, access tokens, and other security information relating to the MCP Integration Feature and for taking reasonable measures to prevent unauthorized use.
4. Processing and Disclosure of Information through the MCP Integration Feature
- When a User uses the MCP Integration Feature, the AI Client authorized by that User may obtain Customer Content or other information from MONJI+ within the scope of the permissions granted to that AI Client.
- For purposes of the DPA, to the extent use of the MCP Integration Feature is permitted under Customer’s administrative settings or role-based permissions, a User’s activation or use of the MCP Integration Feature and the User’s authorization of an AI Client through Provider’s applicable authorization flow constitute Customer’s documented instruction to Provider to process and transmit Customer Content, including Personal Information, to the User-selected AI Client solely to the extent reasonably necessary to provide the MCP Integration Feature, subject to the Terms, the DPA, these MCP Additional Terms, and applicable law.
- Information made available to an AI Client may, depending on the relevant Customer Content, include comments, information concerning web pages, images, attachments, information relating to Users or third parties, and other information stored in MONJI+.
- Such information may include Personal Information, customer information, confidential information, trade secrets, non-public information, copyrighted materials, or other information relating to the rights or interests of Customer or third parties.
- Customer is responsible for ensuring, before making information available to an AI Client, that Customer and the relevant Users have all necessary rights, permissions, notices, consents, internal approvals, and other lawful authority required to disclose, transmit, or permit the use of such information by the applicable Third-Party Service.
- Customer and Users must comply with Customer’s internal information security policies, generative AI policies, confidentiality obligations, contractual obligations to third parties, and other requirements applicable to their use of the MCP Integration Feature.
- Customer is responsible for ensuring that it has all necessary intellectual property rights, licenses, or permissions to make Customer Content available to or use Customer Content with an AI Client.
- For purposes of Section 6.4 of the Terms, making Customer Content available to an AI Client through the MCP Integration Feature will be treated as submitting information to an AI feature. Accordingly, Customer and Users must not use the MCP Integration Feature to transmit or make available any information prohibited by Section 6.4 of the Terms, including health or medical information, biometric or genetic data, children’s data, precise geolocation, government-issued identification numbers or documents, financial account credentials, authentication secrets, special-category or similarly sensitive personal information, criminal-history information, or Personal Information of individuals located in Restricted Regions.
- Provider may take any blocking, deletion, suspension, restriction, or other protective measures permitted under the Terms if prohibited information is submitted or made available through the MCP Integration Feature.
5. Third-Party AI Services and Handling of Information
- An AI Client and any other external service connected through the MCP Integration Feature are Third-Party Services provided independently of Provider. Their use is governed by the terms of service, privacy policies, data-use terms, and other conditions established by the applicable third-party provider.
- For clarity, an AI Client selected and connected by Customer or a User through the MCP Integration Feature is treated as a Customer-configured Third-Party Service under the Terms and is not treated as a Subprocessor of Provider solely by virtue of Customer’s or a User’s decision to connect or use that AI Client.
- Customer and Users are responsible for reviewing the terms applicable to an AI Client or other Third-Party Service before enabling or using the applicable connection.
- After an AI Client or other Third-Party Service obtains information from MONJI+, the storage, retention, use, training or improvement of AI models or services, geographic location of processing, onward transfer, subcontracting, deletion, and other handling of such information may be governed by the terms and practices of the applicable third-party provider.
- Revoking an AI Client connection, terminating an authorization, or ceasing use of the MCP Integration Feature does not necessarily cause information previously obtained by the AI Client or other Third-Party Service to be deleted.
- Provider does not control or guarantee the deletion, retention period, use for AI training or service improvement, processing location, onward transfer, or other handling of information already obtained by an AI Client or other Third-Party Service to the extent such matters are outside Provider’s reasonable control.
- Provider may display explanations, notices, or links concerning an AI Client’s or Third-Party Service’s handling of information on an authorization screen or elsewhere in the Service. Such information is provided to assist Customer and Users and does not modify the terms, privacy policies, or other conditions established by the applicable third-party provider, nor does it constitute a guarantee by Provider regarding that third party’s handling of information.
6. Use of AI Clients and Generative AI
- Information generated, summarized, analyzed, proposed, or otherwise processed by an AI Client or generative AI may contain inaccurate, outdated, incomplete, inappropriate, misleading, or unintended content.
- Customer and Users are responsible for reviewing and validating information generated or presented by an AI Client or other generative AI before relying on or using such information.
- Provider does not warrant the accuracy, completeness, timeliness, usefulness, fitness for a particular purpose, legality, or non-infringement of information generated or processed by an AI Client or other Third-Party Service.
- To the maximum extent permitted by applicable law and subject to the limitations and exclusions set forth in the Terms, Provider is not responsible for loss or damage arising from the operation, output, specifications, modification, suspension, discontinuation, or other conduct of an AI Client or other Third-Party Service that is outside Provider’s reasonable control.
- Nothing in this Section limits Provider’s responsibility, if any, under the Terms, the DPA, or applicable law for the MCP server, authentication, authorization, access-control mechanisms, or other components of the MCP Integration Feature that are operated and controlled by Provider.
7. Prohibited Conduct Relating to the MCP Integration Feature
Without limiting the prohibited conduct set forth in the Terms, Customer and Users must not:
- access, or attempt to cause an AI Client to access, information in MONJI+ beyond the permissions assigned to the relevant User or granted to the AI Client;
- unlawfully or improperly obtain, use, provide, transfer, lend, disclose, or otherwise misuse credentials, access tokens, or other authentication or authorization information used in connection with the MCP Integration Feature;
- circumvent, disable, defeat, or attempt to bypass authentication, authorization, access controls, rate limits, role-based permissions, or other security or technical restrictions applicable to the MCP Integration Feature or the Service;
- use an unauthorized, malicious, or improperly configured AI Client, program, or other means to access the MCP Integration Feature or the Service or to cause unauthorized requests to be made;
- without all necessary rights, permissions, consents, or other lawful authority, cause Personal Information, confidential information, trade secrets, non-public information, or other information relating to the rights or interests of a third party to be obtained, transmitted, or used by an AI Client or other Third-Party Service;
- use the MCP Integration Feature to engage in or facilitate unauthorized access to MONJI+, a Third-Party Service, or any other system, or otherwise violate applicable law;
- unlawfully damage, alter, disclose, compromise, or otherwise improperly handle the data, accounts, networks, systems, or other information assets of Provider, another Customer or User, or any third party;
- impair or threaten the security, integrity, availability, or normal operation of the MCP Integration Feature or the Service; or
- engage in any other conduct substantially similar to the foregoing that Provider reasonably determines is likely to interfere with the secure provision or operation of the MCP Integration Feature or the Service.
8. Records, Security Measures, and Suspension of Connections
- Provider may, to the extent reasonably necessary to verify acceptance of these MCP Additional Terms, provide and secure the MCP Integration Feature, prevent misuse, investigate incidents, verify access activity, or otherwise operate the Service, record information including:
- whether and when these MCP Additional Terms were accepted;
- the applicable version of these MCP Additional Terms;
- MCP-related administrative settings and role-based permission configurations and changes;
- the connected AI Client;
- the permissions granted to the AI Client;
- the relevant User and account;
- access dates and times;
- access targets; and
- access results and other MCP Integration Feature usage information.
- Except where clearly erroneous, Provider’s records of acceptance, administrative settings, role-based permissions, authentication, authorization, access logs, and other system records may be used as reasonable evidence for determining whether, when, and how Customer or a User accepted these MCP Additional Terms, enabled or used the MCP Integration Feature, authorized an AI Client, or accessed information through the MCP Integration Feature.
- If Customer or a User becomes aware of an unfamiliar or unauthorized AI Client connection or other suspected unauthorized access, Customer or the User must promptly revoke the relevant connection and, where appropriate, notify Provider.
- If Provider reasonably determines that unauthorized access, misuse, a security issue, abnormal AI Client behavior, violation of these MCP Additional Terms, or another circumstance threatens the safe provision of the MCP Integration Feature, Provider may, without prior notice where reasonably necessary, suspend all or part of the MCP Integration Feature or revoke or restrict a connection or access permission.
9. Integration into the MONJI Terms of Service
- If Provider incorporates the substance of these MCP Additional Terms into the Terms or another applicable agreement governing the Service, the incorporated terms will apply to use of the MCP Integration Feature from the effective date of the revised agreement.
- Use of the MCP Integration Feature occurring before the effective date of such revised agreement will remain subject to the version of these MCP Additional Terms applicable at the time of such use.
- If the revised MONJI Terms of Service currently planned to become effective on September 28, 2026 become effective on that date and incorporate the substance of these MCP Additional Terms, use of the MCP Integration Feature on and after September 28, 2026 will be governed by those revised Terms.
10. Effective Date
Established and effective: September 8, 2026