FlowCastle

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as ai.flowcastle/flowcastle and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 28 Jul 2026. Not supplied by the maker.

• list_applications

  List the applications this API key can access, with the caller role and the permissions it grants. Start here when using a personal API key (usr_...): every other tool needs an explicit applicationId,

• create_application

  Create a new application (workspace) owned by the caller. Requires a personal API key (usr_...) — application-scoped keys cannot create applications. Seeds default flows unless skipDefaultFlows is tru

• update_application

  Update application-level settings (name, active state, default language, incoming-message behavior). Requires the manage_settings permission in that application.

• get_workspace_summary

  Return compact application, flow, and bot summary without variables or full graph details.

• get_variable_context

  Search variables by scope/query. Values are omitted unless includeValues is true.

• get_application_context

  Return application-level automation context: flows, bots, and variables.

• get_module_catalog

  Return a compact installed and marketplace module index with names, descriptions, actions, and triggers.

• get_module_details

  Return full details for one selected module, including action input fields, trigger config, manual setup fields, and installed action references.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.