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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago