> For the complete documentation index, see [llms.txt](https://docs.flowcp.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowcp.ai/guides/ready-to-use-connectors.md).

# Ready-to-use connectors

**Ready-to-use APIs** are pre-built connectors curated by FlowCP. Instead of pasting an OpenAPI URL and configuring everything yourself, you pick a connector from a catalog and FlowCP creates a **hosted MCP server in your workspace** for that API — with its tools already generated. You bring your own OAuth credentials, and the connector stays up to date as FlowCP maintains it.

> **Not the same as the** [**Connector library (remote MCP servers)**](/guides/mcp-connector-library.md)**.** That catalog lets you attach *external, already-hosted* MCP servers (GitHub, Notion, …) to a chat widget. Ready-to-use connectors instead create a **first-party MCP server you own**, running on FlowCP under your own server ID, in each end-user's own authorization context.

Open **Connectors** in the sidebar and select the **Ready-to-use APIs** tab.

> **Platform admins:** the catalog is empty until you connect a connector repository and sync it. See [Set up the connector library](/guides/set-up-connector-library.md).

## Browse the catalog

Search or filter by category to find a connector. Each card shows the authentication type, how many endpoints (tools) it will generate, and a link to the provider's developer docs.

## Add a connector to your workspace

1. Click **Add to workspace** on a connector.
2. Give the app a name (defaults to the connector's name) and click **Create server**. FlowCP creates a new app and a **Default** MCP server with its own server ID and imports the API to generate your tools.
3. **Connect your account.** How this step works depends on the connector's authentication:
   * **User OAuth** (most connectors) — enter the **Client ID** and **Client Secret** from *your own* OAuth app with the provider. The authorization and token URLs and scopes are prefilled from the connector; you only supply your credentials. Use the **"Where do I create an OAuth app?"** link to reach the provider's developer settings. Add FlowCP's OAuth **redirect URL** (shown in the form) to your OAuth app.
   * **API key / bearer** — you'll be pointed to the app's **MCP Auth** page to add the shared workspace credential.
   * **Open** — nothing to configure.
4. Go to the app's **Tools** page and **enable** the tools you want. As always, tools start **disabled** (default-deny), and destructive tools require confirmation.
5. **Deploy** the server from its **Deploy** page and connect to it from any MCP client.

Your credentials are stored encrypted (AES-256-GCM) and are never shown again. FlowCP never ships credentials in a connector — you always bring your own.

## Staying up to date

A ready-to-use connector stays linked to the FlowCP catalog. When FlowCP updates a connector's API definition, your server's tools are re-imported automatically:

* **New tools** arrive **disabled**, so nothing is exposed without your say-so.
* **Your customizations are preserved** — enablement, confirmation settings, and any manually authored tools survive re-imports.

You can see that an app came from the catalog on its **App details** page, which notes the connector it was created from.

## Removing a connector

A ready-to-use connector is an ordinary app once created. Delete it like any other app from its **Settings → Danger** page. If FlowCP removes a connector from the catalog, your app keeps working — it simply stops receiving catalog updates.