Floot MCP connector for AI agents

Tools your builder agent reaches for on Floot MCP, scoped per user.

CALL ANY TOOL

OAuth 2.1 app builder tools: projects, files, deps, SQL, preview, publish, and checkpoints on Floot.

flootmcp_add_dependency

Add Dependency

Add npm packages to the project (validated against Floot's supported set : rejected packages get a supported alternative named; some versions are pinned/substituted). Avoid node-gyp/native packages (exception: sharp is supported, auto-pinned), WASM modules, and packages bundling large binaries (e.g. ffmpeg/ffprobe); pure JS/TS preferred. A bare `kysely` installs 0.26.3, the version the generated d

Parameters

Name

Type

Required

Description

packages

array

Required

The npm package names to install, optionally with a version (e.g. "package@1.2.3"). Provide at least one. Packages are validated against Floot's supported set : an unsupported package is rejected with a supported alternative suggested. Avoid native/node-gyp packages, WASM modules, and packages bundl

projectId

string

Required

The unique identifier of the Floot project to add dependencies to. Obtain it from create_project or a project listing.

flootmcp_apply_patch

Apply Patch

flootmcp_cancel_request

Cancel Request

flootmcp_card_upload_asset

Card Upload Asset

flootmcp_copy_file

Copy File

flootmcp_create_checkpoint

Create Checkpoint

flootmcp_create_project

Create Project

flootmcp_delete_file

Delete File

flootmcp_edit_file

Edit File

Replace old_string with new_string in a project file. old_string must match the current content exactly (including whitespace) and be unique unless replace_all is set. Prefer this over write_file for changes to existing files.

Parameters

Name

Type

Required

Description

path

string

Required

Path to the file within the project, following the Floot item scheme (for example, a component's main source file). Identifies which file to edit.

projectId

string

Required

The unique identifier of the Floot project that contains the file to edit. Obtain it from create_project or a project listing.

expected_version

integer

Optional

Optimistic-concurrency guard: the file's last-known version number, as previously returned by a read or edit of this file. If the file has changed since then (a concurrent edit, or a prior tool call already modified it), the edit is rejected instead of silently overwriting the newer content. Omit it

new_str

string

Optional

Alternate field name for new_string : the replacement text. Provide either new_string or new_str (not both), paired with the matching old_string or old_str.

new_string

string

Optional

The text that replaces old_string in the file. Needed together with old_string for the edit to actually change anything, even though the schema marks both optional to accommodate the old_str/new_str alias pair.

old_str

string

Optional

Alternate field name for old_string. Provide either old_string or old_str (not both), paired with the matching new_string or new_str.

old_string

string

Optional

The exact text to find and replace in the file, including whitespace. Must match the current file content exactly, and must be unique in the file unless replace_all is true. Needed together with new_string for the edit to actually change anything, even though the schema marks both optional to accomm

replace_all

boolean

Optional

When true, replaces every occurrence of old_string (or old_str) in the file instead of requiring the match to be unique. When false (the default), the edit fails if old_string appears more than once.

flootmcp_execute_sql

Execute Sql

flootmcp_fetch

Fetch

flootmcp_generate_image

Generate Image

flootmcp_get_current_context

Get Current Context

flootmcp_get_guide

Get Guide

flootmcp_get_guides

Get Guides

flootmcp_get_job_status

Get Job Status

flootmcp_get_logs

Get Logs

flootmcp_get_preview_url

Get Preview Url

flootmcp_get_publish_status

Get Publish Status

flootmcp_list_files

List Files

flootmcp_list_projects

List Projects

flootmcp_list_resources

List Resources

flootmcp_navigate_preview

Navigate Preview

flootmcp_provision_resource

Provision Resource

flootmcp_publish_app

Publish App

Publish the app to production : call for the first publish, to publish again after changes the user wants live, and to set up a custom domain. Omit domain and the user gets the publish form in the editor. Pass mobile: true whenever the user mentions iOS, Android, TestFlight, App Store, Google Play, or a mobile/native app : with no store account connected that returns a Connect card; with one conne

Parameters

Name

Type

Required

Description

projectId

string

Required

The Floot project ID to publish. Get this from list_projects, get_project, or the project you just created.

add_another

boolean

Optional

custom_domain only: the project ALREADY has a custom domain and the user has explicitly asked for an ADDITIONAL one. Without it, a custom_domain call on a project that already has domains returns those domains instead of opening the wizard : so a user whose domain is already connected is told so rat

domain

string

Optional

floot_subdomain only: subdomain label (lowercase, digits, hyphens, max 40). Omit to show the user the publish form instead; on a published app a different subdomain is refused (unpublish_app first, confirming with the user). Ignored for custom_domain : the wizard collects the domain.

domain_type

string

Optional

Omit for the floot subdomain (shows the publish form in the editor when domain is omitted). 'custom_domain' for domain setup : a paid-plan feature (get_publish_status reports `paid`); it fails for free accounts.

include_made_with_floot

boolean

Optional

false removes the 'Made with Floot' badge (paid plans only : fails for free accounts). Omit to keep the current setting.

mobile

boolean

Optional

Set true whenever the request mentions iOS, Android, TestFlight, App Store, Google Play, Play Store, a native or mobile app, or a phone build : they all mean a mobile build. No store account connected → returns a Connect card (nothing published). Connected → publishes the web app with the store buil

skipPaymentsOnboarding

boolean

Optional

true publishes although the owner's payments setup is unfinished; the app's payment screens stay unavailable until it is done.

flootmcp_pull_database_schema

Pull Database Schema

flootmcp_query_database

Query Database

flootmcp_read_file

Read File

flootmcp_read_files

Read Files

flootmcp_remove_dependency

Remove Dependency

flootmcp_rename_file

Rename File

flootmcp_request_external_resource

Request External Resource

flootmcp_request_user_upload

Request User Upload

flootmcp_run_code_in_browser

Run Code In Browser

flootmcp_run_code_in_vm

Run Code In Vm

flootmcp_run_tests

Run Tests

flootmcp_screenshot_preview

Screenshot Preview

flootmcp_search

flootmcp_search_code

Search Code

flootmcp_typecheck

Typecheck

flootmcp_unpublish_app

Unpublish App

flootmcp_update_project_metadata

Update Project Metadata

flootmcp_upload_asset

Upload Asset

flootmcp_view_annotation

View Annotation

flootmcp_write_file

Write File

Build your Agent

Same OAuth 2.1 vault and scoped tool list across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from \"@scalekit-sdk/node\";
import { DynamicStructuredTool } from \"@langchain/core/tools\";
const sk = new ScalekitClient(
  process.env.SCALEKIT_ENVIRONMENT_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET,
);
const page = await sk.tools.listScopedTools(\"user_123\", {
  filter: { connectionNames: [\"flootmcp\"], toolNames: [
    \"flootmcp_meetings_list\",
    \"flootmcp_transcription_get\",
    \"flootmcp_notes_list\",
  ]}, pageSize: 100,
});

import OpenAI from \"openai\";
import { ScalekitClient } from \"@scalekit-sdk/node\";
const sk = new ScalekitClient(
  process.env.SCALEKIT_ENVIRONMENT_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET,
);
const page = await sk.tools.listScopedTools(\"user_123\", {
  filter: { connectionNames: [\"flootmcp\"], toolNames: [
    \"flootmcp_meetings_list\",
    \"flootmcp_transcription_get\",
    \"flootmcp_notes_list\",
  ]}, pageSize: 100,
});
const openai = new OpenAI();

import Anthropic from \"@anthropic-ai/sdk\";
import { ScalekitClient } from \"@scalekit-sdk/node\";
const sk = new ScalekitClient(
  process.env.SCALEKIT_ENVIRONMENT_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET,
);
const page = await sk.tools.listScopedTools(\"user_123\", {
  filter: { connectionNames: [\"flootmcp\"], toolNames: [
    \"flootmcp_meetings_list\",
    \"flootmcp_transcription_get\",
    \"flootmcp_notes_list\",
  ]}, pageSize: 100,
});
const anthropic = new Anthropic();

import { ScalekitClient } from \"@scalekit-sdk/node\";
const sk = new ScalekitClient(
  process.env.SCALEKIT_ENVIRONMENT_URL,
  process.env.SCALEKIT_CLIENT_ID,
  process.env.SCALEKIT_CLIENT_SECRET,
);
const page = await sk.tools.listScopedTools(\"user_123\", {
  filter: { connectionNames: [\"flootmcp\"], toolNames: [
    \"flootmcp_meetings_list\",
    \"flootmcp_transcription_get\",
    \"flootmcp_notes_list\",
  ]}, pageSize: 100,
});

Try these prompts

Starter prompts that exercise Floot MCP project and file tools with the signed-in user.

Projects and context

Copy the prompt

Copied

Using Floot MCP, list my projects and summarize the three most recently edited.

Copy the prompt

Copied

What is the current context on my active Floot project?

Copy the prompt

Copied

Show publish status for project Launchpad.

Files and edits

Copy the prompt

Copied

On my Floot project Launchpad, list files and read the main page component.

Copy the prompt

Copied

Search Launchpad code for where auth is handled.

Copy the prompt

Copied

Run typecheck on Launchpad and report any errors.

Preview and publish

Copy the prompt

Copied

Get the preview URL for Launchpad and take a screenshot.

Copy the prompt

Copied

Publish Launchpad after typecheck is clean.

Copy the prompt

Copied

Create a checkpoint titled Shipping launch CTA after the latest file edits.

SEE HOW AUTH WORKS

OAuth 2.1 with MCP discovery and dynamic client registration. Scalekit stores and refreshes tokens so your agent never handles Floot credentials.

Authorize

Your user connects

Floot MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Floot MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Floot MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Floot MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

Pair Floot MCP with adjacent builder and deploy connectors on the same per-user vault.

No items found.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Avoma bearer token makes every transcript lookup look like a bot. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared key
audit → bot_acct

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Avoma today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

How does Floot MCP auth work?

OAuth 2.1 with dynamic client registration. The user authorizes once; Scalekit stores and refreshes tokens for later tool calls.

Can my agent publish a Floot app?

Yes. publish_app and unpublish_app are in the tool list. Treat unpublish as destructive and confirm with the user first.

Do I need a shared Floot service account?

No. Each end user connects their own Floot account. Your agent never sees the raw token.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit