FlowCastle
Server Details
Build, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- FlowCastle/telegram-bot-templates
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
16 toolsapply_actionsInspect
Validate and apply a batch of flow-builder actions. Validation always runs first; when it fails, nothing is applied and the same errors validate_actions would return are reported. Call this directly — a separate validate_actions call beforehand is unnecessary.
| Name | Required | Description | Default |
|---|---|---|---|
| flowId | No | ||
| actions | Yes | ||
| applicationId | No | ||
| conversationId | No |
get_action_schemaInspect
Return supported action kinds and important invariants for draft/apply flow edits.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_application_contextInspect
Return application-level automation context: flows, bots, and variables.
| Name | Required | Description | Default |
|---|---|---|---|
| applicationId | No |
get_block_detailsInspect
Return full details for one selected block, including block data, action configs, HTTP bodies, custom code files, triggers, menu payloads, and media paths.
| Name | Required | Description | Default |
|---|---|---|---|
| flowId | Yes | ||
| blockId | Yes | ||
| applicationId | No |
get_broadcast_analyticsInspect
Return analytics/stats for a broadcast: delivery breakdown by status plus per-message-block sent/clicked stats for its flow over an optional date window.
| Name | Required | Description | Default |
|---|---|---|---|
| endDate | No | ||
| startDate | No | ||
| broadcastId | Yes | ||
| applicationId | No |
get_broadcast_detailsInspect
Return full details for a single broadcast: status, schedule, recurrence, linked flow, and delivery breakdown by status.
| Name | Required | Description | Default |
|---|---|---|---|
| broadcastId | Yes | ||
| applicationId | No |
get_design_guidelinesInspect
Return shared flow-design guidance and examples used by both AI prompt assembly and MCP consumers.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_flow_contextInspect
Return compact flow graph topology and block summaries without full block data or action configs.
| Name | Required | Description | Default |
|---|---|---|---|
| flowId | Yes | ||
| applicationId | No |
get_flow_exampleInspect
Return one reusable flow example by id, optionally including its full action-batch schema example.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| includeSchemaExample | No |
get_module_catalogInspect
Return a compact installed and marketplace module index with names, descriptions, actions, and triggers.
| Name | Required | Description | Default |
|---|---|---|---|
| applicationId | No |
get_module_detailsInspect
Return full details for one selected module, including action input fields, trigger config, manual setup fields, and installed action references.
| Name | Required | Description | Default |
|---|---|---|---|
| moduleKey | Yes | ||
| applicationId | No | ||
| moduleVersion | No |
get_variable_contextInspect
Search variables by scope/query. Values are omitted unless includeValues is true.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | ||
| scope | No | ||
| applicationId | No | ||
| includeValues | No |
get_workspace_summaryInspect
Return compact application, flow, and bot summary without variables or full graph details.
| Name | Required | Description | Default |
|---|---|---|---|
| flowId | No | ||
| applicationId | No |
list_broadcastsInspect
List broadcasts in the application, with status, schedule, and delivery counts. Supports filtering by status/bot/recurrence and pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| botId | No | ||
| limit | No | ||
| status | No | ||
| isRecurring | No | ||
| applicationId | No |
search_flow_examplesInspect
Search compact reusable flow examples by keyword or tag for common business cases.
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | ||
| limit | No | ||
| query | No |
validate_actionsInspect
Dry-run validation of a proposed batch of flow-builder actions without mutating state. OPTIONAL: apply_actions runs this same validation itself and applies nothing when invalid, so calling validate_actions first is redundant — use it only to check a draft you do not intend to apply yet.
| Name | Required | Description | Default |
|---|---|---|---|
| flowId | No | ||
| actions | Yes | ||
| applicationId | No | ||
| conversationId | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!