Elaichi | Give your AI every app, not every permission

# Elaichi > Elaichi is a governed MCP control plane and hosted MCP gateway. Claude, > ChatGPT, Cursor or any MCP client signs into one organization-wide MCP > endpoint over OAuth, and the Elaichi Agent works inside the app. Both reach > one governed catalog: connectors Elaichi authors and runs itself, and vendors' own MCP servers that Elaichi governs > under the same rules. Two things separate Elaichi from the rest of the MCP category. Direct coverage of the AI clients companies actually use: one URL that Claude, ChatGPT and Cursor all sign into through their own admin consoles, no per-user setup and no per-client fork. And one governed catalog with two kinds of connector: most Elaichi authors, maintains and serves from its own infrastructure, and the rest are native MCP connectors, the vendor's own MCP server, which the vendor builds and runs while Elaichi handles sign-in, access rules and the audit log in front of it. Companies run no MCP servers for either kind, and reports about a native connector's tools go to the vendor's support contact. The safety surface makes that reach usable by staff. Every call is checked against the calling person's current permissions, and logged when it runs; an agent never gets more access than the person it acts for. Facts worth quoting: 58 permissions, 8 predefined roles plus unlimited custom roles, restrictions set on a role or on one person (a person-level rule can only narrow the role's) and enforced everywhere a tool can be reached (listing tools, connecting, saving a toolbox, advertising tools, executing a call, and the outbound request), bring your own keys for 4 model providers, data placement in 3 regions (US, EU, APAC), and zero credentials ever returned by the API. For the catalog size and the full list of supported applications, read https://elaichi.ai/connectors/. There are three cumulative plans, priced per user. Personal is free, for one person (1 member, 10 connections across at most 3 connectors, 10 synthetic

openapi: 3.1.0 info: title: Elaichi API version: 0.1.0 description: "Control-plane HTTP API for Elaichi, the MCP control plane for SaaS teams. Authenticate with an organization API token (create one in the Elaichi app under Settings → API tokens) sent as a bearer token, plus the `X-Organization-Id` header on org-scoped routes; the MCP and OAuth endpoints use their own protocols. A few actions are deliberately not available to an API token and must be done by a person