AI apps around the world
Explore regional assistants, coding clients and familiar global apps. See which ones have a documented route to your iCloud and Microsoft 365 accounts.
Pear is a hosted MCP connection for account tools. The AI app must support remote Streamable HTTP and an authentication method Pear accepts. Choose the exact app or edition: a company can offer a chat app, coding agent and model API with different capabilities.
A guide documents a setup path; it does not certify a completed client connection. Check its authentication notes, account requirements and testing status. Gemini CLI is a separate product from the Gemini consumer app.
These sections cover product and language ecosystems, including newer assistants and established vendors. They are not national market-share rankings or a promise of availability in every country. Plan access, network reachability and data handling need checking for your location.
Documentation checked . Public X posts help identify products to investigate; vendor documentation determines the connection guidance. Missing public instructions are recorded as unknown rather than proof that a feature can never work.
Start with the app you already use. Global assistants and India-built products serve different audiences; a local model or language focus does not by itself provide a connection to your accounts.
Sensor Tower's February 2026 India report identifies generative AI as a leading source of download growth. That supports looking at this market; it does not establish an adoption ranking for the local products below. Existing ChatGPT, Claude, Grok and Perplexity guides remain relevant wherever those services and the required plans are available.
Sarvam introduced Indus in February 2026 as a limited beta built for the Indian context. Its consumer interface is separate from Sarvam’s developer products.
No public Pear setup found for the Indus app. Sarvam publishing its own MCP server does not make Indus a Pear client.
Zia Chat advertises connections to external tools through MCP. Its current page describes early access in India and US data centers.
MCP advertised; the reviewed page does not document the remote transport or authentication settings needed for Pear. Setup remains unverified.
Jio’s workplace assistant documents its own Microsoft 365 account connection.
A native Microsoft connection is not a custom Pear connection. No user-configurable Pear MCP setup is established by the reviewed account documentation.
Choose the exact product: a company’s consumer chat app, coding client and model API can have different connection capabilities. The guides below cover the named coding clients.
Qwen Code documents remote HTTP MCP servers with a private Authorization header. Its configuration uses httpUrl.
Setup guide available; authenticated Pear use is still unverified. This is not a setup guide for the consumer Qwen chat app.
Kimi Code supports remote MCP connections from its coding client and provides a personal MCP configuration.
Setup guide available for Kimi Code. It does not establish MCP support in the consumer Kimi chat app; Pear host testing remains pending.
Qoder Work has a connector interface for Streamable HTTP servers and request headers.
Setup guide available for the Work desktop app. Qoder CLI has a different configuration schema; authenticated Pear testing remains pending.
TRAE documents manually configured remote MCP servers with a URL and headers.
Setup guide available for the documented IDE interface. Confirm the controls in your installed edition; authenticated Pear testing remains pending.
DeepSeek offers a consumer assistant and a separate developer API.
No public Pear setup found for the consumer app. Using a DeepSeek model through another MCP-capable client is a separate route.
Doubao is ByteDance’s consumer assistant. It is a different product from the TRAE coding IDE.
No public custom Pear MCP setup found for the consumer app. A TRAE setup guide does not apply to Doubao.
Z.ai documents an API capability for calling third-party MCP servers over remote transports, including custom request headers.
Developer API route documented; this is not a verified Pear connection in the consumer chat app. A developer must implement and test the agent, account access and approvals.
CodeBuddy documents MCP connections in its agent SDK, including remote HTTP servers.
Developer SDK route documented. Do not treat SDK configuration as proof that the same controls exist in every CodeBuddy IDE or Tencent Yuanbao interface.
Cherry Studio is a multilingual desktop client with remote MCP support and a choice of model providers.
Remote MCP is documented. Pear-specific authentication and a complete client test are still unverified; check the current server settings against the generic requirements.
Mistral’s coding CLI and workplace assistant expose different authentication controls. Choose a guide for the product you are using, rather than applying a legacy Le Chat tutorial to every Mistral interface.
The Vibe Code CLI documents Streamable HTTP and API-key configuration. Its current MCP documentation says OAuth is not supported by the CLI.
Setup guide available using an environment-backed Bearer key. Authenticated Pear host testing remains pending.
Work documents custom MCP connectors and detects authentication automatically. It lists Bearer tokens and OAuth with dynamic client registration.
Readiness guide available. Whether Work offers the Bearer path for Pear remains unverified; its documented DCR OAuth flow is not a proven match for Pear’s CIMD flow.
Localized assistants can connect to selected services without allowing users to add an arbitrary MCP server. Japanese or Korean availability also does not establish where connected data is processed.
Genspark publishes Japanese help content and documents custom or community MCP connections alongside its native integrations. This is a global product, not a claim of Japanese market leadership.
MCP documented; the reviewed help page does not establish the exact Pear transport and Bearer-header setup. Pear compatibility remains unverified.
Kakao introduced Kanana as a Korean assistant product. Kakao’s wider distribution is not a measurement of Kanana’s own usage.
No public custom Pear MCP setup found in the reviewed product information.
NAVER announced an assistant for public-service workflows in its app in March 2026.
The announcement describes native service integrations, not user-configured Pear MCP connections.
A regional assistant, its underlying model and its developer platform are separate integration targets. Confirm the client interface before providing a personal API key.
Jais Chat is an Arabic-focused assistant associated with MBZUAI, with mobile apps.
No public custom Pear MCP setup found. Access to a Jais model is not evidence of MCP controls in the Jais Chat app.
Yandex offers Alice AI and a separate business product with its own integrations.
The reviewed business announcement does not document adding an arbitrary Pear MCP server to the consumer assistant.
Sber documents building a custom agent that uses a GigaChat model and an MCP client.
Developer-built agent route, not a demonstrated custom MCP setting in the consumer GigaChat app. Pear access and approval behavior still need implementation and testing.
If your preferred model is available through another client, configure the model and Pear separately. The client needs to support that model provider, tool calling and Pear's remote MCP authentication. A model working in chat does not prove it can reliably choose or approve account actions.
Use a private API key or the documented OAuth route for your client. Start with pear_provider_status and a bounded calendar or mail read. Inspect a draft before approving writes. A local app may still send provider data to a cloud model; review the complete data path.
The app must act as a remote Streamable HTTP MCP client and support an authentication path Pear accepts. A model API, native calendar integration or separate MCP server does not establish that capability. A setup guide describes a documented route; a complete authenticated client test is separate evidence.
Potentially, through an MCP-capable client that supports that model provider and tool calling. Configure the model in that client and Pear as a separate MCP server. This does not add MCP support to the model vendor’s consumer app. Check language quality, tool use, data handling and availability for the combination you choose.
No. These sections describe product and language context, not tested network reachability, local availability or data residency. Client access, plans, model access, provider accounts and local network conditions can differ. Check the current vendor requirements before connecting.
Pear supports iCloud Calendar, Contacts and Mail, and Microsoft 365 Calendar, To Do, Contacts and Outlook Mail. Apple Reminders support is limited to legacy CalDAV data. Google Workspace remains coming soon. Available actions depend on your account, plan and permissions.
