bmlt-mcp-server
bmlt-mcp-server
Un servidor MCP (Model Context Protocol) para el Basic Meeting List Toolbox (BMLT), la base de datos de reuniones de código abierto utilizada por los órganos de servicio de Narcóticos Anónimos en todo el mundo.
Conecta Claude (o cualquier cliente de IA compatible con MCP) a un servidor raíz de BMLT y consulta datos de reuniones de NA usando lenguaje natural.
Qué hace
Expone cuatro herramientas:
Herramienta | Descripción |
| Buscar reuniones por día, formato, ubicación, nombre o coordenadas geográficas |
| Obtener detalles completos de una reunión específica por ID |
| Listar todos los códigos de formato de reunión y sus descripciones (O, C, VM, BT, etc.) |
| Listar todos los órganos de servicio (áreas/regiones) en el servidor raíz |
| Comprobar la versión del servidor raíz y el centro geográfico |
Ejemplos de prompts una vez conectado
"¿Qué reuniones de NA hay en Portland esta noche?"
"Busca reuniones virtuales abiertas el martes"
"Muéstrame todas las reuniones a menos de 5 millas del centro de Portland"
"¿Qué significa el código de formato 'BT'?"
"Lista todos los órganos de servicio en el servidor WSZF"
Related MCP server: GoHighLevel MCP Starter
Valores predeterminados
De forma predeterminada, el servidor apunta a:
Servidor raíz:
https://bmlt.wszf.org/main_server(red WSZF)Órgano de servicio predeterminado:
26(Área de Portland NA)
Todas las herramientas aceptan un parámetro root_server_url para apuntar a cualquier servidor raíz de BMLT, y service_body_ids para limitar las búsquedas a otras áreas.
Instalación
git clone https://github.com/jbonjour/bmlt-mcp-server.git
cd bmlt-mcp-server
npm install
npm run buildUso
Con Claude Desktop (stdio — recomendado)
Añádelo a tu configuración de Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json en macOS):
{
"mcpServers": {
"bmlt": {
"command": "node",
"args": ["/absolute/path/to/bmlt-mcp-server/dist/index.js"]
}
}
}Reinicia Claude Desktop. Verás las herramientas de BMLT disponibles en tu chat.
Con Claude Code
claude mcp add bmlt node /absolute/path/to/bmlt-mcp-server/dist/index.jsModo HTTP (para uso remoto/multicliente)
TRANSPORT=http PORT=3000 node dist/index.js
# Server listens on http://localhost:3000/mcpDesarrollo
npm install
npm run build # compile TypeScript → dist/
npm start # run compiled server (stdio)
# Or run via HTTP for testing:
TRANSPORT=http PORT=3000 npm startPara probar con el Inspector MCP:
npx @modelcontextprotocol/inspector node dist/index.jsVariables de entorno
Variable | Predeterminado | Descripción |
|
| Modo de transporte: |
|
| Puerto HTTP (solo se usa cuando |
Cambiar el servidor raíz o el órgano de servicio predeterminado
Edita src/constants.ts:
export const DEFAULT_ROOT_SERVER = "https://bmlt.wszf.org/main_server";
export const DEFAULT_SERVICE_BODY_ID = 26; // Portland NALuego reconstruye: npm run build
Servidores raíz de BMLT
Se puede consultar cualquier órgano de servicio de NA que ejecute BMLT. Servidores raíz comunes:
Red | URL |
WSZF (Noroeste del Pacífico) |
|
NA World Services (agregador) |
|
Encuentra el servidor raíz de tu región en bmlt.app.
Contribuciones
Las PR son bienvenidas. Esto se creó para apoyar el proyecto de modernización del sitio web de NA del Área de Portland y se publicó como código abierto para la comunidad tecnológica de NA en general.
Licencia
MIT — libre de usar, compartir y modificar. Todo el trabajo realizado por y para la comunidad de NA.
Available Tools
5 toolsbmlt_get_formatsGet Meeting FormatsARead-onlyIdempotent
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:
Discover what format codes are available before filtering a meeting search
Explain what a format code means to a user
List all available meeting types on the server
Args:
root_server_url (string, optional): BMLT root server URL. Defaults to "https://bmlt.wszf.org/main_server"
response_format (string, optional): "markdown" (default) or "json"
Returns: List of format codes, names, and descriptions.
Inputs: root_server_url, response_format.
bmlt_get_meeting_detailsGet Meeting DetailsARead-onlyIdempotent
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:
meeting_id (number): The BMLT meeting ID (the "id_bigint" field from search results)
root_server_url (string, optional): BMLT root server URL. Defaults to "https://bmlt.wszf.org/main_server"
service_body_ids (number[], optional): Service body IDs to scope the search. Defaults to [26]
response_format (string, optional): "markdown" (default) or "json"
Returns: Full meeting record including name, day, time, location, formats, virtual links, and all metadata fields.
Inputs: meeting_id (required), root_server_url, service_body_ids, response_format.
bmlt_get_server_infoGet Server InfoARead-onlyIdempotent
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:
root_server_url (string, optional): BMLT root server URL. Defaults to "https://bmlt.wszf.org/main_server"
Returns: Server version, center lat/lng, default zoom level, and region bias.
Inputs: root_server_url.
bmlt_get_service_bodiesGet Service BodiesARead-onlyIdempotent
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:
Discover service body IDs for use in bmlt_search_meetings
See the hierarchy of areas served by a root server
Find a specific area's helpline or website
Args:
root_server_url (string, optional): BMLT root server URL. Defaults to "https://bmlt.wszf.org/main_server"
response_format (string, optional): "markdown" (default) or "json"
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.
Inputs: root_server_url, response_format.
bmlt_search_meetingsSearch NA MeetingsARead-onlyIdempotent
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:
root_server_url (string, optional): BMLT root server URL. Defaults to "https://bmlt.wszf.org/main_server"
service_body_ids (number[], optional): Filter by service body IDs. Defaults to [26] (Portland NA)
weekdays (string[], optional): Filter by day(s) of week. Accepts day names like "Monday", "tuesday", or numbers 1–7 (1=Sunday)
formats (string[], optional): Filter by format codes, e.g. ["O"] for Open, ["VM"] for Virtual, ["C"] for Closed
meeting_name (string, optional): Search meetings by name (partial match)
lat (number, optional): Latitude for geo search. Requires lng.
lng (number, optional): Longitude for geo search. Requires lat.
radius_miles (number, optional): Search radius in miles when using lat/lng. Default: 10
start_time_min (string, optional): Only meetings starting at or after this time, format "HH:MM" (24h)
start_time_max (string, optional): Only meetings starting at or before this time, format "HH:MM" (24h)
response_format (string, optional): "markdown" (default) or "json"
Returns: Formatted list of meetings with name, day, time, location, formats, and links.
Examples:
"Show all Portland NA meetings on Friday" → weekdays: ["Friday"]
"Find open meetings near downtown Portland" → formats: ["O"], lat: 45.5231, lng: -122.6765
"Virtual meetings this week" → formats: ["VM"]
"Morning meetings" → start_time_max: "12:00"
Inputs: root_server_url, service_body_ids, weekdays, formats, +7 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
One connector for 15,000+ MCP servers plus your team's private MCPs, from any AI client.
Hosted MCP server for live public-data APIs and Skills for AI agents.
Hosted MCP server exposing US hospital procedure cost data to AI assistants
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for Mindbody, enabling AI agents to fetch client info, query class schedules, book classes/appointments (env-gated), and process checkout (payment-gated).5MIT
- AlicenseAqualityDmaintenanceMCP server that lets you talk to your GoHighLevel sub-account in plain English, offering six tools to search contacts, list calendars, check free slots, and book appointments with dry-run safety and explicit error messages.6MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that lets AI assistants query your Halaxy practice-management data—appointments, invoices, referrals, and practitioners—via natural language, exposing read-only tools for daily schedules, billing status, and session limits.GPL 3.0
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes OneMap8 fleet tracking to AI clients, enabling natural-language queries about devices, positions, reports, geofences, drivers, and more. Includes 32 tools, permission scoping, and safety guardrails.-