Skip to main content
Glama
bmlt-mcp-server

bmlt-mcp-server

by jbonjour

bmlt-mcp-server

전 세계 Narcotics Anonymous(NA) 서비스 기관에서 사용하는 오픈 소스 모임 데이터베이스인 BMLT(Basic Meeting List Toolbox)를 위한 MCP(Model Context Protocol) 서버입니다.

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)

모든 도구는 모든 BMLT 루트 서버를 가리키는 root_server_url 매개변수와 다른 지역으로 검색 범위를 지정하는 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 설정(~/Library/Application Support/Claude/claude_desktop_config.json, macOS 기준)에 추가하세요:

{
  "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 커뮤니티를 위해, 커뮤니티에 의해 수행되었습니다.

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.
      -