MCP.so
Sign In

Elaichi MCP ServerVerifiedFeatured

Basic information

Transport

Streamable HTTP

Authentication

OAuth

Category

Data & Analytics

Submitted by

Uday

About Elaichi MCP Server

Elaichi is a governed remote MCP server for companies. Connect the apps your teams already run — 400+ connectors — and point Claude, ChatGPT, Cursor, any MCP client or the Elaichi Agent at one org-wide endpoint over OAuth. Each person signs in as themselves, so every call runs inside the access they already have. Admins restrict which tools each role can reach, and every call lands in an append-only audit log.

Connection details

https://api.elaichi.ai/mcp

Setup

claude mcp add elaichi --transport http https://api.elaichi.ai/mcp

Elaichi MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

This server requires authentication. Tool discovery may require signing in or credentials from the provider.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is Elaichi

Elaichi is an agent platform for companies. It connects the software your teams already run on and turns it into tools an agent can call — from Claude, ChatGPT, Cursor, any MCP client, or the Elaichi Agent — while every call stays inside the permissions that person already has.

One org-wide endpoint, https://api.elaichi.ai/mcp, the same URL for every organization and every person. There is no per-team or per-person URL to distribute, and no token embedded in a config file.

How it works

  1. An admin connects an application once, from a catalog of 400+ connectors.
  2. Anyone on the team points their MCP client at the endpoint and signs in with OAuth.
  3. The agent calls tools as that person, resolved against their current role at the moment of the call.

Standard MCP over Streamable HTTP. Nobody ever handles a credential — not the person sharing a connection, and not the person using it.

Governance

  • Your agent gets exactly the access you have. Nothing more. Permissions are resolved per call, not per key.
  • Restrictions are per tool, set on a role or on one person. A restricted tool is never advertised to the model, so no prompt can reach it.
  • Every action, attributed. Calls land in an append-only audit log with the person, the tool and the result.
  • Third-party credentials sit in a dedicated vault, encrypted at rest, and are never returned by the API — not to users, admins or agents.

Records are read from the source at the moment of the call, so an agent never answers from a stale copy.

What is connected

400+ connectors across CRM, helpdesk, HRIS, accounting, ticketing, marketing automation, cloud storage and more. A few of the larger categories:

Any documented API can become a connector.

Getting started

Start a 14-day free trial on Gold, no credit card. Connect one app and one team, point your client at the endpoint, and go. When a trial ends nothing is deleted — connections, roles and the audit log stay where they are.

Frequently asked questions

1

What is the Elaichi remote MCP server?

The Elaichi remote MCP server is a hosted Model Context Protocol endpoint at https://api.elaichi.ai/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the Elaichi MCP server?

Add the endpoint https://api.elaichi.ai/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the Elaichi MCP server require authentication?

Yes. Elaichi uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the Elaichi MCP server use?

Elaichi exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments