bmlt-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port (only used when TRANSPORT=http) | 3000 |
| TRANSPORT | No | Transport mode: stdio or http | stdio |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bmlt_search_meetingsA | Search for Narcotics Anonymous meetings in the BMLT database. Returns a list of meetings matching the given filters. All filters are optional — omitting them returns all meetings for the default service body. Args:
Returns: Formatted list of meetings with name, day, time, location, formats, and links. Examples:
|
| bmlt_get_formatsA | Retrieve all meeting format codes and their descriptions from a BMLT root server. Formats describe the type of meeting — e.g. "O" = Open, "C" = Closed, "VM" = Virtual Meeting, "BT" = Book Study, "D" = Discussion, "SP" = Speaker, "WC" = Wheelchair Accessible. Use this to:
Args:
Returns: List of format codes, names, and descriptions. |
| bmlt_get_service_bodiesA | Retrieve all service bodies (NA regions, areas, districts) from a BMLT root server. Service bodies are the organizational units that manage meeting data in BMLT. Knowing the ID of a service body lets you filter meeting searches to a specific area. Use this to:
Args:
Returns: List of service bodies with IDs, names, types, URLs, and helplines. Example: Portland NA has service body ID 26 on the WSZF root server. |
| bmlt_get_server_infoA | Retrieve metadata about a BMLT root server, including version and geographic center. Use this to verify a server is reachable, check its version, or get its default center coordinates. Args:
Returns: Server version, center lat/lng, default zoom level, and region bias. |
| bmlt_get_meeting_detailsA | Retrieve full details for a specific NA meeting by its BMLT meeting ID. Use this after bmlt_search_meetings to get the complete record for a specific meeting. Args:
Returns: Full meeting record including name, day, time, location, formats, virtual links, and all metadata fields. |
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 5 tools
Each tool has a clearly distinct purpose: formats, meeting details, server info, service bodies, and search. There is no overlap, and an agent can easily select the right tool for a given task.
All tool names follow the predictable pattern 'bmlt_verb_noun' (e.g., bmlt_get_formats, bmlt_search_meetings). The convention is consistent and readable.
Five tools is an appropriate number for a read-only meeting information server. Each tool serves a necessary function without being excessive or insufficient.
The tool set covers all primary operations for querying BMLT meeting data: retrieving metadata (server info, service bodies, formats), searching meetings, and getting detailed records. No obvious gaps exist for the intended read-only use case.