> 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/what-is-flowcp.md).

# What is FlowCP?

FlowCP is a hosted platform that converts any API with a Swagger/OpenAPI document into an MCP (Model Context Protocol) server. AI clients — Claude Desktop, Cursor, ChatGPT, and any other MCP-compatible tool — can then call your endpoints as if they were native AI tools.

FlowCP supports any provider through an adapter model. The **Generic OpenAPI** provider connects any API that publishes a Swagger/OpenAPI document, and the **Bubble** provider adds Bubble-specific conveniences (connect by App ID, automatic Swagger discovery, Live/Main branches). Both produce the same kind of hosted MCP server.

## The core promise

Every MCP call runs in the end user's own OAuth session. FlowCP never uses a shared admin token to act on a user's behalf. When a user's AI client calls a FlowCP tool, it is their account making the API call — with their permissions and their data visibility.

## How it fits together

```
Your API  (any Swagger/OpenAPI document; app, etc.)
      │
      │ Swagger / OpenAPI document
      ▼
   FlowCP
      │  imports endpoints → generates MCP tools
      │  enforces per-user OAuth
      ▼
  MCP server  (/mcp/<server-id>)
      │
      ▼
  AI client (Claude Desktop, Cursor, ChatGPT…)
```

1. You connect an API. For a generic provider you paste the Swagger/OpenAPI URL; for Bubble you enter your Bubble App ID and FlowCP discovers the Swagger spec automatically.
2. FlowCP parses every API endpoint and creates a corresponding MCP tool.
3. You review the tools, enable the ones you want, and configure OAuth.
4. You publish the server and copy a config snippet into your AI client.
5. When your AI client calls a tool, FlowCP resolves the requesting user's token, validates the input, and proxies the call to your API.

## Who is FlowCP for?

* **API teams and SaaS builders** who want to expose their product to AI workflows without writing a custom MCP integration.
* **Bubble developers and agencies** who want to connect apps (or multiple client apps) to AI clients with zero glue code.
* **Anyone with an OpenAPI-documented API** who wants per-user, OAuth-scoped AI access.

## Next steps

Follow the [Quickstart](/getting-started/quickstart.md) to get a live MCP server running in about five minutes.