Skip to main content
Glama
flowteller-io

Flowteller API MCP Server

Official
by flowteller-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FLOWTELLER_API_URLNoThe Flowteller API URLhttps://dev.api.flowteller.com/api
FLOWTELLER_MCP_API_KEYYesYour API key for Flowteller

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_health_statusA

Check the health status of the Flowteller API.

get_originsB
Get a list of available origin locations for bookings.

Args:
    provider: The booking provider name (e.g., 'bus', 'mysafari', 'otapp'). Default is 'bus'.
get_destinationsA
Get a list of available destination locations for a given origin.

Args:
    origin_id: The ID of the origin location.
    provider: The booking provider name. Default is 'bus'.
search_tripsA
Search for available trips between an origin and destination on a specific date.

Args:
    origin_name: The name of the origin location (e.g., 'Mwanza').
    destination_name: The name of the destination location (e.g., 'Dodoma').
    travel_date: The travel date in YYYY-MM-DD format.
    provider: The booking provider name. Default is 'bus'.
    adults: Number of adult passengers.
    children: Number of child passengers.
get_booking_historyB
Get the agent's booking history.

Args:
    page: Page number (starts at 1).
    per_page: Items per page (max 100).
    status: Filter by booking status.
    provider: Filter by provider.
create_bookingA
Create a new booking.

Args:
    trip_id: The ID of the trip to book.
    passengers: A list of dictionaries representing passengers. Each passenger needs:
        name, phone_number, age_group_id, seat_number, pick_point_id, drop_point_id, 
        gender (M or F), identification_type_id, id_number.
    provider: The provider of the trip (e.g. mysafari).
    origin_id: Optional origin ID.
    destination_id: Optional destination ID.
    travel_date: Optional travel date (YYYY-MM-DD).
generate_receiptB
Generate a formatted text receipt for a given booking reference.

Args:
    booking_ref: The booking reference ID.
    provider: The provider of the booking.
initiate_paymentA
Initiate a customer push payment request for a booking.

Args:
    booking_id: The ID of the booking to pay for.
    provider: The provider of the booking (e.g. mysafari).
    customer_phone: The phone number of the customer for mobile money push.
    payment_provider: Optional mobile money provider name (e.g. VODACOM, TIGO).
get_payment_providersA

Get the list of available mobile money payment providers for customer push payments.

Prompts

Interactive templates invoked by user choice

NameDescription
flowteller_chat_agentSystem prompt for the AI to act as a WhatsApp Travel Agent.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.8/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct resource and action: health, booking history, receipt generation, location lookups, trip search, booking creation, payment providers, and payment initiation. No two tools overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_origins, create_booking, initiate_payment). The naming is predictable and uniform.

Tool Count5/5

With 9 tools, the server is well-scoped for a travel booking API. The count is within the ideal range and each tool serves a clear need without redundancy.

Completeness4/5

The core booking lifecycle (search trips, create booking, initiate payment, view history, generate receipt) is covered. Missing cancellation or individual booking retrieval are minor gaps that agents can work around.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources