bmlt-mcp-server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@bmlt-mcp-server Find open NA meetings in Portland tonight"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
bmlt-mcp-server
An MCP (Model Context Protocol) server for the Basic Meeting List Toolbox (BMLT) — the open-source meeting database used by Narcotics Anonymous service bodies worldwide.
Connect Claude (or any MCP-compatible AI client) to a BMLT root server and query NA meeting data using natural language.
What it does
Exposes four tools:
Tool | Description |
| Search meetings by day, format, location, name, or geo coordinates |
| Get full details for a specific meeting by ID |
| List all meeting format codes and descriptions (O, C, VM, BT, etc.) |
| List all service bodies (areas/regions) on the root server |
| Check root server version and geographic center |
Example prompts once connected
"What NA meetings are happening in Portland tonight?"
"Find open virtual meetings on Tuesday"
"Show me all meetings within 5 miles of downtown Portland"
"What does the format code 'BT' mean?"
"List all service bodies on the WSZF server"
Related MCP server: GoHighLevel MCP Starter
Defaults
Out of the box, the server points to:
Root server:
https://bmlt.wszf.org/main_server(WSZF network)Default service body:
26(Portland Area NA)
All tools accept a root_server_url parameter to point at any BMLT root server, and service_body_ids to scope searches to other areas.
Installation
git clone https://github.com/jbonjour/bmlt-mcp-server.git
cd bmlt-mcp-server
npm install
npm run buildUsage
With Claude Desktop (stdio — recommended)
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"bmlt": {
"command": "node",
"args": ["/absolute/path/to/bmlt-mcp-server/dist/index.js"]
}
}
}Restart Claude Desktop. You'll see the BMLT tools available in your chat.
With Claude Code
claude mcp add bmlt node /absolute/path/to/bmlt-mcp-server/dist/index.jsHTTP mode (for remote/multi-client use)
TRANSPORT=http PORT=3000 node dist/index.js
# Server listens on http://localhost:3000/mcpDevelopment
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 startTo test with the MCP Inspector:
npx @modelcontextprotocol/inspector node dist/index.jsEnvironment variables
Variable | Default | Description |
|
| Transport mode: |
|
| HTTP port (only used when |
Changing the default root server or service body
Edit src/constants.ts:
export const DEFAULT_ROOT_SERVER = "https://bmlt.wszf.org/main_server";
export const DEFAULT_SERVICE_BODY_ID = 26; // Portland NAThen rebuild: npm run build
BMLT root servers
Any NA service body running BMLT can be queried. Common root servers:
Network | URL |
WSZF (Pacific Northwest) |
|
NA World Services (aggregator) |
|
Find your region's root server at bmlt.app.
Contributing
PRs welcome. This was built to support Portland Area NA's website modernization project and open-sourced for the broader NA tech community.
License
MIT — free to use, share, and modify. All work done by and for the NA community.
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.-