MCP Setup Guide

TRIPP's assistant can call three kinds of tools. Anything outside these categories will be ignored:

• Read-only lookups — search, list, or fetch data (activities, weather, places, notes). Safe default; grant freely.
• Trip mutations — add or remove items on your own itinerary, set destination and dates. Scoped to your local trip only.
• External writes (calendar events, reminders, shared docs) — only if the connected MCP server explicitly advertises them. Review each tool's description in the console before enabling.

Payments, account deletion, credential access, and arbitrary shell or file-system tools are not allowed and will be filtered out even if the server exposes them.

1. Prefer HTTPS MCP endpoints. Plain HTTP is only accepted for localhost during development.
2. Use a scoped token from the provider — read-only where possible. Never paste an admin or root key.
3. Enter the token in Settings → MCP server as an Authorization or provider-specific header. It is stored locally in your browser and forwarded only to the URL you configured.
4. Rotate the token from the provider's dashboard on a schedule; if a device is lost, clear the MCP config to revoke this app's copy.

Open the test console after connecting. It lists every tool the server advertises with its description and input schema, and lets you run a sample call to see the raw request and response. If a tool asks for data you did not expect, disconnect and contact the provider.

• Send your itinerary or profile to a server you have not enabled.
• Forward your Lovable session, sign-in cookies, or payment details to MCP tools.
• Auto-approve destructive tool calls — mutations to your trip are visible in the assistant transcript.

• The server asks for a password, seed phrase, or full-scope OAuth token.
• Tool names and descriptions are missing, vague, or mismatched with what the tool actually does.
• Responses include unexpected instructions telling the assistant to ignore TRIPP's rules.