Skip to main content
Glama
idean3885

trip-planner-mcp

by idean3885
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

우리의 여행 ✈️

대화로 만드는 여행 플래너. 일정·숙소·활동을 한곳에 모아 동행자와 함께 모바일에서 바로 열어 씁니다.

trip.idean.me 에 접속하면 프로젝트 랜딩을 먼저 만나고, Google 로그인 한 번으로 바로 쓸 수 있습니다.

이 프로젝트는

AI 에이전트와 바이브 코딩으로 만든 개인 여행 플래너. 자연어로 검색하고 → 웹·API로 일정을 생성해 → 동행자와 함께 플래닝하고 → 현장에선 소소한 가계부가 됩니다.

같이 갈 사람과 대화로 여행을 계획하고, 웹에서 함께 다듬어 현장까지 들고 가는 개인 프로젝트입니다. 어떤 기술로 만들었고 어떻게 운영하는지는 docs/ARCHITECTURE.md에 정리해 두었습니다.

Related MCP server: Trip Planner MCP

어디로 가시나요

써보고 싶은 분 (외부 방문자)

위 링크 한 개로 충분합니다 — 랜딩에서 시작 CTA를 누르면 Google 로그인 → 여행 생성으로 바로 이어집니다.

  • 프로젝트 전반 소개는 랜딩 하단의 프로젝트 소개 링크(About 페이지)에서 더 자세히 읽을 수 있습니다

  • AI 에이전트까지 쓰고 싶다면 아래 빠른 시작의 한 줄 curl을 보세요

기술이 궁금하신 분

구조가 궁금하면 docs/ARCHITECTURE.md 한 문서면 됩니다. 시스템 구성도·주요 흐름·도메인·데이터 스키마를 그림 위주로 봅니다. 스펙을 어떻게 관리하는지(speckit)도 같은 문서에 짧게 언급돼 있습니다.

코드까지 들어가려면 개발 문서 목차 docs/README.md 에서 세팅·도메인·업무 프로세스로 이어집니다.

빠른 시작

# AI 에이전트(MCP) 설치 — 맥북 1줄
curl -sSL https://raw.githubusercontent.com/idean3885/trip-planner/main/scripts/install.sh | bash

설치 중 브라우저가 열리면 Google 로그인만 하세요. 토큰이 자동 저장됩니다. 이후 Claude에게 자연어로 요청하면 됩니다 — 예) "포르투 6월 10일 리스본행 항공편 찾아줘", "3일차 벨렘탑 09:00~11:00 추가해줘".

웹에서만 쓰고 싶다면 위 "써보고 싶은 분" 섹션의 링크로 바로 들어가면 됩니다.

구글 캘린더 연동 제약 (현재 심사 전 단계)

본 앱은 아직 앱 심사 전 단계라, 개발자가 직접 허용한 Google 계정(최대 100명)만 구글 캘린더 연동을 사용할 수 있습니다. 앱 내 일정 조회·편집은 누구나 정상 이용 가능하며, 연동만 등록 사용자에게 한정됩니다.

연동 등록을 원하시면 공개 토론 채널의 Q&A에 가입 Google 이메일을 남겨 주세요.

링크

랜딩·웹앱

trip.idean.me

저장소

github.com/idean3885/trip-planner

개발 문서

docs/README.md

변경 이력

CHANGELOG.md

업무 프로세스

docs/WORKFLOW.md

License: MIT · Author: idean3885

Available Tools

1 tool
get_day_contentA

일자의 전체 마크다운 콘텐츠를 조회한다. 활동 변환 시 원본 확인용.

Args: trip_id: 여행 ID day_id: 일자 ID (get_trip에서 확인)

ParametersJSON Schema
NameRequiredDescriptionDefault
day_idYes
trip_idYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, and the description only states 'retrieves full markdown content'. It does not disclose behavioral traits like read-only nature, error handling, or performance. However, the tool is simple and the description is adequate for a get operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise: two sentences and arg definitions, no fluff. It is front-loaded with the main purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, so return values are covered. The description is complete for a simple read operation with no missing gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description adds meaning to both parameters: trip_id is '여행 ID' and day_id is '일자 ID' with a note to confirm via get_trip. This helps beyond the schema's basic type and title.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves the full markdown content of a day, with a specific use case (checking original when converting activities). It is distinct from siblings like clear_day_content or update_day.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions a specific use case ('활동 변환 시 원본 확인용'), giving context for when to use. It does not explicitly exclude other uses or mention alternatives, but the purpose is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 19 tool updatesv4.12.2
    • Removedclear_day_content
    • Removedcreate_activity
    • Removedcreate_day
    • Removeddelete_activity
    • Removeddelete_day
    • Removedget_attraction_details
    • Removedget_hotel_details
    • Removedget_hotels
    • Removedget_trip
    • Removedlist_members
    • Removedlist_trips
    • Removedreorder_activities
    • Removedsearch_attraction_locations
    • Removedsearch_attractions
    • Removedsearch_destinations
    • Removedsearch_flight_destinations
    • Removedsearch_flights
    • Removedupdate_activity
    • Removedupdate_day
  2. 2 tool updatesv4.1.0
    • Changedcreate_activity2 fields changed
      • addedInput schema / properties / payment_timing
        Added value: +{
+  "default": "",
+  "title": "Payment Timing",
+  "type": "string"
+}
      • removedInput schema / properties / reservation_status
        Removed value: -{
-  "default": "",
-  "title": "Reservation Status",
-  "type": "string"
-}
    • Changedupdate_activity2 fields changed
      • addedInput schema / properties / payment_timing
        Added value: +{
+  "default": "",
+  "title": "Payment Timing",
+  "type": "string"
+}
      • removedInput schema / properties / reservation_status
        Removed value: -{
-  "default": "",
-  "title": "Reservation Status",
-  "type": "string"
-}
  3. 2 tool updatesv3.22.0
    • Changedcreate_activity1 field changed
      • addedInput schema / properties / url
        Added value: +{
+  "default": "",
+  "title": "Url",
+  "type": "string"
+}
    • Changedupdate_activity1 field changed
      • addedInput schema / properties / url
        Added value: +{
+  "default": "",
+  "title": "Url",
+  "type": "string"
+}
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no risk of confusion between tools.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern ('get_day_content').

Tool Count1/5

A trip planner server with only one tool is severely under-scoped; a typical trip planner would need many more operations.

Completeness1/5

The tool surface is extremely limited, lacking any CRUD operations for trips, days, or activities, making it incomplete for a trip planner.

Maintenance

ActivitySlowing
ResponsivenessResponsive

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Trip Planner MCP

    SUSHRUTH3002
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables multi-agent trip planning with coordinated specialized agents for team management, food preferences, and travel recommendations. Integrates Neo4j employee graphs, Postgres data, real-time weather APIs, and country information for comprehensive travel planning.
    -
  • mcp-travelcode by Travel-Code-Inc

    mcp-travelcodeofficial

    Travel-Code-Inc
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI assistants to search flights and hotels, manage bookings, check flight status, and access delay statistics through the TravelCode corporate travel API, all via natural language conversations.
    12
    2
    MIT

Appeared in Searches