# Goshuin Atlas
Discover temples, shrines, and goshuin in Japan and plan culturally respectful
visits. The plugin combines a travel planning skill with four public catalogue tools and an optional saved-places tool. You can use it without collecting
goshuin, sharing your exact location, or signing in to Goshuin Atlas.
Try asking:
- "Find temples and shrines in Kyoto and explain why each might suit a first visit."
- "Find Fushimi Inari Taisha, then compare other sacred places within 20 km."
- "Find paper-cutting goshuin designs and explain what to confirm before visiting."
The tools search public records, retrieve a selected place brief, find places
around a public place anchor, and search approved goshuin designs. Nearby
distances are straight-line comparisons. Confirm transport routes, opening
hours, admission, accessibility, closures, and goshuin availability with current
official sources. A missing result describes catalogue coverage.
Connect your Goshuin Atlas account only when you want to read your saved temples
and shrines. The optional `saved_places.read` permission returns public place
details from your saved list; it excludes notes, visits, photos and other lists.
You can disconnect at `https://goshuin.com/auth/mcp`.
The plugin cannot book, save private trips, accept uploads,
search hotels or restaurants, or change records. If the catalogue is unavailable,
the skill can continue with attributed official web research when browsing is
available.
## Data handling
The remote MCP endpoint is `https://mcp.goshuin.com/mcp`. Send only bounded place
or goshuin searches and returned public identifiers. Do not send exact GPS,
credentials, booking references, private records, or sensitive personal details.
Public tools use an immutable snapshot. The MCP has no database credential;
the optional saved-places tool calls Goshuin Atlas’s account service over HTTPS
with a token digest and separate service authentication. Access tokens expire
after 15 minutes, refresh credentials rotate, and connections expire after
30 days unless you disconnect sooner. Credentials travel through the client’s
OAuth flow; never paste them into a conversation.
Operational controls use bounded counters and daily HMAC-derived address
identifiers; application logs exclude query text and results.
[Website](https://goshuin.com/en/apps/goshuin-atlas) ·
[Support](https://goshuin.com/en/contact) ·
[Privacy](https://goshuin.com/en/privacy) ·
[Terms](https://goshuin.com/en/terms)
## Claude release preparation
The Claude manifest is `.claude-plugin/plugin.json`; skills and `.mcp.json` are
shared with the maintained OpenAI package. Version 1.3.0 publication is pending. The distribution repository is
[goshuin-atlas-plugin](https://github.com/thedaviddias/goshuin-atlas-plugin).
To prepare a clean Claude bundle from the source repository, run:
```sh
pnpm exec node scripts/plugins/package-goshuin-atlas-claude.mjs /tmp/goshuin-atlas-claude-release
```
The exporter requires a new destination and includes only the manifest, MCP
configuration, README, skills, and image assets. Submit the exported folder from
a dedicated public GitHub distribution repository. Keep the private application
repository private. Submit the hosted MCP as a connector before the plugin bundle
in the same Claude organization. The endpoint must pass live tool calls before
either listing is submitted.
For a local Claude Code check of the exported bundle:
```sh
claude plugin validate /tmp/goshuin-atlas-claude-release
claude --plugin-dir /tmp/goshuin-atlas-claude-release
```
The frozen OpenAI submission assets remain separate from the Claude export.