Productivity

yoteiko.com

Manages travel itineraries by creating, modifying, retrieving, listing, and forking itineraries with days and places.

1 endpoint16 known toolsFirst detected September 29, 2026Last detected September 29, 2026

ENDPOINT 1

https://mcp.yoteiko.com/mcp

No auth detected

MCP server metadata

Name: yoteiko-travel
Version: 2.0.0

Capabilities

tools.listChanged

Server instructions

You are connected to Yoteiko, a travel planning platform. You can create itineraries, search destinations worldwide, find hotels, restaurants, attractions, and events, and help users plan their trips. Workflow for planning a trip: 1. Ask the user about their destination, dates, budget, and travel style 2. Use search_destinations to find the destination 3. Use search_hotels, search_restaurants, search_attractions to find places 4. Use create_itinerary to build the trip plan 5. Show the user the full itinerary and offer to modify it 6. Use modify_itinerary with natural language for any changes 7. Use publish_itinerary to share with the community, or share_itinerary for a link For inspiration, use search_communities to find popular itineraries. For write operations (create, modify, publish, share), the user must be authenticated.

Known tools 16

create_itinerary

Create a new travel itinerary.

Potential side effects

modify_itinerary

SIMPLE modifications only — change title, set budget, add tag, set destination, set description, set season, set travel type.

Inferred read-only

get_itinerary

Retrieve full details of a travel itinerary including all days and places.

Inferred read-only

list_itineraries

List the user's travel itineraries with optional filters.

Inferred read-only

fork_itinerary

Create a copy of a community itinerary in the user's account for customization.

Potential side effects

publish_itinerary

Publish an itinerary to the Yoteiko community, making it publicly visible.

Potential side effects

share_itinerary

Generate a shareable link for an itinerary.

Inferred read-only

delete_itinerary

Permanently delete an itinerary by ID or by exact name.

Potential side effects

set_itinerary_status

Change an itinerary between draft and published.

Inferred read-only

update_itinerary

USE THIS TOOL for adding days with places, replacing the full itinerary, or any complex changes.

Inferred read-only

search_destinations

Search for travel destinations worldwide.

Inferred read-only

search_hotels

Search for hotels at a destination.

Inferred read-only

search_restaurants

Search for restaurants at a destination.

Inferred read-only

search_attractions

Search for tourist attractions at a destination.

Inferred read-only

search_events

Search for events at a destination within a date range.

Inferred read-only

search_communities

Search published community itineraries for inspiration.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.yoteiko-travel]
url = "https://mcp.yoteiko.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "yoteiko-travel": {
      "type": "http",
      "url": "https://mcp.yoteiko.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: yoteiko-travel
Remote MCP URL: https://mcp.yoteiko.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "yoteiko-travel": {
      "url": "https://mcp.yoteiko.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "yoteiko-travel": {
      "type": "http",
      "url": "https://mcp.yoteiko.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "yoteiko-travel",
  "transport": "streamable-http",
  "url": "https://mcp.yoteiko.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.