> 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/getting-started/quickstart.md).

# Quickstart

Get from sign-up to a live MCP server in about five minutes.

> **Tip:** The dashboard's **Getting started** checklist tracks these steps for you and links to each page as you go — see [Onboarding checklist](/guides/onboarding-checklist.md).

## Prerequisites

Pick the path that matches your API:

* **Generic OpenAPI** — a reachable Swagger/OpenAPI document URL (and OAuth `authorize`/`token` URLs if your API uses OAuth).
* **Bubble** — a Bubble app with its API enabled (Bubble Settings → API → Enable the Bubble API) and a Bubble OAuth app configured (Bubble Settings → API → 3rd Party OAuth / SAML Access).

***

## Step 1 — Sign up and create a workspace

Go to the FlowCP dashboard and sign up. A workspace is created for you automatically. All apps and servers you create live inside this workspace.

***

## Step 2 — Connect your API

1. Click **New connection** in the sidebar (or navigate to `/connect`).
2. Choose a **Provider** — **Generic OpenAPI** or **Bubble**.
3. Enter a **Display name** (used only inside FlowCP).
4. Then, depending on the provider:

   **Generic OpenAPI**

   * Paste your **Swagger / OpenAPI URL** (e.g. `https://api.example.com/openapi.json`).
   * Click **Continue to import**. FlowCP fetches the document to confirm it is reachable, then imports it into a single **Default** branch. There is no ownership-verification step.

   **Bubble**

   * Enter your **Bubble App ID** — the subdomain of your Bubble URL. For example, if your app lives at `myapp.bubbleapps.io`, enter `myapp`.
   * Click **Continue to verification**, then add a Bubble page with the verification token slug and click **Check Verification**.
   * After verification, FlowCP creates two **versions** — **Live** and **Main** (the `/version-test/` development version).

See [Managing branches](/guides/manage-branches.md) to add or remove branches.

> **Switching apps:** Once you have one or more apps, use the **app selector** in the header (to the left of the breadcrumb) to switch between them or to connect a new app. The sidebar always shows the menu for the currently selected app, organized into **Build** (Tools, Skills, Widgets, Prompts, Resources), **Configure** (Servers, MCP Auth, Settings), **Monitor** (Health, Stats, Logs, Alerts), and **Support** (Feedback).

***

## Step 3 — Review the import

Open the branch's **Tools** to see all endpoints found in the imported document. If an import fails, see [Troubleshooting](/support/troubleshooting.md).

***

## Step 4 — Enable tools

Navigate to the **Tools** tab. Every endpoint starts **disabled** by default — FlowCP never exposes a tool until you explicitly turn it on.

1. Enable each endpoint you want AI clients to be able to call.
2. Optionally rename the tool or edit its description to give the AI clearer context.
3. Check the **risk level** badge: `read`, `write`, or `destructive`. Destructive tools (`DELETE` endpoints) require the **Require confirmation** toggle to be on before you can deploy.

***

## Step 5 — Configure OAuth

Navigate to **MCP Auth** in the sidebar, click **Add config**, and choose **User OAuth**.

1. Enter the **Client ID** and **Client Secret** for your API's OAuth app. For a generic provider, also enter the **authorize** and **token** URLs and any scopes. For Bubble, find these under Bubble Settings → API → 3rd Party OAuth / SAML Access.
2. Copy the **OAuth redirect URI** shown on the page (`https://api.flowcp.io/oauth/callback`) and add it to your OAuth app's allowed redirect URLs.
3. Click **Save**.

***

## Step 6 — Chat-test in the Playground

Before deploying, open **Playground** under your server to talk to a model that calls your tools for real. Save your own [OpenRouter](https://openrouter.ai/keys) API key, click **Connect account** to authorize, then chat and watch the tool calls and results. See [Chat-test your MCP server](/guides/chat-test-your-mcp-server.md) for details.

***

## Step 7 — Test in development, then deploy

Navigate to **Deploy** under your server.

**Test first:** copy the **Development URL** snippet and add it to your AI client. The development endpoint is available immediately — no deploy needed, and only workspace members can reach it.

**Deploy when ready:**

1. If any enabled destructive tools are missing the confirmation flag, the deploy button is blocked — fix those first.
2. Click **Deploy to Production**. The status changes to **Production**.
3. The **Production URL** panel appears. Select the tab for your AI client (Claude Desktop, Cursor, or ChatGPT) and copy the JSON.

***

## Step 8 — Add the config to your AI client

Paste the copied JSON into your AI client's config file:

* **Claude Desktop** — `claude_desktop_config.json`
* **Cursor** — `.cursor/mcp.json` (or Cursor's MCP settings panel)
* **ChatGPT** — the MCP server settings in the ChatGPT desktop app

Restart the AI client. Your tools should now appear in the tools list.

***

## What's next?

* [Monitor execution logs](/guides/publish-your-mcp-server.md) to see every tool call
* Read about [how user-context OAuth works](/security/user-context-oauth.md)