Skip to main content
Admissions are openCall +880 1758-395001 for Standard VI to A Level-A2 Cambridge classes.

AI Connector Terms

Rules for the complete student, staff, faculty, and administrative MCP connector.

Last updated: 27 August 2026

1. Acceptance and scope

These terms apply when you connect or use the Samim's Tutorial MCP server from an AI client. They supplement the ordinary student enrollment, staff, faculty, administrator, and Platform rules that already apply to your account. By connecting or invoking a tool, you agree to these connector terms and our Privacy Policy.

2. Eligible accounts

You must have an active Platform account and authority to use the information or action requested. A student may use only the student capabilities exposed to that account. Staff, faculty, and administrator tools are available only when current Platform roles and permissions allow them. Access shown by an AI client is not a substitute for institutional authorization.

3. Authentication and account responsibility

OAuth is used to connect the client without giving it your Platform password. You are responsible for protecting your account, reviewing requested scopes, securing the device and AI-client account used to connect, and disconnecting access that is no longer needed. Do not share access tokens, refresh tokens, authorization codes, passwords, OTPs, or idempotency keys.

4. Read and write access

mcp.read permits authorized retrieval. mcp.write is required for tools that change Platform state. Every write remains subject to live role, permission, ownership, enrollment, roster, state, and validation checks.

Mutating tools require explicit confirmation and an idempotencyKey. Confirmation means you reviewed the proposed action and intend it to occur. Idempotency reduces accidental duplicate execution; it does not make an incorrect or unauthorized instruction acceptable.

5. Privileged use

Staff, faculty, and administrators must use academic, exam, result, attendance, leave, notice, and directory tools only for legitimate assigned work. Destructive actions—including overwriting records, synchronizing authoritative state, cancelling items, changing lifecycle state, acknowledging on behalf of the current account, or publishing results—must be reviewed carefully before confirmation.

6. Acceptable use

  • Do not attempt to access another person's records without authorization.
  • Do not bypass role, scope, confirmation, rate, validation, or audit controls.
  • Do not use the connector for harassment, discrimination, impersonation, academic misconduct, surveillance, or unlawful activity.
  • Do not submit secrets, payment-card information, government identifiers, or unrelated sensitive information through free-text fields.
  • Do not automate high-volume writes or destructive actions without a separately approved operational process.

7. AI client providers

The connector can be used with compatible third-party clients, including OpenAI and Anthropic products. Those providers operate their own services and process prompts, tool arguments, and results under their own terms. Samim's Tutorial does not control the provider's model output. Review generated summaries and every proposed write; the authorized Platform result remains the source of record.

8. Availability and changes

We may change tools, schemas, limits, permissions, or availability to protect users, correct behavior, meet institutional needs, or maintain compatibility. A connector or tool may be suspended when it is insecure, unstable, misused, or no longer supported. We do not promise uninterrupted availability or that model-generated wording will be accurate.

9. Suspension and termination

We may suspend or revoke a connector grant, OAuth client, tool, or account when required for security, policy enforcement, account termination, permission removal, or legal obligations. Users may end connector access at any time by disconnecting it in the AI client. Ending connector access does not remove records that must remain in Platform for educational, administrative, audit, security, or legal reasons.

10. Support and updates

Report connector problems through our contact page. Include the affected tool and approximate time, but never send passwords, tokens, OTPs, or full student records in an initial support message. We may update these terms; the published date identifies the current version.