List your agent

fuast

MCP server● Hosted · onlinev2.3.0

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

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: automate CI/CD pipelines.
All AI agents to automate CI/CD pipelines, ranked →

Similar tools

Listed for the same task: automate CI/CD pipelines

Reviews

No review yet. Used fuast? Be the first to help others choose.

What it does

fuast is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: devops automation. That makes it a candidate for tasks such as automate CI/CD pipelines or monitor production incidents.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version2.3.0
PriceNot in the registry
First seen12 Nov 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://fuast.com/mcp streamable-http

In Claude Code: claude mcp add --transport http fuast https://fuast.com/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "fuast": {
      "url": "https://fuast.com/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE fuast answered an MCP connection on 15 Nov 2026 and introduced itself as fuast 2.3.0 (MCP protocol 2025-06-18).

20 tools offered to AI assistants

  • fuast_guide · 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 ca
  • fuast_docs · 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.
  • list_templates · 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.
  • get_template · 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.
  • check_app · 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. Cal
  • deploy_app · 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,
  • get_app_source · 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, en
  • update_app_files · 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);
  • list_apps · 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.
  • get_app · 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.
  • get_logs · 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.
  • screenshot_app · Opens one page of a deployed app in a browser and returns a picture of it, with any errors the page reported while it loaded. Use it after a deploy to see what a person will see, which rows and logs cannot show: a blank page, a broken layou
Show 8 more
  • inspect_app · 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: t
  • call_app · 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
  • share_app · 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 tak
  • set_env · 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.
  • rollback_app · 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.
  • delete_app · 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
  • get_claim_link · For a preview that deploy_app deployed without an account: returns the claim link to give to the person, the preview link, and when the preview is deleted if nobody claims it. Opening the claim link and signing in makes the app theirs.
  • whoami · 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 th

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Version2.3.0DECLAREDSRC-001 Official MCP Registry1d ago
Hosted endpointhttps://fuast.com/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Websitehttps://fuast.com/agentsDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

  • VERSION15 Nov 2026
    2.2.0 → 2.3.0
  • VERSION12 Nov 2026
    2.1.0 → 2.2.0
  • NEW12 Nov 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run fuast? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor fuastLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of fuast?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/fuast?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/fuast/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about fuast

How do I connect fuast?

Use the hosted endpoint https://fuast.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does fuast offer?

When Electra Index connected on 15 Nov 2026, it listed 20 tools: fuast_guide, fuast_docs, list_templates, get_template, check_app, deploy_app, get_app_source, update_app_files and more. The full list is in "Live check" above.

Is fuast online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.

What can I use fuast for?

Based on its description, it is most relevant to: automate CI/CD pipelines, monitor production incidents.