For AI agents

MCP server

japan-like.com runs a read-only MCP (Model Context Protocol) server so AI agents can pull honest, sourced tour listings for Kyoto walks, Tokyo food tours, Okinawa diving, Osaka day trips and Fuji/Hakone day trips. No key or registration is needed.

Endpoint

Tools

ToolWhat it returnsArguments
list_sectionsLists the planning sections (Kyoto walking tours, Tokyo food tours, Okinawa diving, Osaka day trips, Fuji day trips, Hakone day trips) with their page URLs.none
search_toursTour listings for one section: name, area, duration, languages, meeting area, provider listing URL and the checked date — at most 10 listings, never prices. A tracked booking link appears only where the placement is active.section (required; id from list_sections), query (optional, 2–80 characters)
get_planning_guideOne planning guide page: our own title, a summary of at most 600 characters, and the page URL.section (required), slug (required, e.g. best-gion-walking-tours)
kyoto_tour_finderThe free Kyoto tour-fit finder from the site: pick duration, preferred start time and mobility needs; returns at most 3 matching Kyoto Gion listings.duration (any / under-two / around-three), time (any / morning / evening), mobility (comfortable / step-free) — all optional

Every result ends with a source line (for example: Source: japan-like.com (independent travel guide; tour details from Viator listings, checked 2026-10-15). japan-like.com/kyoto/walking-tours) naming the date the listing details were last checked. Results never include prices; booking links are tracked affiliate links (Viator partner P00326056) and are labelled as such.

Example calls

curl -s -X POST https://japan-like.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -d '{"jsonrpc":"2.0","id":1,"method":"server/discover"}'

list_sections:

curl -s -X POST https://japan-like.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_sections","arguments":{}}}'

search_tours:

curl -s -X POST https://japan-like.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_tours","arguments":{"section":"kyoto-walks","query":"gion"}}}'

get_planning_guide:

curl -s -X POST https://japan-like.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get_planning_guide","arguments":{"section":"kyoto-walks","slug":"best-gion-walking-tours"}}}'

kyoto_tour_finder:

curl -s -X POST https://japan-like.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -d '{"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"name":"kyoto_tour_finder","arguments":{"duration":"under-two","time":"evening","mobility":"comfortable"}}}'

Client setup

Claude (web, desktop, mobile)

Settings → Customize → Connectors → add a custom connector with the server URL https://japan-like.com/mcp (no key needed). Free plans are limited to one custom connector.

Source: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp

Cursor

Add to mcp.json: {"mcpServers": {"japan-like": {"url": "https://japan-like.com/mcp"}}}

Source: https://cursor.com/docs/mcp

Claude Code

claude mcp add --transport http japan-like https://japan-like.com/mcp

Source: https://code.claude.com/docs/en/mcp

ChatGPT

Custom MCP apps require developer mode. As of 24 Oct 2026, full MCP support is limited to Business, Enterprise and Edu workspaces and needs an admin to enable developer mode.

Source: https://help.openai.com/en/articles/12584461

Limits and fair use

Privacy

Each tool call logs one analytics event with the tool name, the request inputs trimmed to at most 80 characters each, a short response summary (result count, top result name, error), status, the client name when sent, and a hashed (never raw) IP address. Full responses are never logged. MCP traffic is excluded from the site's page-view and product analytics. Inputs are intended to be kept for at most 30 days.