maitabi 1.0.0__tar.gz

maitabi-1.0.0/.github/workflows/ci.yml

@@ -0,0 +1,36 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    name: Test & build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install dependencies (incl. dev group)
+        run: uv sync --group dev
+
+      - name: Run offline test suite
+        run: uv run pytest tests/ -v
+
+      - name: Build package
+        run: uv build
+
+      - name: Check generated catalog is up to date
+        run: uv run python scripts/gen_catalog.py --check

maitabi-1.0.0/.github/workflows/docker-publish.yml

@@ -0,0 +1,64 @@
+name: Publish Docker Image to Docker Hub
+
+on:
+  push:
+    tags:
+      - 'v*'
+  release:
+    types: [published]
+  workflow_dispatch:
+
+jobs:
+  build-and-push:
+    runs-on: ubuntu-latest
+
+    environment:
+      name: dockerhub
+      url: https://hub.docker.com/r/phonhay103/maitabi
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up QEMU (for multi-arch)
+        uses: docker/setup-qemu-action@v3
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      - name: Log in to Docker Hub
+        uses: docker/login-action@v3
+        with:
+          username: ${{ secrets.DOCKERHUB_USERNAME }}
+          password: ${{ secrets.DOCKERHUB_TOKEN }}
+
+      - name: Extract metadata for Docker
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: ${{ secrets.DOCKERHUB_USERNAME }}/maitabi
+          tags: |
+            type=raw,value=latest
+            type=semver,pattern={{version}}
+            type=semver,pattern={{major}}.{{minor}}
+
+      - name: Build and push Docker image
+        uses: docker/build-push-action@v5
+        with:
+          context: .
+          platforms: linux/amd64,linux/arm64
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          annotations: ${{ steps.meta.outputs.annotations }}
+          provenance: true
+          sbom: true
+
+
+      - name: Update Docker Hub Description
+        uses: peter-evans/dockerhub-description@v4
+        with:
+          username: ${{ secrets.DOCKERHUB_USERNAME }}
+          password: ${{ secrets.DOCKERHUB_TOKEN }}
+          repository: ${{ secrets.DOCKERHUB_USERNAME }}/maitabi
+          short-description: "Maitabi CLI + MCP server: bus tours, trekking tours, calendars (unofficial)."
+          readme-filepath: ./README.md

maitabi-1.0.0/.github/workflows/pypi-publish.yml

@@ -0,0 +1,38 @@
+name: Publish Python Package to PyPI
+
+on:
+  push:
+    tags:
+      - 'v*'
+  release:
+    types: [published]
+  workflow_dispatch:
+
+jobs:
+  pypi-publish:
+    name: Build and publish to PyPI
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/maitabi
+    permissions:
+      id-token: write  # Mandatory for Trusted Publisher authentication
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Build package
+        run: uv build
+
+      - name: Publish package to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

maitabi-1.0.0/.gitignore

@@ -0,0 +1,17 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# Environments & Packaging
+.venv/
+.uv/
+dist/
+build/
+*.egg-info/
+node_modules/
+
+# Logs & OS
+*.log
+.DS_Store
+.env

maitabi-1.0.0/.pre-commit-config.yaml

@@ -0,0 +1,31 @@
+# Secret scanning on every commit (https://github.com/gitleaks/gitleaks).
+# One-time setup per clone:  pre-commit install
+# The hook builds gitleaks with the Go toolchain on first run, so Go must be
+# on PATH; the built binary is cached afterwards.
+# Only staged changes are scanned, and matches are redacted in the output.
+repos:
+  - repo: https://github.com/gitleaks/gitleaks
+    rev: v8.30.1
+    hooks:
+      - id: gitleaks
+
+  # Project's own linters, run through uv so the ruff/ty versions pinned in
+  # uv.lock are the ones enforced (same as `make lint`).
+  - repo: local
+    hooks:
+      - id: ruff-check
+        name: ruff check
+        entry: uv run --frozen ruff check --force-exclude
+        language: system
+        types: [python]
+      - id: ruff-format
+        name: ruff format --check
+        entry: uv run --frozen ruff format --check --force-exclude
+        language: system
+        types: [python]
+      - id: ty
+        name: ty check
+        entry: uv run --frozen ty check
+        language: system
+        pass_filenames: false
+        types: [python]

maitabi-1.0.0/.vscode/mcp.json

@@ -0,0 +1,45 @@
+{
+	"servers": {
+		"maitabi": {
+			"command": "docker",
+			"args": [
+				"run",
+				"-i",
+				"--rm",
+				"phonhay103/maitabi:latest",
+				"mcp"
+			],
+			"type": "stdio"
+		},
+		"maitabi-pypi": {
+			"type": "stdio",
+			"command": "uvx",
+			"args": [
+				"maitabi",
+				"mcp"
+			]
+		},
+		"maitabi-uvx-local": {
+			"type": "stdio",
+			"command": "uvx",
+			"args": [
+				"--from",
+				".",
+				"maitabi",
+				"mcp"
+			]
+		},
+		"maitabi-docker-local": {
+			"type": "stdio",
+			"command": "docker",
+			"args": [
+				"run",
+				"-i",
+				"--rm",
+				"maitabi:latest",
+				"mcp"
+			]
+		}
+	},
+	"inputs": []
+}

maitabi-1.0.0/AGENTS.md

@@ -0,0 +1,79 @@
+# Maitabi Core ↔ MCP ↔ CLI ↔ Skills Sync Guide
+
+**Purpose**: Core logic lives once in `core/` + `services/`. MCP (`mcp/`) and CLI (`cli/`) are thin adapters generated from **one action registry** — `registry.py`. The tool catalog (`docs/TOOL_CATALOG.md`) and the per-skill `filter-mapping.md` copies are **generated from that code**, so the old manual Must-Match tables and sync checklists are gone: CI fails if they drift. Three skills stay independent; the `maitabi-mcp` skill is the procedure layer (which tool, in what order, how to read results) and always assumes the server is already connected — it contains zero setup.
+
+**One package, three faces.** The installed artifact is `maitabi` (PyPI + image `phonhay103/maitabi`): CLI (`maitabi <bus|general> <command>`), MCP server (`maitabi mcp`), and the three skills. The CLI is the default interface for agents and scripts; MCP is the protocol adapter for clients that speak it; the skills carry the workflows. `dependencies` in `pyproject.toml` stay full (mcp, fastmcp, httpx, pydantic) so a single install serves every interface.
+
+---
+
+## Architecture (All Layers Match — By Construction)
+
+```
+Core:     core/enums.py + core/inputs.py (param source of truth) + core/filters.py
+          + core/days.py + core/errors.py + config.py (env-overridable base URLs)
+Services: services/http.py (shared get_json + rate-limit detect + bounded fan-out)
+          + services/bus.py + services/general.py           (return plain dicts)
+Wiring:   registry.py — one Action per capability (tool name, CLI command, Input
+          model, service, endpoint, MCP doc, CLI help)
+MCP:      mcp/tools.py (tool signatures generated from model FieldInfo → flat schema)
+          + mcp/server.py (create_mcp() + run() + standalone main)
+CLI:      mcp_args.py (transport flags, no fastmcp import) → cli/fields.py (one
+          field plan feeds both sides) → cli/parser.py (two-level: <domain> <command>
+          + `mcp`) + cli/commands.py (one generic handler) + cli/main.py (exit codes)
+Catalog:  docs/TOOL_CATALOG.md + skills/{maitabi-cli,maitabi-mcp}/references/filter-mapping.md
+          — GENERATED by scripts/gen_catalog.py (--check in CI)
+Skills:   skills/maitabi-bus-extractor (raw curl/HTTP, standalone),
+          skills/maitabi-cli (terminal only), skills/maitabi-mcp (procedure only)
+```
+
+Rules:
+- Fix/query/parse logic once in `services/` (+ pure helpers in `core/`); adapters only map args → `Input` → service and serialize JSON **at the edge** (one `json.dumps` in the MCP tool, one in the CLI emitter — wire bytes identical).
+- `cli/*` must NEVER import `fastmcp`/`mcp`/`server`/`mcp.*` (keeps CLI importable without MCP deps — enforced by `tests/test_import_isolation.py`).
+- `__init__.py` stays empty (no heavy imports at package import time).
+- **Parameters and their descriptions live only in `core/inputs.py`.** The MCP schema and every CLI flag are derived from `model_fields`; never restate a description in an adapter.
+- **Generated files are never hand-edited**: `docs/TOOL_CATALOG.md` and the two skill `references/filter-mapping.md` copies come from `scripts/gen_catalog.py`. CI runs `--check` and fails when they are stale.
+
+---
+
+## The 7 Actions
+
+Canonical table (MCP tool ↔ CLI subcommand ↔ Input model ↔ service ↔ endpoint) and every parameter/type/default are generated into **`docs/TOOL_CATALOG.md`** — read it there instead of copying it here. Sources: `registry.py` (actions) + `core/inputs.py` (params). ID value tables (departure/area/style/return-day/seat/lodge) live in `skills/maitabi-bus-extractor/references/filter-mapping.md`, copied into the other two skills by the generator.
+
+## Contract Guarantees (Enforced by Tests)
+
+- **MCP wire schema** — `tests/test_mcp_schema.py` compares `tools/list` against `tests/fixtures/mcp_schema.json`. Byte-identical unless the change is intentional (then regenerate the fixture in the same commit and call it out in the changelog).
+- **Output shape** — `tests/test_output_contract.py` freezes `detail_url` formats, price/availability filters, multi-day fan-out, batch detail, and error payloads (`{"error", "detail"[, "retry_hint"]}`).
+- **Parity** — `tests/test_parity.py`: 7 MCP tools ↔ 7 CLI subcommands ↔ 7 registry actions.
+- **CLI exit codes** — `tests/test_cli_exit_codes.py`: `0` OK, `1` upstream/network error, `2` input error (bad flag / failed validation).
+
+---
+
+## Workflow (On Every Change)
+
+1. Branch →
+2. Edit core: `core/inputs.py` (params/descriptions) and/or `services/*` (endpoint logic; errors via `core/errors.py`) →
+3. New action only: add one `Action` to `registry.py` (MCP tool + CLI subcommand + catalog row appear automatically) →
+4. `make catalog` (regenerates catalog + skill reference copies) →
+5. Update affected skill `SKILL.md` prose/examples (extractor: cURL; cli: commands; mcp: tool flows) →
+6. Test: `make test` (offline) + `make cli-help` + `make smoke` (live) →
+7. PR → 8. Merge → 9. Tag release (`v*` triggers PyPI + Docker Hub) → 10. `npx skills add -g <repo>`
+
+---
+
+## File Map
+
+| Component | Path |
+|-----------|------|
+| Param source of truth | `src/maitabi/core/inputs.py` |
+| Enums / filters / errors | `src/maitabi/core/{enums,filters,errors}.py` |
+| Services | `src/maitabi/services/{http,bus,general}.py` |
+| Action registry | `src/maitabi/registry.py` |
+| MCP adapter | `src/maitabi/mcp/{tools,server}.py` |
+| CLI adapter | `src/maitabi/cli/{fields,parser,commands,main}.py` |
+| Envelope / query echo | `src/maitabi/core/envelope.py` |
+| Shared MCP transport args | `src/maitabi/mcp_args.py` |
+| Catalog generator | `scripts/gen_catalog.py` → `docs/TOOL_CATALOG.md` + skill copies |
+| Extractor Skill | `skills/maitabi-bus-extractor/SKILL.md` |
+| CLI Skill | `skills/maitabi-cli/SKILL.md` |
+| MCP Skill | `skills/maitabi-mcp/SKILL.md` |
+| Filter Refs (source) | `skills/maitabi-bus-extractor/references/filter-mapping.md` |

maitabi-1.0.0/Dockerfile

@@ -0,0 +1,44 @@
+# Stage 1: Build virtual environment with uv and Python 3.14
+FROM ghcr.io/astral-sh/uv:python3.14-bookworm-slim AS builder
+
+WORKDIR /app
+
+# Enable bytecode compilation
+ENV UV_COMPILE_BYTECODE=1
+ENV UV_LINK_MODE=copy
+
+# Copy project configuration and lock file
+COPY pyproject.toml uv.lock ./
+
+# Sync dependencies first (without installing the local project package)
+RUN --mount=type=cache,target=/root/.cache/uv \
+    uv sync --no-dev --no-editable --no-install-project
+
+# Copy README and source files, then do the final project install
+COPY README.md ./
+COPY src/ src/
+RUN --mount=type=cache,target=/root/.cache/uv \
+    uv sync --no-dev --no-editable
+
+# Stage 2: Minimal runtime image with Python 3.14
+FROM python:3.14-slim-bookworm AS runner
+
+WORKDIR /app
+
+# Copy virtual environment and source code from builder stage
+COPY --from=builder /app/.venv /app/.venv
+COPY --from=builder /app/src /app/src
+
+# Set environment variables
+ENV PATH="/app/.venv/bin:$PATH" \
+    PYTHONUNBUFFERED=1 \
+    PYTHONPATH="/app/src" \
+    MCP_TRANSPORT="stdio" \
+    HOST="0.0.0.0" \
+    PORT="8000"
+
+EXPOSE 8000
+
+# Run the MCP server over stdio or http streamable
+ENTRYPOINT ["maitabi", "mcp"]
+CMD ["--transport", "stdio"]

maitabi-1.0.0/LAUNCHGUIDE.md

@@ -0,0 +1,50 @@
+# Maitabi MCP Server
+
+## Tagline
+Search Japanese alpine bus tours, mountain lodges, and trekking packages from Maitabi.
+
+## Description
+Maitabi MCP Server provides AI agents with real-time access to Japan's premier alpine transportation and mountain tour network, Maitabi (まいたび - 毎日新聞旅行 / 毎日あるぺん号). It enables LLMs to search mountain bus departures across the Japanese Alps (Northern, Central, and Southern Alps including Kamikochi, Tateyama Murodo, Hakuba, Yatsugatake, and Mt. Fuji), filter alpine lodge packages, inspect guided trekking itineraries, check live seat availability, and explore departure calendars. Designed for hikers, outdoor enthusiasts, travel concierges, and trip planning agents.
+
+## Setup Requirements
+- `MCP_TRANSPORT` (optional): Transport protocol to use (`stdio`, `sse`, or `streamable-http`). Default is `stdio`.
+- `PORT` (optional): Port number for HTTP/SSE transport modes. Default is `8000`.
+- `HOST` (optional): Host address to bind for HTTP/SSE transport modes. Default is `0.0.0.0`.
+- `MCP_PATH` (optional): Path for Streamable HTTP transport mode. Default is `/mcp`.
+
+## Category
+Search & Web
+
+## Use Cases
+Japan Alpine Trip Planning, Mountain Bus Departure Search, Mountain Lodge Package Discovery, Guided Trekking Itinerary Exploration, Multi-filter Tour Comparison, Departure Calendar Matrix Tracking, Outdoor & Hiking Concierge, Travel Assistant Integration
+
+## Features
+- Search mountain bus departures and alpine lodge packages across the Japanese Alps (bus.maitabi.jp)
+- Search domestic and overseas guided climbing tours and hiking trips (www.maitabi.jp)
+- Support for multiple departure hubs including Tokyo (Takebashi/Shinjuku), Osaka, Kyoto, and Nagoya
+- Filter by seat classes including Standard, Premium, and Double seat configurations
+- Filter by specific mountain huts and lodges (e.g., Enzanso, Nishiho Sanso, Murodo Sanso)
+- Filter tours by date ranges, price range, and live seat availability (excluding full/closed tours)
+- Retrieve complete tour itineraries, bus stop locations, meal plans, guide details, and direct booking links
+- Extract monthly departure calendar matrix and tour counts for any given year and month
+- Zero API key requirement with direct connection to public Maitabi endpoints
+- Seamless compatibility with stdio, SSE, and Streamable HTTP transports
+
+## Getting Started
+- "Find mountain bus tours from Tokyo to Kamikochi departing next month with available seats."
+- "Search for trekking packages staying at Enzanso lodge with premium bus seating."
+- "Check the departure calendar for domestic mountain climbing tours in August 2026."
+- "Show me tour details, prices, and itinerary for course number 14241."
+- Tool: list_filters — Fetch available filter dropdown options, departure areas, tour styles, mountain lodges, and live tour counts.
+- Tool: list_district_groups — Fetch mountain area/district groups and tour counts based on active filters.
+- Tool: search_tours — Search mountain bus tours and lodge packages with full filter support (departure, date, seat type, lodge, price, availability).
+- Tool: get_tour_detail — Fetch complete tour schedule, pricing matrix, and bus stop details for a specific bus tour by course_no.
+- Tool: search_general_tours — Search general travel tours and alpine trekking packages across 5 categories on www.maitabi.jp.
+- Tool: get_general_tour_detail — Fetch complete itinerary, meal condition, guide info, and booking links for a general tour by course_no.
+- Tool: get_tour_calendar — Fetch monthly departure calendar matrix and tour availability for a given year and month.
+
+## Tags
+maitabi, japan-alps, mountain-bus, trekking, hiking, travel, alpine, kamikochi, tateyama, hakuba, fuji, japan-travel, tour-search, fastmcp, mcp-server
+
+## Documentation URL
+https://github.com/phonhay103/maitabi

maitabi-1.0.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

maitabi-1.0.0/Makefile

@@ -0,0 +1,59 @@
+.PHONY: help install dev dev-http dev-sse test smoke cli-help cli-example docker-build docker-run docker-run-http build catalog catalog-check clean
+
+DOCKER_USER ?= phonhay103
+IMAGE_NAME ?= maitabi
+TAG ?= latest
+HOST ?= 0.0.0.0
+PORT ?= 8000
+
+help: ## Show this help message
+	@echo "Usage: make [target]"
+	@echo ""
+	@echo "Targets:"
+	@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = ":.*?## "}; {printf "  \033[36m%-18s\033[0m %s\n", $$1, $$2}'
+
+install: ## Install dependencies using uv
+	uv sync
+
+dev: ## Run the MCP server locally using stdio transport
+	uv run maitabi mcp --transport stdio
+
+dev-http: ## Run the MCP server locally using Streamable HTTP transport
+	uv run maitabi mcp --transport streamable-http --host $(HOST) --port $(PORT)
+
+dev-sse: ## Run the MCP server locally using SSE transport
+	uv run maitabi mcp --transport sse --host $(HOST) --port $(PORT)
+
+test: ## Run offline test suite (pytest, no network)
+	uv run pytest tests/ -v
+
+smoke: ## LIVE network smoke check against production API (not part of make test)
+	uv run python -c "import asyncio; from maitabi.services.bus import list_filters_service; from maitabi.core.inputs import ListFiltersInput; asyncio.run(list_filters_service(ListFiltersInput())); print('Smoke check passed!')"
+
+catalog: ## Regenerate docs/TOOL_CATALOG.md + skill filter-mapping copies
+	uv run python scripts/gen_catalog.py
+
+catalog-check: ## Fail when generated catalog files are stale (used by CI)
+	uv run python scripts/gen_catalog.py --check
+
+cli-help: ## Show CLI help
+	uv run maitabi --help
+
+cli-example: ## Example CLI search (mountain bus tours)
+	uv run maitabi bus search-tours --departure 1 --month 8 --area 18 --page 1 | head -c 2000
+
+docker-build: ## Build the 2-stage Docker image (Python 3.14)
+	docker build -t $(IMAGE_NAME):$(TAG) -t $(DOCKER_USER)/$(IMAGE_NAME):$(TAG) .
+
+docker-run: ## Run the MCP server inside Docker container (stdio transport)
+	docker run -i --rm $(IMAGE_NAME):$(TAG)
+
+docker-run-http: ## Run the MCP server inside Docker container (Streamable HTTP transport)
+	docker run -i --rm -p $(PORT):$(PORT) $(IMAGE_NAME):$(TAG) --transport streamable-http --port $(PORT)
+
+
+build: ## Build Python package wheel & sdist for PyPI / uvx
+	uv build
+
+clean: ## Remove build artifacts and cache
+	rm -rf .venv __pycache__ .pytest_cache *.egg-info src/*.egg-info dist