Plan with your assistant

Before you connect

Adventure Runner has two separate MCP surfaces. Use the exact deployment origin shown in Account; a loopback URL is accessible only to clients on this machine. Remote AI hosts require an authorized reachable HTTPS deployment.

The guest catalog is /mcp/catalog with no authentication. It exposes list_routes and get_route for the ten public reference variants. It cannot read personal preferences or plans, check trip-date weather, save drafts or generate account exports. Seasonal guidance is not current access clearance.

• Name: Adventure Runner Catalog. Server URL: your deployment origin plus /mcp/catalog. Authentication: None.
• Try: “Use Adventure Runner Catalog to compare Zion Traverse and Teton Crest. Keep source dates, route variants and unconfirmed water/access clear.”

Connect an account

The personal endpoint is /mcp at the same deployment origin. Choose OAuth in a client that supports remote MCP and authorization-code PKCE. Laravel Passport owns OAuth authorization; Google identifies the account owner. Review the registered client, callback and requested access before consenting.

An enabled assistant entitlement and a live owner grant are required for personal operations. No shared API key is entered into chat. The endpoint advertises OAuth discovery; exact authorization, token and registration URLs come from that deployment’s metadata.

• Sign in to the same Adventure Runner account you intend to share.
• Add /mcp as the account connection, choose OAuth, and complete owner consent.
• Begin with a read-only preference request before creating drafts or sharing files.

From route to reviewed plan

Ask for a named route variant, then provide the actual date, local start time, moving hours excluding breaks, and day-trip versus reference-camp style. Samples are assumptions, not predictions of fitness.

Ask about group experience, navigation, water, camps, transport, check-in arrangements and weather review thresholds. A conditions request runs on demand; there is no background watcher or current fire/access clearance.

New plans are pending drafts. Return to Account, refresh proposals and review the route, timing, packing and unresolved arrangements. Approval creates a shared account snapshot. Save a local copy to use it in the browser planner.

• Try: “Help me build a Zion trip. Ask for my missing date, start, moving hours and overnight style before creating a draft.”
• Try: “Read my preferences. Tell me whether they are saved values or defaults; do not change them.”

Edits, preferences and exports

Assistants may propose bounded plan or preference changes. They cannot mark permits/water arranged or approve their own proposals. Use the latest saved revision; stale changes are refused.

Export only the specific plan or draft requested. PDF and mapped GPX links are bearer capabilities: anyone with the URL can download until expiry or revocation. Pending-draft PDFs remain marked as drafts; an export does not approve or save a plan. Revoke download links invalidates issued links, while authorized assistants can generate new ones as long as sharing remains active. Stop sharing or Disconnect to prevent new exports. Existing downloaded copies cannot be recalled.

Account access and billing

Laravel stores account preferences, shared plans, proposals, drafts, export capabilities and grants. Account read/review/revocation operations use the first-party session and CSRF protection. Assistant operations use separate scoped OAuth tokens. Billing is not enabled by this migration.

Host compatibility

Protocol tests establish local transport and tool contracts. They do not prove a particular ChatGPT, Claude, Grok, Gemini, Ollama or Synaptic account can connect to this new Laravel endpoint. Previous production acceptance belongs to the previous endpoint. Check the AI app’s current custom-MCP support, plan and workspace settings.

Synaptic and coding agents

Synaptic Chat Actions and Synaptic Code MCP are separate host surfaces. An operator must configure the selected native endpoint and OAuth client, and each user authorizes their own Adventure Runner account. The former Supabase Actions bridge is not silently reused.

Troubleshooting

A missing trip may be browser-local and never shared; sign-in alone does not upload it. A pending proposal is not a saved change. Refresh the account view and review the matching identifier.

If authorization or tools fail, confirm the exact deployment, reachable HTTPS URL, Google callback, OAuth client, account grant and entitlement. Do not copy passwords, provider tokens or private trip links into troubleshooting messages. Reconnect only after checking that the client supports the advertised protocol.

Privacy and operating limits

Tool arguments and shared plan results pass to the invoking AI host. Send short topic inputs to the public catalog. Shared account plans can contain personal notes and contact agreements. The app and hosting operator must review request logging and retention before production cutover.

This build enables no new paid service, automatic alert, account import or production deployment. Local test results and remaining live acceptance gates are recorded in the project’s migration documentation.