Skip to content

Getting started

Elaichi connects the apps your company already uses to the AI clients your team works in, such as Claude, ChatGPT, Cursor and Microsoft Copilot. It works with any client that supports MCP (the Model Context Protocol, the open standard AI clients use to find and run tools).

You connect an account once, choose which tools to expose, and each person signs in to Elaichi with their own account. Nobody shares credentials, and administrators control what AI clients can reach.

The words Elaichi uses

Term What it means
Organization Your team's workspace in Elaichi. It has its own members, roles, connections and toolboxes. Nothing crosses between organizations.
Connector An app Elaichi knows how to talk to, such as Slack, Jira or Salesforce.
Connection One authorized account for a connector, such as "our shared HubSpot" or "my Jira".
Tool One action an AI client can run, such as "create issue" or "search contacts".
Toolbox A set of tools, often from several connectors, that an AI client can use.
MCP endpoint The one address you paste into an AI client. It is the same text for everyone.
How the pieces connect 
flowchart LR
  Connector["Connector<br/>an app Elaichi supports"] --> Connection["Connection<br/>an authorized account"]
  Connection --> Toolbox["Toolbox<br/>a set of tools"]
  Toolbox --> MCP["MCP endpoint<br/>one address"]
  MCP --> Client["AI client<br/>Claude, ChatGPT, Cursor, Microsoft Copilot"]

In words: a connector describes an app, a connection is your signed-in account for that app, a toolbox groups the tools you want to offer, and the MCP endpoint is how an AI client reaches those toolboxes.

Sign in

Open app.elaichi.ai. Elaichi has no passwords. You sign in with one of these methods:

  • Email code. Elaichi emails you a six-digit code.
  • Passkey. Your device unlocks your account.
  • Google, GitHub or Microsoft.
  • Your company's single sign-on (SSO), if an administrator set it up.

Your account is global. The first time you sign in, you create an organization, accept an invite, or join automatically because an administrator verified your email domain. See Sign in.

Connect your first AI client in three steps

The path to your first working AI client 
flowchart TD
  A["1. Connect an account"] --> B["2. Choose tools<br/>use the automatic toolbox or build one"]
  B --> C["3. Connect your AI client<br/>copy the MCP endpoint"]
  C --> D["Paste the endpoint into your AI client and sign in"]

In words: you connect an app account, you decide which tools to offer, and then you add the Elaichi endpoint to your AI client.

1. Connect an account

  1. Choose Connections in the sidebar, then Add connection.
  2. Select the app, then choose Connect.
  3. If Elaichi asks how you want to sign in, choose OAuth 2.0.
  4. Sign in to the app and approve the access it asks for.

Elaichi stores the credentials in a secure vault and uses them only when a tool runs. A new connection is private to you. You can share it with a member, a team, or everyone in your organization. See Connect an account.

2. Choose tools

Every connection automatically gets a read-only toolbox named "{connection name} tools". It appears on the Toolboxes page under Automatic, so you can start right away.

When you want a smaller, more deliberate set, build your own toolbox. See How toolboxes work.

3. Connect your AI client

  1. Choose Connect in the sidebar. Some organizations see Connect an AI client instead.
  2. Copy the endpoint shown in Connect your AI client.
  3. Add it to your AI client as a remote MCP server, then sign in with your Elaichi account.

Step-by-step instructions: Claude, ChatGPT, Cursor, Microsoft Copilot. The client can then run your tools as you, with your permissions.

Ready-made config files for each client are in the elaichi-mcp repository on GitHub.

What keeps access under control

  • Roles decide what each member can do in Elaichi.
  • Restrictions allow or block connectors and tools for a role or a member. They apply everywhere, including tools reached through MCP.
  • The audit log records meaningful actions, so administrators can see who did what.