# Elaichi — Governed MCP servers for your whole company

> Connect every SaaS product your teams use, compose curated MCP toolboxes, and hand every user a personal, permission-clamped MCP endpoint for Claude, Cursor, or any MCP client — governed by roles, restrictions, and audit logs.

Elaichi is a governed MCP control plane for companies.

## What it does

1. **Connect** — browse a catalog of 200+ connectors and connect SaaS accounts at user, team, or org scope. Credentials are vaulted and encrypted; end users never see them.
2. **Compose** — every connection instantly becomes a toolbox of MCP tools, or curate template toolboxes with renamed tools, frozen parameters, schema overrides, and defaults.
3. **Mint** — create an MCP endpoint on any toolbox and paste the URL into Claude Desktop, Cursor, Dust, or any MCP client.
4. **Govern** — roles decide who can do what, restrictions decide which connectors and tools are even visible, and every privileged action lands in an append-only audit log.

## Key capabilities

- 200+ pre-built SaaS connectors
- Curated MCP toolboxes with frozen parameters and per-tool overrides
- Delegated connections — share access without sharing credentials
- Personal permission-clamped MCP endpoints for Claude, Cursor, and any MCP client
- Role-based access control with custom roles
- Connector and tool restrictions with org/role/user precedence
- Append-only audit log with Datadog forwarding
- Synthetic tools — compose multiple tools into one
- Custom and forked connectors with upstream pull
- Enterprise SSO (SAML/OIDC), SCIM provisioning, BYOK encryption
- Desktop companion app that writes Claude Desktop and Cursor configs

## FAQ

### What is an MCP control plane?

An MCP control plane is a central system that manages how a company creates, shares, and governs Model Context Protocol (MCP) servers. Instead of each employee minting ad-hoc MCP servers with personal API keys, Elaichi connects your SaaS tools once, turns them into curated toolboxes, and hands every user a personal MCP endpoint clamped by roles, restrictions, and audit logging.

### How does Elaichi work?

Four steps. Connect — pick from 200+ connectors and finish a hosted connect flow; credentials are vaulted and encrypted. Compose — every connection instantly becomes a toolbox of MCP tools, or you curate a template toolbox with renamed tools, frozen parameters, and defaults. Mint — create an MCP endpoint on any toolbox and paste the URL into Claude Desktop, Cursor, or any MCP client. Govern — roles decide who can do what, restrictions decide which tools are even visible, and every call lands in an append-only audit log.

### How do I give my team MCP servers without sharing API keys?

With delegated connections. In Elaichi, a shared toolbox can expose the sharer's connection: recipients call the third-party API through it without ever seeing credentials. Every call is clamped server-side by the toolbox's tool list, frozen parameters, and restrictions.

### Which AI clients work with Elaichi?

Any MCP client that speaks Streamable HTTP — Claude Desktop, Cursor, and Dust connect directly today. Elaichi MCP endpoints speak standard MCP JSON-RPC (initialize, tools/list, tools/call), and the desktop companion app writes Claude Desktop and Cursor config files for you.

### What are frozen parameters?

Frozen parameters are tool arguments fixed by the toolbox curator and stripped from the schema the model sees. They are force-merged at execution time, so the AI can never see or override them — for example pinning a Google Drive tool to one specific folder.

### What happens when a toolbox has too many tools for the model's context?

Toolboxes exposing more than about 30 tools automatically advertise just two meta-tools — search_tools(query) and execute_tool(name, arguments) — so large toolboxes stay out of the model's context window. This behavior is configurable per MCP server.

### Does Elaichi store my SaaS credentials?

Third-party credentials are held in a dedicated credential vault, encrypted at rest with AES-256-GCM, and are never exposed to end users or to the AI. Session, API, and MCP tokens are stored as keyed hashes and shown only once. Enterprise plans can bring their own AWS KMS keys.

### Can I build a connector for an internal API?

Yes. Custom connectors let you author a connector from a JSON config — base URL, auth, resources, and methods — or fork any of the 200+ public connectors, including its documentation. Forks track upstream lineage, so you can review and selectively pull upstream improvements later.

### How is Elaichi different from running my own MCP servers?

Self-hosted MCP servers multiply credentials, have no shared governance, and leave no audit trail. Elaichi centralizes connections with vaulted credentials, applies role-based access control and allow/blocklists at connect, advertise, and execute time, logs every tool call, and lets admins revoke or rotate any endpoint instantly.

Learn more: [Product](https://elaichi.ai/product/) · [Pricing](https://elaichi.ai/pricing/) · [Security](https://elaichi.ai/security/) · [Sign up](https://app.elaichi.ai)