Docs

What's MindCloud Embedded?

Add 3,400+ app connections to your product with MindCloud Embedded. Compare the API, MCP, and SDK, and learn how end users and installations work.

MindCloud Embedded brings 3,400+ apps into your product, so customers can connect their accounts and use those apps without leaving your experience. MindCloud handles boring part, such as app authentication, credential storage, and provider token refresh so you don't need to worry about that.

You decide what happens after a customer connects an account. Your backend can run an app action. An AI agent can find the right action and run it for that customer. Or your product can offer an integrations page with workflows you build.

Choose how to use Embedded

  • Embedded API lets your backend run app actions with a customer's connection.

  • Embedded MCP gives your server-side AI agent tools to find apps, connect accounts, and run actions for one customer at a time.

  • Embedded SDK adds the connection and installation experience to your product, including integrations with published workflows.

These approaches can work together. For example, a customer can connect an account through the SDK, then your backend can use that installation to run an action through the API.

Understanding Embedded

End user. A customer in your product who uses an integration. MindCloud assigns them an end-user ID. Store it with your own customer ID so later requests act for the right person.

App and connection. An app is an third-party API in the MindCloud catalog. A connection is an end user's authenticated account for that app. MindCloud stores the credentials, so your code does not need the provider's tokens.

Integration. The connection or workflow experience you configure for customers. It can include one or more apps. A connect-only integration gives customers an account to use through the API. A workflow integration gives them published automations to install.

Installation. One end user's instance of an integration. It holds that user's connection and settings. The same person can have several installations, such as two stores connected to one integration.

Workflow. A sequence of steps that you build and publish for a workflow integration. Each installed copy runs with that end user's connections and settings.

Start with Getting Started to enable Embedded, create an API key, and set up end-user identity.