Context7
Up-to-date docs for AI agents
作者による説明(英語の原文)
Read-only European city sights: search, nearby, walking routes and itineraries in 6 languages.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
Authorization「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
このアドレスはリクエストの header にキーが必要ですが、コネクタを追加するメニューでは設定できません。代わりにClaude Code、Cursor、VS Codeを使ってください。
ターミナルでこれを実行します
claude mcp add --transport http catalog https://gingerguide.app/mcp --header 'Authorization: your-value'動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"catalog": {
"url": "https://gingerguide.app/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"catalog": {
"type": "http",
"url": "https://gingerguide.app/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
このアドレスはリクエストの header にキーが必要ですが、コネクタを追加するメニューでは設定できません。代わりにClaude Code、Cursor、VS Codeを使ってください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
Authorization 秘密 HTTP headerこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
このサーバーのツール一覧はまだ読み取っていません。エンドポイントは順番にチェックしています。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック
レジストリ名はドメイン gingerguide.app で確認済みです(レジストリがドメインの所有を確認しています)
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
まだチェックしていません。エンドポイントは順番にチェックしています
まだチェックしていません。エンドポイントは順番にチェックしています
まだチェックしていません。エンドポイントをチェックするときにツール一覧を読み取ります
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:Authorization
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は–、最新バージョン(2.0.0)がレジストリに届いたのは25 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。
同じカテゴリには:Context7, Codebase Memory, Exa
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
[Gingerguide](https://gingerguide.app) is a self-guided audio walking tour app for iPhone and Android. It covers 275 European cities and 4,500+ narrated sights in 46 countries. Each sight has a researched 2 to 3 minute story, read by a lifelike AI voice, in English, Spanish, French, German, Turkish and Chinese. Cities work fully offline.
This repository lets AI assistants and agents use the Gingerguide catalog. It contains:
https://gingerguide.app/mcp. Its 14 tools find sights by interest, historical period or location, recommend sights and cities, compare cities, find day trips, give practical visit facts, and plan walking tours and multi-day itineraries, in six languages.SKILL.md format) for audio tour lookup and one-day city walks.The server is read-only. It needs no API key and no sign-in. An optional free API key raises the daily limit (see Optional free API key).
| MCP endpoint | https://gingerguide.app/mcp |
| Transport | Streamable HTTP (stateless, JSON responses) |
| Auth | None required (optional free API key) |
| MCP Registry name | app.gingerguide/catalog |
| Developer docs | https://gingerguide.app/developers/ |
| OpenAPI (REST) | https://gingerguide.app/api/openapi.json |
| llms.txt | https://gingerguide.app/llms.txt |
The server works without a key. Without a key, it allows 1,000 tool calls per IP address per UTC day. Hosted assistants such as Claude and ChatGPT call from a few shared IP addresses, so their requests get 50,000 per IP address per day. A free key raises the limit to 20,000 tool calls per key per day and shows your usage. It is useful when your agent runs on a shared cloud (Vercel, AWS, Cloudflare). Only tools/call counts. There is no sign-up and no email.
# Create a key (it is shown once; the server stores only its hash)
curl -sS -X POST https://gingerguide.app/api/keys \ -H 'content-type: application/json' -d '{"label":"my-agent"}'
curl -sS https://gingerguide.app/mcp \ -H 'authorization: Bearer ggk_...' \ -H 'content-type: application/json' -H 'accept: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
curl -sS https://gingerguide.app/api/keys/me -H 'authorization: Bearer ggk_...' curl -sS -X DELETE https://gingerguide.app/api/keys/me -H 'authorization: Bearer ggk_...'
You can also send the key as X-API-Key. An unknown or revoked key gets HTTP 401. Remove the header to continue without a key. Tool-call responses carry RateLimit and X-RateLimit-Remaining headers. Details: https://gingerguide.app/developers/#api-key.
Every tool is read-only (readOnlyHint: true) and accepts language: en, es, fr, de, tr or zh.
| Tool | What it does | Main arguments |
|---|---|---|
search_attractions | Searches sights in all cities or in one city, by free text, category, interest, historical period, indoor or outdoor, visit length, free entry, or distance from a point. Example: five Byzantine sights in Istanbul. | query, city_id, country, categories, interests, periods, setting, free_only, near_lat, near_lng, radius_km, sort, limit |
find_nearby_attractions | Returns the sights closest to a latitude and longitude, with walking minutes. If no sight is in the radius, it returns the nearest covered city. | lat, lng, radius_km, interests, categories, pace |
get_attraction | Returns one sight: long description, a notable fact, photo, coordinates, map link, visit time and the nearest other sights. In researched cities it adds entry, booking, weekly closing days, dress code and the official site. | attraction_id (for example rome-colosseum) |
get_visit_info | Practical facts for one city: best months and crowd seasons, how to get from the airport, main station or cruise port to the centre, city passes, free sights, what to book ahead, weekly closing days and dress codes. Every fact has a source and a check date. Researched cities only (Rome, Barcelona and Vienna so far); for other cities it says so. | city_id, topics |
search_cities | Finds cities by name (in any of the six languages), country or region. Returns the city id that the other tools need. | query, country, limit |
get_city_guide | Returns one city: overview, headline sights, lesser-known sights, and every sight with category, coordinates and visit time. detail: "full" adds every long description. | city_id, detail |
list_countries | Lists the covered countries with their city ids. | none |
get_catalog_overview | Returns coverage totals, languages, and the exact values that the categories, interests and periods filters accept. | none |
| Tool | What it does | Main arguments |
|---|---|---|
recommend_attractions | Picks sights in one city for the traveler's interests, favourite periods, headline sights or hidden gems, indoor or outdoor, and time available. Each pick says why it was chosen. | city_id, interests, periods, style, setting, available_minutes, exclude_ids |
recommend_destinations | Ranks cities for interests or historical periods, for example "best cities for Byzantine history", and says why. | interests, periods, country, trip_days |
compare_cities | Compares two to four cities side by side: sights, days needed, strongest interests and periods, share of indoor sights, headline sights and the distance between them. Says which city is stronger for each interest or period. | city_ids, interests, periods, trip_days |
find_day_trips | Lists covered cities that make a day trip from a base city, ranked by distance, interests and fame, with what to see there in one day. Sea crossings that need a flight are left out; short ferry trips are marked. | city_id, max_distance_km, interests, periods, hours_on_site |
| Tool | What it does | Main arguments |
|---|---|---|
plan_walking_tour | Builds an ordered walking route in one city for a time budget. Returns each stop with walking minutes, time on site, clock times, and a Google Maps walking link. | city_id, duration_minutes, interests, periods, style, pace, start_lat, start_lng or start_attraction_id, start_time, must_include, weekday |
plan_trip_itinerary | Plans 1 to 7 days in one city. Each day covers one or two walkable areas, with a public transport hop between them. | city_id, days, hours_per_day, interests, periods, style, pace, start_time, start_weekday |
Filter values. Interests: history, architecture, art, museums, religious_sites, archaeology, nature, views, food, local_life, shopping, relaxing, royalty, military, music, literature, science, performing_arts, memorials. Periods: prehistoric, ancient_greek, etruscan, roman, byzantine, medieval, gothic, moorish_islamic, ottoman, renaissance, baroque, georgian_neoclassical, nineteenth_century, art_nouveau, twentieth_century_modern, world_war_ii, cold_war. Style: must_see, balanced, hidden_gems. Pace: relaxed, normal, brisk.
Limits of the data. Interests, periods and indoor or outdoor are derived from each sight's category and description. Walking times are estimates (straight-line distance x 1.3 at the chosen pace). Day-trip and comparison distances are straight-line and come without travel times. With weekday, the planners leave out sights that are closed that day or temporarily closed, in researched cities. Opening hours and ticket prices are not included. Bad input returns an error that names the allowed values.
claude mcp add --transport http gingerguide https://gingerguide.app/mcp
Open Settings → Connectors → Add custom connector. Set the name to Gingerguide and the URL to https://gingerguide.app/mcp.
For older Claude Desktop builds that only read claude_desktop_config.json, use the bridge config in examples/claude_desktop_config.json.
Add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project). File: examples/cursor-mcp.json.
{
"mcpServers": { "gingerguide": { "url": "https://gingerguide.app/mcp" } } }
Add this to .vscode/mcp.json. File: examples/vscode-mcp.json.
{
"servers": { "gingerguide": { "type": "http", "url": "https://gingerguide.app/mcp" } } }
In a workspace or plan that allows custom connectors (developer mode), add a new connector with the URL https://gingerguide.app/mcp and no authentication.
Any MCP client that supports remote Streamable HTTP servers can connect to https://gingerguide.app/mcp. See examples/curl.md for raw JSON-RPC calls.
The skills/ folder has two skills in the SKILL.md format. Claude, Claude Code and other agents that read this format can load them.
| Skill | Use it when a person... |
|---|---|
find-audio-walking-tour | asks for an audio tour, walking tour or self-guided guide for a city |
plan-city-day-with-gingerguide | asks for a one-day itinerary or walking route in a covered city |
The same skills are also served from the website at https://gingerguide.app/.well-known/agent-skills/index.json.
| Endpoint | Returns |
|---|---|
GET https://gingerguide.app/api/cities.json | All cities with id, country, sight count and guide URL |
GET https://gingerguide.app/api/cities/{id}.json | One city with all its sights |
GET https://gingerguide.app/api/openapi.json | The OpenAPI description |
The cli/ folder has the source of the official command-line client. It is on npm as gingerguide.
npx gingerguide cities
npx gingerguide city rome npx gingerguide countries npx gingerguide health
The files in this repository (docs, configs, skills) are under the MIT License. The catalog data that the server and the API return belongs to Gingerguide. See the [ter
冒頭だけを表示しています。続きはリポジトリで読めます