mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-10-18 21:16:47 +00:00
Maurice
7da0080557
* docs(wiki): correct the install and operations pages for 4.0.0 Quick Start passed docker an empty ENCRYPTION_KEY: an assignment prefix is not expanded on the same command line, so the server silently generated its own key instead of taking the one the page told you to set. The tag examples pinned to the 3.x line, the documented tmpfs size did not match the shipped compose file, and several .env values were described as reaching the container when compose never interpolates them. * docs(wiki): match the MCP reference to the registered surface The scope table was missing the whole Collections group and the totals said 27 scopes across 13 groups where the code registers 29 across 14. The Cloudflare link on the setup page pointed at an anchor on its own page instead of the heading on Troubleshooting. * docs(wiki): correct the plugin and admin pages Three links to Plugin-Development carried a .md suffix, which does not resolve on the wiki. The admin pages described tabs, permissions and storage behaviour that had moved on. * docs(wiki): bring the feature pages back in line with the app Costs still documented the old panel, where categories could be added, renamed, reordered and deleted; they are fixed now and the panel is a day-grouped ledger with settlements. Trip sharing, journeys, maps, packing, reservations and the account pages had all drifted in the same way. * docs(wiki): cover the pages the first pass did not reach The MCP catalog listed 168 of the 201 registered tools; the settlement tools and rate_place were missing here and the Collections family from the addon page. Several resource rows claimed a trips:* scope where the handler asks for trips:read. * docs(wiki): tighten the corrections a review picked apart The audit-log resource is the row id, not the credential id; an admin password reset does not bump password_version the way the page implied; and a few of the new paragraphs described behaviour more confidently than the code supports. * docs(wiki): fix what a last read-through caught Costs shows every figure in your display currency, not the trip's, and an expense with no payer still counts against the members it is split between. Studio's cutoff is a 1024px viewport rather than phones alone, and the Integrations tab is gated on the providers an admin has configured. * docs(wiki): the last few the review caught A passkey satisfies the MFA policy everywhere except the WebSocket handshake, which still asks for TOTP, so a passkey-only account under that policy gets no live updates. Mobile optimizes a day from two places, not three. The ctx.db row carried an unescaped pipe that split the table, and the Backups table linked with a wiki link whose pipe did the same.
4.5 KiB
4.5 KiB
MCP Scopes
OAuth scopes control exactly which data your AI client can read or write in TREK. You select scopes during the OAuth consent screen or when pre-creating an OAuth client. You can revoke access at any time by deleting the OAuth client or token from Settings → Integrations → MCP.
All scopes
TREK defines 29 scopes across 14 groups.
| Group | Scope | Permission |
|---|---|---|
| Trips | trips:read |
View trips, days, day notes, and members |
trips:write |
Create and update trips; create, update, and delete days, day notes, and accommodations; manage members; duplicate trips | |
trips:delete |
Permanently delete entire trips (irreversible) | |
trips:share |
Create, update, and revoke public share links for trips | |
| Places | places:read |
Read places, day assignments, tags, and categories |
places:write |
Create, update, and delete places, assignments, and tags | |
| Collections | collections:read |
Read saved-place collections, their places, ratings, labels, and members |
collections:write |
Create and edit collections, save, rate, label and copy places, and share lists | |
| Atlas | atlas:read |
Read visited countries, regions, and bucket list |
atlas:write |
Mark countries and regions visited, manage bucket list | |
| Packing | packing:read |
Read packing items, bags, and category assignees |
packing:write |
Add, update, delete, toggle, and reorder packing items and bags | |
| To-dos | todos:read |
Read trip to-do items and category assignees |
todos:write |
Create, update, toggle, delete, and reorder to-do items | |
| Budget | budget:read |
Read budget items and expense breakdown |
budget:write |
Create, update, and delete budget items | |
| Reservations | reservations:read |
Read reservations and accommodation details |
reservations:write |
Create, update, delete, and reorder reservations | |
| Collaboration | collab:read |
Read collab notes, polls, and messages |
collab:write |
Create, update, and delete collab notes, polls, and messages | |
| Notifications | notifications:read |
Read in-app notifications and unread counts |
notifications:write |
Mark notifications as read or unread (individually or all at once) | |
| Vacation | vacay:read |
Read vacation planning data, entries, and stats |
vacay:write |
Create and manage vacation entries, holidays, and team plans | |
| Geo | geo:read |
Search locations and public transit routes, resolve map URLs, and reverse-geocode coordinates |
| Weather | weather:read |
Fetch weather forecasts for trip locations and dates |
| Journey | journey:read |
Read journeys, entries, and contributor list |
journey:write |
Create, update, and delete journeys and their entries | |
journey:share |
Create, update, and revoke public share links for journeys |
Scope rules
- A
:writescope implies:readaccess for the same group (e.g.budget:writealso grants read access to budget data). - Any
trips:*scope (trips:read,trips:write,trips:delete, ortrips:share) grants trip read access. journey:readorjourney:writegrants journey read access.journey:sharealone does not grant read access — it only enables managing public share links.list_tripsandget_trip_summaryare always available regardless of scope — they are navigation tools.- Static tokens and web session JWTs have full access equivalent to all scopes.
- Addon-gated tools (Packing, To-dos, Budget, Collections, Atlas, Collab, Vacay, Journey) require both the relevant scope and the corresponding addon to be enabled by an admin. The to-do tools ride the Packing addon, not an addon of their own.
Choosing the right scopes
Grant only what you need. Some examples:
| Use case | Minimum scopes |
|---|---|
| Read-only AI assistant | All :read scopes relevant to your data |
| Full trip planner | All scopes except :delete (use the Claude.ai or Claude Desktop preset) |
| Budget review only | trips:read + budget:read |
| Packing list assistant | trips:read + packing:read + packing:write |
| Journey writer | trips:read + journey:read + journey:write |
The preset buttons in Settings → Integrations → MCP → OAuth Clients fill in a reasonable scope set for common clients. VS Code defaults to read-only scopes; Claude.ai and Claude Desktop default to all scopes except :delete.