MCP integration

Use Aitane from the AI tools you already use

MCP (Model Context Protocol) is a shared standard that lets AI apps talk to external services safely. Aitane provides an MCP server so that MCP-compatible AI tools such as Claude, Claude Code, ChatGPT, and Notion can look up Aitane customer and deal information and request actions. The conversation stays in the tool you already use; Aitane keeps control of the data and the permissions.

• Because MCP is an open standard, any compatible client can connect, even one that is not in the catalog. Settings > Aitane MCP lists the common apps and links to each app's official site or setup documentation
• Requests from external AI tools run on the same AI core as the web AI chat and Aitane on LINE. Whichever entry point you use, what you can see and do follows the same permissions you have in Aitane
• Ask "What is the latest with Sample A Inc.?" or "Analyze my deal pipeline this month" and the external AI answers from Aitane data, so you can also use it for documents and analysis

Connect through an OAuth consent screen

Connecting uses OAuth 2.1 authorization, not pasted API keys or tokens. When you add Aitane as a connection in the external AI tool, an Aitane consent screen opens. It shows the signed-in user and workspace, lets you choose the permissions (scopes) to grant, and completes the connection when you choose Allow.

• You can connect whether you sign in to Aitane with a Google or a Microsoft account
• The consent screen separates read permissions such as viewing deals, meetings, tasks, and contacts from write permissions such as updating deal stage and next action or sending minutes emails and follow-up messages. Write permissions are highlighted as permissions that need care
• Connected tools appear in the Connected list under Settings > Aitane MCP together with the scopes you granted, and you can revoke any of them from Aitane at any time. Revoking invalidates the issued tokens
• When a member is deactivated or leaves, their connections are revoked automatically

What external AI can read, and the published tools

Aitane MCP publishes a small, curated set of tools that are easy for AI to use well. Alongside tools that search and fetch deals, meetings, tasks, messages, companies, and contacts, it offers tools that return "today's brief" or "items needing action" in one call, so the external AI reaches an answer in fewer round trips.

• Read tools such as search (aitane_find), detail lookup (aitane_get), meeting lists, message threads, and full text of minutes or transcripts (aitane_resource_get)
• Outcome-oriented tools such as aitane_brief_today, which summarizes what needs attention today, and aitane_queue_list, which returns items needing action
• Every tool takes simple inputs and returns structured results with a JSON Schema. Errors include the cause and how to fix it, so the AI can rephrase and retry on its own
• No general-purpose HTTP or code-execution tools are published. Text that originates outside Aitane, such as minutes or email bodies, is returned with a note that it should be treated as untrusted input

Changes run only after you review them and answer "Yes"

A request from an external AI never changes Aitane data on its own. For actions that modify data, such as updating a deal stage or next action or sending minutes emails and follow-up messages, the external AI shows who made the request and exactly what will change, and the action runs only after you review it and answer "Yes".

• If you answer "No" or do not answer, nothing is changed
• Permissions of the person who made the request are checked again just before the action runs. If they no longer allow it, it does not run
• Email and message recipients are limited to people already in Aitane, such as meeting attendees and deal contacts. Messages cannot be sent to arbitrary addresses
• Write tools carry duplicate protection (an idempotency key), so a request that arrives twice does not run twice
• A change requested from a connection without write permission, or from a read-only role, is not executed; the AI is told that permission is missing and how to resolve it

Permissions, admin controls, and audit

Actions through external AI pass a double gate: the scopes granted on the consent screen and the role you hold in Aitane (RBAC) must both allow them. Workspace admins can enable or disable external AI connections for the whole workspace under Settings > External AI, and while disabled every access is rejected, including existing connections.

• External AI connections are off by default. Members can request activation from the settings screen, and admins receive an in-app notification
• Viewer, external, and auditor roles never see write permissions on the consent screen and remain read-only
• External AI can only read and act on data in your own workspace that your permissions allow. Data in other workspaces is never accessible
• Tool calls made through external AI are recorded in Aitane's activity records as MCP activity. Connections that go unused for a long time expire automatically, and the member who connected them is notified

Supported clients, plans, and rollout

MCP integration is available to workspaces on the Standard plan and above. Delivery starts with OAuth connection, connection management, and the search tool, followed by the full tool set and the confirmation flow for actions that change data.

• During the beta we verify connections from Claude (web and desktop), Claude Code, ChatGPT, and Notion. Other MCP-compatible clients not in the catalog can connect under the standard as well
• Listings in each AI tool's official connector directory will follow after the beta
• An "External AI" badge and per-user filter in the AI activity screen, and an admin view of every member's connections, are candidates for after the beta
• The AI will not send email or make other changes without confirmation. Allowing automatic execution only for reversible, low-risk actions is a future consideration

How it works

1. Use Aitane from Claude, Claude Code, ChatGPT, and Notion
2. Reference customers, deals, tasks, and other Aitane information
3. Request actions and review changes before they run

What it looks like in practice

Keep using the AI tools you prefer while Aitane provides shared business context and a safe confirmation point.