Trip Planner
Wire Claude Code or Cursor to AI Trips so your agent can research flights, stays, activities, tasks, and maps while you plan travel without leaving the editor.
Overview
io.aitrips/trip-planner is an MCP server for the Build phase that connects your agent to AI Trips for flights, activities, accommodations, tasks, and map-backed trip planning over streamable HTTP.
What is this MCP server?
- AI-native trip planning across flights, activities, accommodations, tasks, and maps from one MCP remote
- Streamable HTTP endpoint at aitrips.io/api/ai/mcp for MCP-compatible clients
- Authorization via API key (tpk_ prefix) or OAuth access token in the Bearer header
- Published server schema v2025-12-11 with version 1.0.0 and GitHub source at astondg/trip-planner
- MCP integration for agents—not a local skill file or marketplace bundle
- Server version 1.0.0 per MCP server.schema.json
- Single streamable-http remote: https://aitrips.io/api/ai/mcp
- Five capability areas named in the catalog description: flights, activities, accommodations, tasks, and maps
What problem does it solve?
Jumping between travel sites and your coding agent breaks context when you want flights, hotels, activities, and maps researched in one conversational workflow.
Who is it for?
Solo builders who already use MCP in Claude Code or Cursor and want agent-driven trip research, itinerary tasks, and map context through a single authenticated remote.
Skip if: Teams that need on-prem travel data, offline-only planning, or a no-API-key consumer app experience without configuring MCP remotes.
What do I get? / Deliverables
After you add the remote MCP URL and Bearer token, your agent can call AI Trips-backed planning capabilities from Claude Code or Cursor without manual copy-paste across tabs.
- Agent-callable trip planning surface covering flights, activities, accommodations, tasks, and maps via the registered re
- Authenticated MCP session ready for iterative itinerary and research prompts in your editor
Recommended MCP Servers
Journey fit
Skillselion shelves MCP servers under Build because registration and auth setup are part of extending your agent stack before or alongside product work, not a launch or growth tactic. Trip Planner is a remote streamable-http MCP with a required Bearer credential—exactly the agent-tooling pattern solo builders use to add third-party APIs to coding agents.
How it compares
Remote MCP travel integration backed by AI Trips, not a repository SKILL.md workflow or a generic web-scraping skill.
Common Questions / FAQ
Who is io.aitrips/trip-planner for?
It is for developers and solo builders who use MCP-capable agents and want AI-native trip planning—flights, stays, activities, tasks, and maps—inside Claude Code, Cursor, or similar clients.
When should I use io.aitrips/trip-planner?
Use it when you are configuring agent-tooling during Build and need structured trip planning APIs in the same session as other agent work, with a tpk_ API key or OAuth Bearer token ready.
How do I add io.aitrips/trip-planner to my agent?
Register the streamable-http remote at https://aitrips.io/api/ai/mcp in your MCP client and set the Authorization header to Bearer plus your tpk_-prefixed API key or OAuth access token.