# Itinerary Day Builder AI Agent Connect

> Itinerary Day Builder MCP handles the heavy lifting of travel logistics. It calculates travel times between locations, checks attraction operating hours, and builds daily schedules that respect your time constraints. Instead of guessing if you can make it from a museum to a park, your AI client uses this MCP to verify every stop is physically possible.

## Overview
- **Category:** productivity
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_j27CjymcFUoZd6yCjnmvaRsMl5HdzfYGojviN0RV/ai-agent-connect
- **Tags:** itinerary, travel-planner, scheduling, logistics, optimization

## Description

Planning a trip usually involves a lot of manual math. You have to check when a museum opens, how long you'll spend inside, and how long it takes to get to the next spot. This MCP turns your AI client into a logistics expert. It solves the problem of impossible schedules by reconciling attraction hours with travel latency. 

When you ask your agent to plan a day, it doesn't just list places. It uses specific tools to pull attraction details and calculate the time needed to move between points. If you have a rough idea for a day, you can run it through a validation check to see if it's actually doable. It's about moving from a wish list to a functional, timed itinerary that respects the reality of transit and business hours.

## Tools

### build_optimized_itinerary
This tool creates the most efficient daily schedule based on your chosen locations and time limits.

### get_attraction_details
This tool pulls specific data about an attraction, including its operating hours and unique constraints.

### calculate_travel_time
This tool determines exactly how much time you need to get from one location to another.

### validate_itinerary
This tool checks your proposed sequence of stops to ensure the plan is physically and logically possible.

## Prompt Examples

**Prompt:** 
```
Build me an itinerary for attractions A1, B2, and C3 starting at 09:00 and ending at 18:00.
```

**Response:** 
```
Your optimized itinerary is: 09:00 - 10:30: Attraction A1, 11:00 - 13:00: Attraction B2, 13:30 - 15:30: Attraction C3.
```

**Prompt:** 
```
Is it possible to visit the Grand Museum and the Central Park between 10:00 and 14:00?
```

**Response:** 
```
Yes, that itinerary is valid and fits within your time window.
```

**Prompt:** 
```
What are the opening hours for attraction ID 'museum_01'?
```

**Response:** 
```
The museum is open from 09:00 to 18:00.
```

## Capabilities

### Route Optimization
Your agent uses this to order stops in a way that minimizes wasted time.

### Constraint Checking
The AI checks attraction hours to prevent you from arriving when a place is closed.

### Travel Math
The MCP calculates transit time between every point in your plan.

### Feasibility Testing
Your agent validates a list of locations to confirm the schedule is realistic.

## Use Cases

### Daily Trip Planning
Generate a timed list of activities for a single day in a new city.

### Itinerary Auditing
Check an existing plan to see if you actually have enough time to visit everything.

### Logistics Verification
Confirm that transit times between two specific landmarks fit within a specific window.

### Constraint Management
Ensure all planned stops are open during your intended visit times.

## Benefits

- Eliminates impossible schedules by factoring in travel latency.
- Prevents wasted trips by checking attraction operating hours.
- Reduces manual calculation of transit times between locations.
- Provides instant validation for proposed travel sequences.

## How It Works

Connect your client to Vinkius and start delegating travel math to your agent.

1. Connect your preferred MCP-compatible client to Vinkius.
2. Tell your agent which locations you want to visit and your time constraints.
3. The agent uses the MCP to pull attraction details and calculate travel times.
4. The agent generates or validates a finished, optimized itinerary.

## Frequently Asked Questions

**How does this MCP handle travel times?**
It uses a specific tool to calculate the time required to move between two points, ensuring the schedule accounts for transit.

**Can I check if my current plan is realistic?**
Yes, you can use the validation tool to check if a sequence of locations is physically and logically possible.

**Does it account for when places are closed?**
Yes, the MCP pulls attraction details to ensure your stops align with their operating hours.

**Which AI clients can use this MCP?**
You can use this with any MCP-compatible client like Claude, Cursor, Windsurf, or VS Code.

**Do I need to host this myself?**
No, Vinkius hosts and manages the MCP for you, so it is ready to use immediately after connection.

**How does the engine ensure the itinerary is feasible?**
The engine uses `validate_itinerary` to check that all visits occur within attraction operating hours and that the total time for visits and travel fits within your specified availability window.

**Can I prioritize specific locations?**
Yes, the `build_optimized_itinerary` tool prioritizes attractions based on their assigned importance, ensuring high-priority locations are included whenever possible.

**How is travel time calculated?**
Travel time is determined by the `calculate_travel_time` tool, which uses a transit matrix to find the exact minutes required to move between specific attraction IDs.