Skip to main content
Glama

Server Details

Build, deploy and share small full-stack team apps from your AI chat. No account needed to start.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 19 tools

Disambiguation4/5

Most tools are clearly distinct (deploy vs check vs delete vs rollback vs share vs set_env), and the failure modes are described in enough detail that misselection is unlikely. The one soft spot is the get_app / get_app_source / inspect_app cluster: get_app already returns usage, limits and handlers, while inspect_app reads usage, schedules and manifest, and get_app_source overlaps with update_app_files' expected_deploy_id flow, so an agent may hesitate over which to reach for first.

Naming Consistency4/5

The dominant pattern is a clean verb_noun snake_case set (deploy_app, check_app, get_app_source, update_app_files, list_apps, set_env, share_app). The exceptions are the noun-prefixed fuast_guide/fuast_docs and the bare whoami, which don't follow that pattern but are memorable and few.

Tool Count4/5

Nineteen tools is on the heavy side, but each covers a genuinely different stage of the build-check-deploy-operate-share lifecycle and none look redundant. It edges just past the comfortable 3-15 band, mainly because the platform surface (docs, templates, previews, claim links, account) is broad.

Completeness4/5

The lifecycle is well covered: onboarding guide, docs, templates, build check, deploy, partial update, rollback, logs, env, sharing, inspection and deletion. Gaps remain around data and files — there is no tool to write/seed table rows or to manage stored files and schedules directly, so agents must fall back to writing handler code or call_app mutations.

Available Tools

19 tools
call_appRun a handler of an appA
Destructive
Inspect

Runs one query, mutation or action of a deployed app and returns its result and the log lines it wrote, so you can test what you deployed. It runs as the connected person (as: "me", the default), never as anyone else; as: "guest" runs it as a guest visitor and only works on public apps. On a preview deployed without an account every call runs as one guest. Mutations and actions change real data. Only for apps the person owns or administers.

Inputs: kind (required), name (required), as, app, +2 more. Returns: kind, logs, name, slug, +4 more

check_appCheck an app without deployingA
Read-onlyIdempotent
Inspect

Builds the files, type checks them and loads the server in a sandbox, without deploying anything. Returns ok with the queries, mutations, tables and tools the app declares, or ok false with diagnostics that carry file, line and message. Call it before deploy_app and fix every diagnostic.

Inputs: files (required). Returns: ms, ok, code, name, +5 more

delete_appDelete an app for goodA
Destructive
Inspect

Deletes an app and everything in it: its data, stored files, deploys, schedules and custom domains. This cannot be undone. Only the app's owner can do it, and confirm must repeat the app's slug. Do this only when the person explicitly asks for the app to be deleted.

Inputs: app (required), confirm (required). Returns: name, slug, deleted, warnings

deploy_appDeploy an appA
Destructive
Inspect

Deploys the files and returns the app's URL. With a connected fuast account it creates a new private app in the person's workspace, or updates the app named in app. Without an account it deploys a temporary preview and returns preview_url, claim_url and edit_token: give the person claim_url so they can make the app theirs, and pass edit_token to later calls to keep working on it. Send every file each time; use update_app_files to change a few. A failed build returns diagnostics with file and line and deploys nothing.

Inputs: files (required), app, name, edit_token, +1 more. Returns: url, name, slug, limits, +14 more

fuast_docsRead or search the fuast docsA
Read-only
Inspect

Read one docs page as markdown (page), or search every page for words (search). With neither, lists the pages. Useful pages: capsule-api (every server and client API), database, auth, limits, storage, schedules, email, teams, examples/todo.

Inputs: page, search. Returns: url, page, pages, title, +2 more

fuast_guideRead the fuast guideA
Read-only
Inspect

Call this first. Returns how to build, check, deploy and share a fuast app with these tools, and the rules a fuast app must follow (file layout, server and client APIs, database, auth, UI). fuast apps are small full-stack TypeScript apps called capsules: server/index.ts and client/index.tsx, no npm packages.

Inputs: no named parameters. Returns: guide, pages

get_appGet an app's statusB
Read-only
Inspect

Returns one app: URL, status, sharing, handlers, recent deploys with their ids (for rollback_app), today's usage and limits, and the names (never the values) of its env vars.

Inputs: app, edit_token. Returns: url, name, slug, owner, +19 more

get_app_sourceGet an app's source filesA
Read-only
Inspect

Returns the source of the app's live deploy as {path: content}, with the deploy id to pass to update_app_files as expected_deploy_id. Large apps return the file list only: ask again with paths for the files you need. Secrets (.env files, env values) are never returned.

Inputs: app, paths, edit_token. Returns: name, slug, files, deploy_id, +2 more

get_logsRead an app's logsA
Read-only
Inspect

Returns recent log entries of an app, oldest first: what its handlers wrote with ctx.log, handler errors with stack traces, and platform events such as deploys. Pass the returned cursor as since to read only newer entries.

Inputs: app, level, limit, since, +1 more. Returns: slug, cursor, entries

get_templateGet a template's filesA
Read-only
Inspect

Returns the source files of one starter template as {path: content}: a complete app that passes check_app and can be sent to deploy_app as is. Change the files to build what the person asked for.

Inputs: id (required), name. Returns: id, name, files

inspect_appInspect an appA
Read-only
Inspect

Reads one thing about a deployed app. manifest: handlers, schema, indexes, endpoints, read metrics. tables: each table with its fields and row count. rows: rows of one table (give table; at most 100 per call, continue with cursor). usage: today's counters and limits. schedules: cron schedules and their last runs. jobs: scheduled jobs. Only the app's owner and workspace admins can inspect.

Inputs: what (required), app, limit, table, +2 more. Returns: jobs, rows, slug, what, +6 more

list_appsList my appsA
Read-only
Inspect

Lists the fuast apps the connected account can use: its own, its workspace's, and apps shared with it, with URL, sharing mode and whether the account can manage each one.

Inputs: no named parameters. Returns: apps

list_templatesList starter templatesA
Read-only
Inspect

Lists the working starter apps a new fuast app can begin from, with what each one demonstrates. Get a template's files with get_template.

Inputs: no named parameters. Returns: templates

rollback_appRoll an app back to an earlier deployA
DestructiveIdempotent
Inspect

Makes an earlier deploy of the app live again. deploy_id comes from get_app; without it, the most recent earlier deploy that is ready. The app's data stays as it is; if that deploy's schema cannot hold the current data, nothing changes.

Inputs: app (required), deploy_id. Returns: url, slug, active_deploy_id, previous_deploy_id

set_envSet an app's server secretsA
DestructiveIdempotent
Inspect

Sets or removes environment variables of an app (read in handlers as ctx.env.NAME). They take effect at once, without a deploy. Values are write-only: no tool returns them, only the names.

Inputs: app (required), set, unset. Returns: set, keys, slug, unset

share_appShare an appA
DestructiveIdempotent
Inspect

Changes who can open an app. visibility: private (the owner and invited people), workspace (everyone at the owner's company), or public (anyone with the link, guests included). invite adds people by email and sends each an email; remove takes people off the list. Do this only when the person asks for it. Returns the resulting sharing.

Inputs: app (required), invite, remove, visibility. Returns: url, slug, invited, removed, +2 more

update_app_filesChange some of an app's filesA
Destructive
Inspect

Redeploys the app with a few files changed: files maps each path to its new content, or to null to delete it. Every other file stays as it is. expected_deploy_id must be the app's live deploy (from get_app_source or the last deploy result); if someone deployed in between, nothing changes and you are told to read the source again. Builds and type checks like deploy_app.

Inputs: files (required), expected_deploy_id (required), app, edit_token, +1 more. Returns: url, name, slug, limits, +14 more

whoamiShow the connected fuast accountA
Read-only
Inspect

Returns the fuast account this connection acts as: email, workspace, role, and what the connection may do. If no account is connected yet, calling it starts sign-in: call it when the person has a fuast account or wants apps deployed into their own workspace instead of as a temporary preview.

Inputs: no named parameters. Returns: app, name, email, client, +4 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources