From c0e3fde6f70f088bbd1be47384e07086b7a641c6 Mon Sep 17 00:00:00 2001 From: amo Date: Sat, 12 Sep 2026 13:08:18 +1000 Subject: [PATCH 1/2] Clarify settings path for creating machine client Updated instructions to specify 'user' in settings path. Without it, minor confusion to be still operating in main 'Admin' settings where you enabled MCP integration --- wiki/MCP-Setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/MCP-Setup.md b/wiki/MCP-Setup.md index 9fa95c8c3..1fe562939 100644 --- a/wiki/MCP-Setup.md +++ b/wiki/MCP-Setup.md @@ -94,7 +94,7 @@ Use this when your AI agent or automation script needs to authenticate silently ### Create a machine client -1. Go to **Settings → Integrations → MCP → OAuth 2.1 Clients** and click **New Client**. +1. Go to (user) **Settings → Integrations → MCP → OAuth 2.1 Clients** and click **New Client**. 2. Tick **Machine client (no browser login)**. The redirect URI field disappears — machine clients don't need one. 3. Give it a name, select scopes, and click **Register Client**. 4. Copy the `client_id` and `client_secret` shown — the secret is displayed only once. From b90d258b6c50db3ad68a9855840478f2efd577d6 Mon Sep 17 00:00:00 2001 From: Maurice Date: Sat, 12 Sep 2026 12:55:34 +0200 Subject: [PATCH 2/2] docs(mcp): say whose settings the OAuth client lives in --- wiki/MCP-Scopes.md | 4 ++-- wiki/MCP-Setup.md | 10 +++++----- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/wiki/MCP-Scopes.md b/wiki/MCP-Scopes.md index b2cbb1016..d7c0d9fa4 100644 --- a/wiki/MCP-Scopes.md +++ b/wiki/MCP-Scopes.md @@ -1,6 +1,6 @@ # 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**. +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 your **Settings → Integrations → MCP**. ![OAuth consent screen](assets/OAuthConsentDCR.png) @@ -70,7 +70,7 @@ Grant only what you need. Some examples: | 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`. +The preset buttons in your **Settings → Integrations → MCP → OAuth 2.1 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`. ## Related diff --git a/wiki/MCP-Setup.md b/wiki/MCP-Setup.md index 1fe562939..28beeb95b 100644 --- a/wiki/MCP-Setup.md +++ b/wiki/MCP-Setup.md @@ -14,7 +14,7 @@ OAuth 2.1 is the preferred connection method. You grant specific scopes during t Claude.ai (web) supports native MCP connections — no JSON config file required: -1. In TREK, go to **Settings → Integrations → MCP → OAuth 2.1 Clients** and click **New Client**. +1. In TREK, go to your **Settings → Integrations → MCP → OAuth 2.1 Clients** and click **New Client**. 2. Select the **Claude.ai** preset. This fills in the redirect URI (`https://claude.ai/api/mcp/auth_callback`) and a default scope set. 3. Give the client a name, adjust scopes if needed, and save. Copy the client ID and client secret (`trekcs_` prefix) — the secret is shown only once. 4. In Claude.ai, open the MCP settings and add a new server using your TREK URL (`https:///mcp`). Claude.ai will open your browser to complete the OAuth consent flow. @@ -23,7 +23,7 @@ Claude.ai (web) supports native MCP connections — no JSON config file required Claude Desktop supports native MCP connections — no JSON config file required: -1. In TREK, go to **Settings → Integrations → MCP → OAuth 2.1 Clients** and click **New Client**. +1. In TREK, go to your **Settings → Integrations → MCP → OAuth 2.1 Clients** and click **New Client**. 2. Select the **Claude Desktop** preset. This fills in the redirect URI and a default scope set. 3. Give the client a name, adjust scopes if needed, and save. Copy the client ID and client secret — the secret is shown only once. 4. In Claude Desktop, open Settings → MCP and add a new server using your TREK URL (`https:///mcp`). Claude Desktop will open your browser to complete the OAuth consent flow. @@ -76,7 +76,7 @@ Create a client in TREK using the appropriate preset (Cursor, VS Code, Windsurf, ### Pre-created OAuth clients -**Settings → Integrations → MCP → OAuth 2.1 Clients** lets you create named OAuth clients before connecting. This gives you: +Your **Settings → Integrations → MCP → OAuth 2.1 Clients** page (your own settings, not the admin area) lets you create named OAuth clients before connecting. This gives you: - A fixed, named scope list defined up front - A client secret (`trekcs_` prefix, shown once) for confidential client mode @@ -94,7 +94,7 @@ Use this when your AI agent or automation script needs to authenticate silently ### Create a machine client -1. Go to (user) **Settings → Integrations → MCP → OAuth 2.1 Clients** and click **New Client**. +1. Go to your **Settings → Integrations → MCP → OAuth 2.1 Clients** and click **New Client**. 2. Tick **Machine client (no browser login)**. The redirect URI field disappears — machine clients don't need one. 3. Give it a name, select scopes, and click **Register Client**. 4. Copy the `client_id` and `client_secret` shown — the secret is displayed only once. @@ -115,7 +115,7 @@ Machine clients are designed for **AI agent frameworks and custom MCP client imp Static tokens grant full access to all tools and resources with no scope restrictions. A static-token session is warned about the deprecation once, not on every call: the notice rides along with the result of the first `list_trips` or `get_trip_summary` in that session — the trip-discovery tools an AI client normally reaches for first — for the client to surface to you. The tool's own payload still comes with it, and every later call in that session returns a plain result. The notice is also part of the session instructions the server sends when the connection initializes. -1. Go to **Settings → Integrations → MCP**, open the **API Tokens** sub-tab, and click **Create New Token**. +1. Go to your **Settings → Integrations → MCP**, open the **API Tokens** sub-tab, and click **Create New Token**. 2. Give the token a name and copy it immediately — it is shown only once. The token starts with `trek_`. 3. Pass the token as a header in your client config: