Skip to main content
Glama
flowteller-io

Flowteller API MCP Server

Official
README.md
# Flowteller API MCP Server

This is an MCP (Model Context Protocol) server for the Flowteller API. It allows AI clients (like Claude Desktop) to natively interact with the Flowteller backend to search for trips, find locations, and manage bookings.

## Installation & Setup for Claude Desktop

Because this project is hosted publicly on GitHub, you do not need to clone it to your computer! You can run it directly using `uvx`.

1. **Install `uv` (if you haven't already):**
   ```bash
   curl -LsSf https://astral.sh/uv/install.sh | sh
   ```

2. **Configure Claude Desktop:**
   Open your Claude Desktop configuration file:
   - Mac: `~/Library/Application Support/Claude/claude_desktop_config.json`
   - Windows: `%APPDATA%\Claude\claude_desktop_config.json`

   Add the following configuration, inserting your actual API key:

   ```json
   {
     "mcpServers": {
       "flowteller": {
         "command": "uv",
         "args": [
           "--directory",
           "/Users/whoisladleo/Work/flowteller/mcp",
           "run",
           "flowteller-mcp"
        ],
        "env": {
          "FLOWTELLER_API_URL": "http://localhost:8000/api",
          "FLOWTELLER_MCP_API_KEY": "your_secure_mcp_api_key_here"
        }
      }
    }
  }
```
   

3. **Restart Claude Desktop.** You should now see the Flowteller tools and prompts available!

## Testing Locally (Inspector)
If you are developing or modifying the code locally, you can use the interactive MCP Inspector UI:
```bash
npx @modelcontextprotocol/inspector uv run app/server.py
```

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