Travel Planner MCP Server (@gongrzhe/server-travelplanner-mcp)

Created By
GongRzhea year ago
Travel planning and itinerary management microservice server
Overview

what is Travel Planner MCP Server?

Travel Planner MCP Server is a microservice designed for travel planning and itinerary management, enabling interaction with Google Maps and other travel services.

how to use Travel Planner MCP Server?

To use the Travel Planner MCP Server, you can install it via Smithery or manually using npx. You will need to provide your Google Maps API key for full functionality.

key features of Travel Planner MCP Server?

  • Search for places using Google Places API
  • Retrieve detailed information about specific places
  • Calculate routes between locations
  • Get timezone information for specific locations

use cases of Travel Planner MCP Server?

  1. Finding restaurants or attractions in a specific area.
  2. Planning routes for road trips or travel itineraries.
  3. Integrating travel planning features into applications using LLMs.

FAQ from Travel Planner MCP Server?

  • What APIs does the Travel Planner MCP Server use?

It uses Google Maps APIs including Places API, Directions API, Geocoding API, and Time Zone API.

  • Is there a cost associated with using the Travel Planner MCP Server?

The server itself is free to use, but you will need a Google Maps API key, which may incur costs depending on usage.

  • Can I run this server locally?

Yes, you can run the server locally after installation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
GongRzhe
Star
7
Language
JavaScript
License
MIT license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago