docs: complete the getting-started flow + workspace-driven routing - #166
Merged
Conversation
…ting The getting-started guide stopped at "connect your client" and several docs still described the removed Follow-Active / per-client-grant model. - getting-started: add the missing steps — connection approval, folder → Space/FeatureSet routing (Workspaces), and @mux Tool Optimization — so the guide covers the full journey end to end. - clients: replace the obsolete "connection modes" and per-client grants with the current model — one-click OAuth approval + workspace-driven routing (tools decided by the folder the app reports, not the app). - spaces / gateway / index: fix the remaining Follow-Active references; the active Space is now the fallback for unmapped folders. Add Workspaces and Tool Optimization to the index Key Concepts. Validated by building discover.ui against these docs (164 pages, all cross-links and screenshots resolve). Signed-off-by: Mohammod Al Amin Ashik <maa.ashik00@gmail.com>
Several guide pages were text-heavy with no visuals. Add a relevant app screenshot to each dry section: - security: the consent dialog in the OAuth Security section - gateway: the Settings page (gateway port, startup, updates) in Starting and Stopping - workspaces: the FeatureSet detail showing the toolset a folder resolves to - feature-sets: the effective-features view; also reframe the stale "assign per client" note to workspace-driven routing Validated by building discover.ui against the docs (164 pages, every image resolves from the live screenshots). Signed-off-by: Mohammod Al Amin Ashik <maa.ashik00@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The getting-started guide stopped at "connect your client" and several docs still described the removed Follow-Active / per-client-grant model. This brings the guide docs in line with how McpMux actually works today (workspace-root routing, dropped in migration 005's
client_pinremoval).getting-started — now end to end
Adds the missing post-connection steps so the journey is complete:
@muxTool Optimization: let the AI compose + pin a focused toolset from chat.clients — current model
Replaced "Connection Modes" (Follow Active / Locked / Ask on Change) and per-client FeatureSet grants with: one-click OAuth approval, workspace-driven routing (same folder → same tools, regardless of app), access keys, and managing/revoking apps.
spaces / gateway / index
Validation
Built discover.ui against these docs → 164 pages, every cross-link and screenshot resolves (screenshots are live from #25). No prose-only
tsc/lint gates, but the pre-commit hook (fmt/clippy/eslint/typecheck) passed.Renders on mcpmux.com/docs once merged (the site sources
docs/guide/via fetch-docs).