Skip to main content
Glama
bmlt-mcp-server

bmlt-mcp-server

by jbonjour

bmlt-mcp-server

一个用于 Basic Meeting List Toolbox (BMLT) 的 MCP (Model Context Protocol) 服务器——这是全球戒毒互助会 (NA) 服务机构使用的开源会议数据库。

将 Claude(或任何支持 MCP 的 AI 客户端)连接到 BMLT 根服务器,并使用自然语言查询 NA 会议数据。


功能介绍

提供四个工具:

工具

描述

bmlt_search_meetings

按日期、形式、地点、名称或地理坐标搜索会议

bmlt_get_meeting_details

通过 ID 获取特定会议的详细信息

bmlt_get_formats

列出所有会议形式代码及其描述(O, C, VM, BT 等)

bmlt_get_service_bodies

列出根服务器上的所有服务机构(地区/区域)

bmlt_get_server_info

检查根服务器版本和地理中心

连接后的提示词示例

  • “今晚波特兰有哪些 NA 会议?”

  • “查找周二的开放式虚拟会议”

  • “显示波特兰市中心 5 英里内的所有会议”

  • “形式代码 'BT' 是什么意思?”

  • “列出 WSZF 服务器上的所有服务机构”


Related MCP server: GoHighLevel MCP Starter

默认设置

开箱即用,服务器指向:

  • 根服务器: https://bmlt.wszf.org/main_server (WSZF 网络)

  • 默认服务机构: 26 (波特兰地区 NA)

所有工具都接受 root_server_url 参数以指向任何 BMLT 根服务器,并接受 service_body_ids 以将搜索范围限定在其他区域。


安装

git clone https://github.com/jbonjour/bmlt-mcp-server.git
cd bmlt-mcp-server
npm install
npm run build

使用方法

使用 Claude Desktop (stdio — 推荐)

添加到您的 Claude Desktop 配置文件(macOS 上为 ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "bmlt": {
      "command": "node",
      "args": ["/absolute/path/to/bmlt-mcp-server/dist/index.js"]
    }
  }
}

重启 Claude Desktop。您将在聊天中看到可用的 BMLT 工具。

使用 Claude Code

claude mcp add bmlt node /absolute/path/to/bmlt-mcp-server/dist/index.js

HTTP 模式(用于远程/多客户端使用)

TRANSPORT=http PORT=3000 node dist/index.js
# Server listens on http://localhost:3000/mcp

开发

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 start

使用 MCP Inspector 进行测试:

npx @modelcontextprotocol/inspector node dist/index.js

环境变量

变量

默认值

描述

TRANSPORT

stdio

传输模式:stdio 或 http

PORT

3000

HTTP 端口(仅在 TRANSPORT=http 时使用)


更改默认根服务器或服务机构

编辑 src/constants.ts:

export const DEFAULT_ROOT_SERVER = "https://bmlt.wszf.org/main_server";
export const DEFAULT_SERVICE_BODY_ID = 26; // Portland NA

然后重新构建:npm run build


BMLT 根服务器

任何运行 BMLT 的 NA 服务机构都可以被查询。常见的根服务器:

网络

URL

WSZF (太平洋西北地区)

https://bmlt.wszf.org/main_server

NA World Services (聚合器)

https://na.org/main_server

在 bmlt.app 查找您所在地区的根服务器。


贡献

欢迎提交 PR。本项目旨在支持波特兰地区 NA 的网站现代化项目,并为更广泛的 NA 技术社区开源。


许可证

MIT — 可自由使用、共享和修改。所有工作均由 NA 社区完成并服务于 NA 社区。

Available Tools

5 tools
bmlt_get_formatsGet Meeting FormatsA
Read-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 DetailsA
Read-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 InfoA
Read-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:

Returns: Server version, center lat/lng, default zoom level, and region bias.

Inputs: root_server_url.

bmlt_get_service_bodiesGet Service BodiesA
Read-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 MeetingsA
Read-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

    A4.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All tool names follow the predictable pattern 'bmlt_verb_noun' (e.g., bmlt_get_formats, bmlt_search_meetings). The convention is consistent and readable.

    Tool Count5/5

    Five tools is an appropriate number for a read-only meeting information server. Each tool serves a necessary function without being excessive or insufficient.

    Completeness5/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Mindbody, enabling AI agents to fetch client info, query class schedules, book classes/appointments (env-gated), and process checkout (payment-gated).
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP 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
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      -