Meetup MCP

Purpose

• MCP server for meetup planning using Kakao Local + Kakao Mobility directions.
• Supports driving-time-balanced meetup area suggestions and nearby place recommendations.

Key Behaviors

• Uses Kakao REST API key for both Local and Mobility APIs.
• Loads .env explicitly from the project directory via python-dotenv.
• Default transport is stdio; can switch to HTTP with MCP_TRANSPORT=streamable-http.

Tools

• geocode: free-text -> place candidates (lat/lng) via Kakao Local keyword search.
• search_places: search places around an area center (keyword search), supports hotplace flag.
• plan_meetup_driving: main planner; resolves origins, ranks areas by driving time, then recommends places.

Natural Language Handling (in plan_meetup_driving)

• Single-origin text like "인천에서 강남 사이" is split into two origins.
• Vague origins like "내 집/근처/현재 위치" cause NEED_LOCATION response asking for a real place.
• preferences_text auto-parses cuisine preferences (e.g., 고기/일식/카페/술집) and hotplace intent.
• hotplace adds "핫플" to the search keyword.

Preferred Areas

• prefer_areas list: add candidate stations near preferred areas.
• Bonus scoring applied based on distance to preferred areas:
  • <= 3 km: +12
  • <= 8 km: +6
• Response includes prefer_distance_km and prefer_bonus per area.

Cloud Run Compatibility

• FastMCP binds to 0.0.0.0 and PORT (default 8080).
• Dockerfile sets MCP_TRANSPORT=streamable-http and exposes 8080.
• MCP HTTP endpoint for Cloud Run is /mcp.

Files Changed

• meetup-mcp/server.py
• meetup-mcp/dockerfile
• meetup-mcp/requirements.txt
• meetup-mcp/.env.example
• meetup-mcp/.env

Claude Desktop (Windows) MCP Config

• %APPDATA%\Claude\claude_desktop_config.json
• Example: { "mcpServers": { "meetup-mcp": { "command": "C:\Python313\python.exe", "args": [ "C:\Users\CNXK\Desktop\projectfiles\개인\meetup-mcp\server.py" ] } } }

Notes

• Cloud Run is HTTP-only; stdio works for Claude Desktop.
• PlayMCP likely expects HTTP access (not stdio).