Bixi MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BIXI_PASSWORD | Yes | Your Bixi account password | |
| BIXI_USERNAME | Yes | Your Bixi account username |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_stationsA | List all Bixi stations currently in service. Returns: A list of stations, each with id, name, lat, and lng. |
| list_ridesA | List the current member's ride history. Args: offset: Number of most-recent rides to skip, for pagination. Defaults to 0, which returns the full ride history. Returns: A list of rides, most recent first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools target completely different domains: station availability/location versus the member's ride history. There is no possibility of confusing list_stations with list_rides. Each has a clearly distinct purpose.
Both tools follow a consistent verb_noun pattern (list_stations, list_rides), using snake_case throughout. The naming convention is uniform and predictable.
With only 2 tools, the server feels quite thin for what appears to be a bike-sharing service. While both tools are useful, the scope of a Bixi server would naturally extend to more operations, meaning the count sits at the borderline low end.
The surface is notably incomplete. It provides station listing and ride history, but lacks obvious operations such as finding available bikes/docks, checking station real-time availability, or any ride lifecycle actions. The read-only surface covers only a narrow slice of the domain.