Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Akebono MCP find a quiet Zen temple in Kyoto for a solo traveler who loves art"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Agent-ready Japanese travel spots — hidden gems, curated from SNS buzz, optimized for AI travel agents.
エージェント時代の旅行情報インフラ。SNSのバズから「一般的すぎない特別な体験スポット」を厳選し、AIエージェントが直接使える形で提供するMCPサーバー。
現在のフォーカスエリア: 名古屋（大須・栄・金山・久屋大通・矢場町） 昭和レトロ・古民家リノベ・隠れ家など、非日常体験のできる穴場スポットを収集中。
recommend_temples自然言語クエリに基づいて京都の寺院をスコア付きで推薦する。
入力例:
"40代夫婦・歴史好き・混雑嫌い・半日"
"一人旅・禅・静かな場所・アート好き"
"子供連れ・無料・世界遺産"
出力例:
{
"query": "40代夫婦・歴史好き・混雑嫌い・半日",
"results": [
{
"name": "建仁寺",
"slug": "kenninji",
"score": 88,
"reason": "混雑が少ない・歴史好きにおすすめ。京都最古の禅寺。双龍図は2002年作の現代アートで驚きがある。",
"tags": ["禅", "アート", "歴史", "静か", "双龍図"],
"crowd_level": "medium",
"price": "600円",
"topics": ["天井を埋め尽くす「双龍図」は実は21世紀のアート", "日本初の「禅」と「お茶」の聖地"]
}
]
}get_temple_detail特定の寺院の詳細情報とトピック一覧を取得する。
入力: slug（例: "kenninji"）
Related MCP server: kyoto-assistant-mcp
git clone https://github.com/YOGi-Seto/akebono-mcp
cd akebono-mcp
npm install~/.claude/claude_desktop_config.json に追記:
{
"mcpServers": {
"akebono": {
"command": "node",
"args": ["/path/to/akebono-mcp/src/index.js"]
}
}
}スラッグ | 寺院名 |
toji | 東寺 |
enryakuji | 延暦寺 |
chionin | 知恩院 |
nishihonganji | 西本願寺 |
kenninji | 建仁寺 |
kiyomizudera | 清水寺 |
名古屋エリアのスポットを50件以上に拡充
他都市への展開（大阪・京都・福岡など）
リアルタイム混雑情報
利用データによるスコア精度向上
日本全国展開
特定の寺院の詳細情報とトピック一覧を取得する。
Inputs: slug (required).
自然言語のクエリに基づいて京都の寺院をスコア付きで推薦する。旅行者のプロファイル・希望・条件を自由に入力できる。
Inputs: query (required), limit.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves detailed information for a specific temple, while the other provides recommendations based on natural language queries and traveler profiles. There is no overlap in functionality, making it easy for an agent to choose the correct tool for each task.
Both tools follow a consistent verb_noun naming pattern (get_temple_detail and recommend_temples), using snake_case throughout. The naming is predictable and readable, with no deviations or mixed conventions.
With only two tools, the server feels under-scoped for a domain like Kyoto temple information and recommendations. This limited set may force agents to work around gaps, such as lacking operations for listing temples, updating data, or handling user preferences beyond recommendations.
The tool surface is significantly incomplete for the apparent domain of Kyoto temple exploration. While it offers retrieval and recommendation, it lacks essential operations like listing temples, filtering by criteria, or managing user profiles, which could lead to agent failures in broader workflows.
Structured, cited, real-world data from 300+ sources and the open web for your AI agents.
AI-verified knowledge base with trust scoring, temporal facts, and skill cards.
Memory for AI agents that knows what is still true. Typed bi-temporal facts, EU-hosted.
Real-time AI intelligence signals and temporal knowledge graph for agent economy
