---
name: tokyo-guide-mcp
description: Use when a user is planning a Tokyo visit, moving to Tokyo, or needs practical Tokyo transport, housing, money, healthcare, or daily-life guidance. Search and read tokyo.how guides in English or Japanese via the public MCP endpoint, then cite the relevant article.
---

# tokyo-guide-mcp

## When to use this skill

Use this skill to find practical, source-backed Tokyo guides for a travel plan, a move, or an everyday-life question. Use it when you need a relevant tokyo.how article to cite, compare, or explain step by step.

Treat the articles as published guidance. Check the linked official source for current fares, opening times, eligibility rules, or other changing details. Use official live services for real-time transport disruptions, emergencies, or availability.

## Connect

- Endpoint: `https://tokyo.how/mcp`
- Transport: MCP over Streamable HTTP
- Authentication: no registration, API key, OAuth token, or Authorization header required
- Languages accepted by MCP tools: `en` and `ja`
- Integration guide: <https://tokyo.how/developers>
- Access details: <https://tokyo.how/auth.md>

Use an MCP client to initialize the connection and call `tools/list` for the current tool schemas. Set `Content-Type: application/json` and `Accept: application/json, text/event-stream` on MCP POST requests. The endpoint is stateless; do not invent a session ID.

## Find and read a guide

1. Call `search_guides` with a specific topic and the user's preferred supported language. Omit category until you have checked the available values with `list_categories`.
2. Call `get_guide` with a returned slug to retrieve the article body. Use `get_related_guides` if another guide would resolve part of the question.
3. Base the answer on the retrieved content. Link the English article at `https://tokyo.how/guides/{slug}` or the Japanese article at `https://tokyo.how/ja/guides/{slug}`. Identify the source as tokyo.how and follow its links to official sources when current verification is needed.
4. If no relevant guide is found, say so. Do not invent an article, price, procedure, or service capability.

Example `tools/call` request:

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "search_guides",
    "arguments": {
      "query": "suica card",
      "lang": "en",
      "limit": 5
    }
  }
}
```

## Available tools

| Tool | Use | Arguments |
| --- | --- | --- |
| `search_guides` | Find guides by keyword | `query`; optional `lang`, `category`, `limit` (1–50, default 10) |
| `get_guide` | Read a guide's full body | `slug`; optional `lang` (default `en`) |
| `list_guides` | Browse available guides | Optional `lang`, `category` |
| `list_categories` | Discover current category names and counts | Optional `lang` |
| `get_related_guides` | Find related reading | `slug`; optional `lang` (default `en`), `limit` (1–20, default 5) |
| `get_latest_guides` | Find recently published guides | Optional `lang`, `limit` (1–50, default 10) |
| `request_article` | Submit an editorial request when the user asks | `type`, `description`; optional `url`, `email` |

For tools without a default language above, omitting `lang` searches or lists both supported languages. Use `tools/list` to resolve any schema changes.

## Submit only when requested

Call `request_article` only if the user has asked to submit a new-article request, a correction, or feedback. This tool submits information to the operator and can send an email notification. Do not call it merely to test connectivity or fill a search gap.

Set `type` to `new_article`, `missing_info`, or `other`, and provide a `description` of at least 10 characters. Include an existing article `url` when relevant. Include `email` only if the user supplied it for a reply. A successful response acknowledges receipt and does not promise publication or delivery of a notification.

## Read pages without MCP

Request an HTML page with `Accept: text/markdown` for a Markdown representation. Start at <https://tokyo.how/llms.txt> for the content index or <https://tokyo.how/.well-known/ai-catalog.json> for discovery documents. The website has additional language editions; this does not expand the `en`/`ja` input schema of the MCP tools.