Wayfinder Guides

Overview

Wayfinder now supports the full path from AI-assisted generation to learner delivery and reporting. That includes role-based learning paths, standalone courses, exams, LMS assignments, SCORM, instructor-led training, presentation-based assessments, and MCP-driven collaboration.

What’s New

Getting Started

1. Go to Roles and choose whether you are creating a Role Learning Path or an Individual Course.
2. Provide the role or course prompt, source documentation, SME interview results when available, human instructions, and AI instructions.
3. If Adaptive Work Styles is enabled in your private context, use Use in AI Instructions on the Roles page to insert a support scaffold directly into the generation run.
4. Start generation and monitor the run in Role Workbench.
5. Watch the Quality Gates as Wayfinder runs path and outline QC automatically and repairs weak output when possible.
6. Open Course Studio to edit course structure, AI knowledge, media, and publish state.
7. Use LMS and Learn to verify the learner-facing experience.
8. When the role is ready for learners, assign generated-role memberships, provision context, and, if needed, configure tenant branding and Trusted Access for rollout.

This sequence is the same whether the work is performed directly in the UI or through an MCP-connected AI agent. If you leave the Workbench, return through the related item on the Roles page or reopen the saved Workbench URL for that role.

Generation Modes

Standalone courses publish into the shared Individual Courses container for the active company scope, so authors can find them in a predictable place after publication. Both generation modes now rely on automatic QC and targeted repair before human cleanup.

Course Studio Blocks

Course Studio is the primary authoring surface for native Wayfinder courses. The block editor now uses structured controls for common learning interactions instead of delimiter-heavy textareas.

Recommended editing pattern

1. Select a course in Course Studio.
2. Select a block so its controls open inside the slide canvas.
3. Use the structured controls for the block type instead of hand-writing JSON or delimiter syntax.
4. Let autosave capture edits after you leave the active field, or publish only after reviewing the learner view.

Exams

Wayfinder Exams is a role-level exam authoring workspace for editors and tenant admins. It is designed to build defensible certification-style exams from completed role paths, then move those exams through blueprint review, item-bank review, form assembly, publication, and export.

Recommended exam workflow

1. Create an exam from a completed role path.
2. Review the Blueprint and adjust purpose, audience level, total items, pass threshold, time limit, and competencies.
3. Approve the blueprint to generate the Item Bank.
4. Review flagged items, edit weak questions, delete duplicates, or regenerate specific items.
5. Approve the item bank and let Wayfinder build the Form Assembly.
6. Review the assembled form, approve it, then publish the exam.
7. Open LMS to verify the published exam preview and run exports.

LMS Operations

Wayfinder LMS now separates learner consumption from training operations. The Learning tab stays learner-focused, while Calendar and Operations support assignment, scheduling, and training management.

Training types supported in LMS

• Generated Path: published role-based path with learner registration and assigned-path workflows.
• Generated Course: published course from a path or the shared Individual Courses container.
• SCORM Course: uploaded ZIP package launched through the Wayfinder SCORM player with runtime tracking.
• Instructor-Led Course: reusable course record with one or more scheduled sessions.

Presentation-based activities

• Editors can add a presentation_submission block in Course Studio.
• Learners can upload or record a presentation in Learn.
• Instructors and coordinators grade the submission with the visible rubric from the Instructor page.

Course Coach

Course Coach adds a short reflective check after substantive modules so learners can explain what they understood, receive targeted correction when needed, and retry with a reframed question. Wayfinder keeps course content, source references, SME interview guidance, and tenant collective intelligence together as Coach context.

Recommended setup

1. Set tenant-wide defaults first, usually Recommended, Balanced, Encouraging, and a low retry limit while piloting.
2. Use SME interviews on manually created role paths so tacit workflow knowledge, common mistakes, and examples feed generation and Coach prompts.
3. Review generated courses in Course Studio and leave inheritance on unless one course needs a different policy.
4. Open the learner preview to confirm Coach appears only after meaningful modules.
5. Use Reports > Coach to review learner gap patterns, mark attempts useful or not useful, promote strong guidance into SME-reviewed Coach context, reset sessions, or regenerate weak Coach questions.

Privacy and collective intelligence

• Tenant-specific Coach attempts can improve tenant collective intelligence without crossing tenant boundaries.
• Privacy controls live in Accounts > Tenant Management > Coach Privacy.
• Admins can disable collection, retain only anonymized summaries, redact learner answer excerpts, apply retention rules, and export Coach insights.
• Learners see a Coach privacy notice in the Learn page and MCP/MCP-UI delivery surfaces.

SCORM/xAPI Package Editing

Wayfinder supports safe, non-destructive editing for uploaded SCORM and xAPI packages. Editors and admins can inspect detected text, media, and package structure inside Course Studio, save edits into a draft package revision, preview that revision, and publish it when ready.

Course Studio workflow

1. Open Course Studio and select the SCORM or xAPI package from the Packages list.
2. Click Inspect Package if the detected targets are not already loaded.
3. Select a text target and edit the textarea. Text edits autosave into a draft revision; if no draft exists, Wayfinder creates one automatically.
4. For media, select the media target, then drag a replacement file into the drop zone or use Choose File, then click Swap Media.
5. For structure, select a manifest or activity item, rename it, and optionally mark a SCORM item as the launch item.
6. Use Preview Draft to launch the edited draft package without affecting learners.
7. Click Publish Draft when the edited package should become the live learner launch version.

MCP package editing tools

• inspect_training_package: returns detected structure, text, and media targets.
• create_training_package_revision: creates a non-destructive draft package revision.
• update_training_package_text: updates one detected text target with revision-conflict protection.
• replace_training_package_media: swaps one detected media asset.
• update_training_package_structure: renames detected structure items or updates the SCORM launch item.
• get_training_package_revision: reads the draft revision, version token, and refreshed inventory.
• publish_training_package_revision: atomically publishes the edited package revision.

SCORM 1.2 launch compatibility

• SCORM 1.2 packages use the classic API runtime object and LMSInitialize, LMSGetValue, LMSSetValue, LMSCommit, and LMSFinish calls.
• Wayfinder’s player installs the SCORM 1.2 API into the launch frame so older packages can find the LMS runtime.
• If a SCORM 1.2 manifest points at a known placeholder launch file, Wayfinder can fall back to a real launchable HTML page and provide a navigation shell.
• For older packages that include loose content pages but no sequencing UI, Wayfinder builds a page outline from the manifest file list and loads each page through the same runtime frame.

Audiences

Wayfinder now separates functional role from audience. Roles determine what a user can do. Audience determines which learner-facing training they should see.

Where audience is configured

• Accounts: set user audience to Internal, Customer, or Partner.
• Course Studio: set one or more audiences for generated learning paths and individual courses.
• LMS Operations: set the audience and path targeting for custom training such as SCORM and instructor-led courses.

Context

Wayfinder Context gives each user a managed portfolio layer for role-specific memory, user-specific overlays, and agent-specific MCP behavior. It is designed so role assignments, AI knowledge, and external agents can all resolve against the same operating context.

Adaptive Work Styles

• Open Preferences > Context and enable Adaptive Work Styles if the user wants more structured agent support.
• Choose favorite support modes and default response or planning styles to shape future agent briefs.
• Use the built-in Quick Use Prompts to copy ready-made scaffolds without needing MCP tool names.
• Open Roles and use Use in AI Instructions to inject a support scaffold directly into role-path or individual-course generation.
• Use the quiet Helpful / Not Helpful buttons so Wayfinder can improve the modes in aggregate without storing diagnostic or manager-visible signals.
• When enabled, a smaller Adaptive Work Styles quick-help panel also appears in LMS for the signed-in learner.
• The same private quick-help prompts now appear inside the live course learner view so support is available while working through modules.
• Tenant and system admins can review aggregate-only mode feedback from Reports > Context.
• Tenant admins now see only their own tenant’s aggregate feedback in reports and exports, while system admins can review the platform-wide view.
• Admins can also export aggregate mode feedback and monthly trend data from Reports > Context.

What now resolves from membership

• LMS role visibility for generated roles
• AI Knowledge access for role-scoped generated knowledge
• Portfolio template provisioning into user portfolios
• Membership inspection views used by managers, editors, and admins in LMS

Recommended context workflow

1. Create a portfolio template for the generated role if the role needs shared company context.
2. Assign the generated role to a user through learning assignment or explicit generated-role membership.
3. Let Wayfinder provision the matching user portfolio automatically.
4. Upload any user-specific notes, preferences, or memory into the Personal Context Overlay.
5. Bind the user’s MCP token to the intended portfolio and agent profile so the correct context resolves automatically for that agent.

Notion Documentation

The Notion connector gives Wayfinder read-only access to a tenant documentation database. Synced pages become selectable source material for role and course generation, and can also appear as Course Coach reference material when learners need targeted review.

Database URL vs database name

• Paste the full Notion database link or the 32-character database ID.
• Do not paste the workspace name or plain database title. A plain name cannot be resolved by the Notion API.
• If Wayfinder says Notion could not find the database, confirm the database was shared with the integration and that the value is a database URL or ID.

Audience handling

• The connector has a default audience setting: Internal, Partner, or Customer.
• Use separate Notion databases, pages, or connector sync passes when documentation differs by audience.
• When generating paths or courses, Wayfinder uses the lowest-common audience level selected for the training so customer-facing work does not accidentally draw from internal-only documentation.
• The current Notion connector is documentation-only. It is intended for source selection, generation context, and Coach references, not for writing back to Notion.

Editor workflow

1. Tenant Admin saves the Notion connector and clicks Sync Now.
2. Confirm synced documents appear in the Integrations card modal and the Documentation Library pickers.
3. Editors open Roles creation and select relevant synced documents from the Documentation Library.
4. Wayfinder includes those selected documents in the role/course prompt and source snapshots.
5. Course Coach can use those source references later when suggesting review content.

Troubleshooting

• 404 database not found: the database was not shared with the integration, or the saved value is a name instead of a URL/ID.
• 0 documents synced: confirm the integration has access to the actual database page, not only a parent workspace page, and confirm the database contains pages.
• Only one document synced: check whether the database mostly contains child pages under one parent page, or whether only one database row is visible to the integration.
• Documents appear in Notion but not in generation: confirm the training audience selection matches the documentation audience you synced.

Confluence Documentation

The Confluence connector gives Wayfinder read-only access to selected Confluence Cloud pages. Synced pages join the tenant Documentation Library and can be selected for generation prompts or used later as Course Coach references.

Setup location

• Open Accounts > Tenant Management > Integrations.
• Select the Confluence integration card to open the setup modal.
• After saving the connector, use Sync Now from that same modal to populate the Documentation Library.

API details

• External API: Wayfinder calls the Confluence Cloud REST API under /wiki/rest/api.
• Search endpoint: Wayfinder uses GET /wiki/rest/api/content/search with CQL, limit, start, and expand=body.storage,version,space.
• Authentication: Confluence Cloud uses Basic Auth with the Atlassian account email and an Atlassian account API token. Organization Admin API keys are not accepted for page content sync.
• Wayfinder save endpoint: POST /api/documentation-connectors/confluence.
• Wayfinder sync endpoint: POST /api/documentation-connectors/confluence/sync.
• Wayfinder library endpoint: synced records are listed through GET /api/documentation-documents and then appear in Role generation and Role Workbench Documentation Library pickers.

Space key vs CQL

• For a simple setup, provide a space key such as KB. Wayfinder searches type=page AND space="KB".
• For narrower control, provide a CQL query such as space = KB AND type = page AND label = customer-facing.
• If CQL is provided, it takes precedence over the space-key-only query.
• Keep the first sync small and audience-safe, then expand after confirming the results.

Audience handling

• The connector has a default audience setting: Internal, Partner, or Customer.
• Use separate spaces, labels, or CQL filters when internal, partner, and customer documentation should differ.
• When Editors attach documentation to a path or course, Wayfinder uses the selected training audience to keep references audience-aware.
• The Confluence connector is documentation-only. It does not create, edit, or publish Confluence pages.

Troubleshooting

• 401 or 403: check the email/API token pair and confirm the integration user can view the selected space/pages.
• Expecting value / non-JSON response: confirm the URL is the Confluence site URL, such as https://example.atlassian.net/wiki, and that the token is an Atlassian account API token rather than an Organization Admin API key.
• 0 documents synced: confirm the space key or CQL returns pages for that user in Confluence.
• Wrong pages synced: narrow the connector with a CQL query, usually by space, type, label, ancestor, or title.
• Documents appear in Confluence but not generation: confirm the synced audience and selected training audience line up.

ServiceNow Documentation

The ServiceNow connector gives Wayfinder read-only access to selected Knowledge Base articles. Synced articles join the tenant Documentation Library and can be selected for generation prompts or used later as Course Coach references.

Setup location

• Open Accounts > Tenant Management > Integrations.
• Select the ServiceNow integration card to open the setup modal.
• After saving the connector, use Sync Now from that same modal to populate the Documentation Library.

API details

• External API: Wayfinder calls the ServiceNow Table API.
• Knowledge endpoint: Wayfinder reads GET /api/now/table/kb_knowledge.
• Query parameters: Wayfinder sends sysparm_query, sysparm_limit, sysparm_display_value=true, sysparm_exclude_reference_link=true, and selected sysparm_fields.
• Authentication: use a ServiceNow integration user credential that can read Knowledge articles through the Table API.
• Wayfinder save endpoint: POST /api/documentation-connectors/servicenow.
• Wayfinder sync endpoint: POST /api/documentation-connectors/servicenow/sync.
• Wayfinder library endpoint: synced records are listed through GET /api/documentation-documents and then appear in Role generation and Role Workbench Documentation Library pickers.

Encoded query guidance

• If the query field is blank, Wayfinder uses workflow_state=published^active=true.
• Use ServiceNow encoded queries to filter by knowledge base, category, workflow state, label, or audience-safe article set.
• Keep internal, customer, and partner content separated with distinct queries or dedicated knowledge bases.

Troubleshooting

• 401 or 403: check the username/password pair and confirm the user can read kb_knowledge through the Table API.
• Non-JSON response: confirm the instance URL is the ServiceNow instance URL, such as https://example.service-now.com, and that API access is not redirecting to an interactive login flow.
• 0 documents synced: test the encoded query in ServiceNow and confirm it returns published Knowledge articles for that user.
• Wrong articles synced: narrow the connector with an encoded query by knowledge base, category, or publication status.

Support Operations

Wayfinder support intake is now a persistent support workflow instead of a trial-only inbox. Requests are triaged, tracked, and written back with visible resolution notes.

• /feedback now captures a short subject, what happened, expected behavior, and reproducible steps.
• Each submission stores AI-assisted triage fields such as priority, triage summary, suspected area, and recommended owner.
• System Admins can review and resolve requests from Reports > Support.
• Tenant Admins can review all support requests created by accounts in their tenant, including customer-visible resolution notes.
• Reports > Support now supports filtering by status, priority, category, and search text, plus CSV export for the current filtered view.
• Tenant admins can add visible follow-up notes without overwriting the latest resolution note, while system admins can keep separate internal notes.
• MCP now includes support-request tools so a System Admin agent can list, triage, annotate, and resolve support issues.

Tenant Rollout

Wayfinder now supports a fuller tenant rollout motion: provision the learning model, bind role memberships, set up context, brand the tenant workspace, and optionally launch learners in from the tenant’s own site.

Tenant Branding

Tenant branding is a premium white-label layer for Captain and Fleet tenants. It is managed from Accounts > Tenant Management and uses a safe draft, preview, and publish workflow.

Developer reference

• Supported token keys: bg, bg_accent, panel, text, text_strong, muted, primary, primary_strong, accent, ok, warn, err, line_soft
• Allowed asset URLs: https://..., http://..., or managed /files/... URLs
• If you import hosted fonts, set the matching font family name in the tenant branding form so the shell can reference it directly.
• Custom CSS should extend the shell contract instead of replacing page structure wholesale
• Save Draft does not affect learners. Publish makes the theme live for tenant views.

Trusted Access

Trusted Access is Wayfinder’s lightweight, one-click tenant launch flow. It is intended for tenant websites that already authenticate users and want to hand learners directly into Wayfinder LMS without implementing full OAuth or SSO.

Claims

Instant Auth accepts either the full Trusted Access claim set or a simpler portal-friendly JWT. Use sub for the learner email when you do not want to send both email and external_user_id; use dest_path as a friendly alias for return_to.

• iss
• aud
• tenant_id
• sub or both external_user_id and email
• name
• audience_type and role, or allow Wayfinder defaults to fill them
• dest_path or return_to when the launch should open somewhere other than the default path
• jti
• iat, nbf, exp

ServiceNow header pattern

<a class="btn btn-link" href="/api/x_wayfinder/instant_auth_redirect">Wayfinder Training</a>

The ServiceNow endpoint should run server-side, call Wayfinder Instant Auth, and redirect to the returned absoluteLoginUrl. Do not build tickets inside the Employee Center Header widget.

Shared-secret Instant Auth example (Node.js)

import jwt from 'jsonwebtoken';

const rawJwt = {
  iss: 'tenant.example.com',
  aud: 'wayfinder-trusted-access',
  tenant_id: 'acme',
  sub: 'learner@example.com',
  name: 'Sample Learner',
  external_user_id: 'employee-123',
  audience_type: 'internal',
  role: 'Learner',
  dest_path: '/lms',
  jti: crypto.randomUUID(),
  iat: Math.floor(Date.now() / 1000),
  nbf: Math.floor(Date.now() / 1000),
  exp: Math.floor(Date.now() / 1000) + 120,
};

const res = await fetch('https://wayfinder.example.com/api/trusted-access/instant-auth-request', {
  method: 'POST',
  headers: {'Content-Type': 'application/json'},
  body: JSON.stringify({tenant_id: 'acme', jwt: jwt.sign(rawJwt, process.env.WAYFINDER_SHARED_SECRET, {algorithm: 'HS512'})})
});
const {absoluteLoginUrl} = await res.json();
// Redirect the learner to absoluteLoginUrl.

Tenant Management also includes a copy-ready Python signing example for teams that prefer Python backends.

Security notes

• Never expose the signing secret in browser JavaScript.
• Instant Auth JWTs and generated login URLs should be short-lived and one-time use.
• Match the JWT algorithm to the tenant signing mode: use HS256, HS384, or HS512 for Shared Secret mode; use RS256, ES256, or EdDSA for JWT Public Key mode.
• Use the Tenant Management validator to test tickets without signing a user in.
• Trusted Access now requires configured allowed_origins; browser launch and curl testing must come from a listed origin.
• ServiceNow outbound REST must trust the Wayfinder TLS certificate chain. If ServiceNow returns Session contains no certificates - Untrusted, import the full certificate chain or fix the public certificate chain before debugging JWT claims.
• SystemAdmin is intentionally blocked from trusted ticket role mapping.

Review and Approval

1. Learning Path Quality Gate: for role-based runs, Wayfinder now scores the generated path, repairs weak output, and usually auto-continues without a manual pause.
2. Course Outline Quality Gate: Wayfinder applies the same automatic QC and repair loop to outlines before content generation continues.
3. Course Collaboration Review: when collaborators edit fields or sections, review pending changes before publication.
4. Publication Review: confirm the learner-facing course content in Studio or LMS before considering the course finished. Course publishing is still the main human quality checkpoint for learning content.
5. Instructor / Coordinator Review: for presentation activities and instructor-led completion, learners do not self-grade or self-complete. The grading or completion step belongs to the reviewer role.
6. Exam Review: for exams, approve the blueprint first, then the item bank, then the assembled form before publication becomes available.

Where to Edit

• Roles: start new generation runs and choose role path vs individual course.
• Role Workbench: monitor generation progress, inspect workflow state, and restart generation runs. Reopen it from the related role item on the Roles page or by returning to the saved Workbench URL for that role.
• Course Studio: manually create learning paths, reorder or move courses with drag and drop, mirror courses into multiple roles, set path/course audience visibility, edit course metadata, build structured interaction blocks, upload media, manage AI knowledge, and control publication state.
• Instructor Dashboard: review learner presentation submissions and apply rubric-based grading.
• LMS Operations: manage SCORM uploads, instructor-led courses, scheduling, custom training metadata, and header images.
• Preferences > Context: manage portfolio templates, user portfolios, personal context overlays, agent profiles, and re-import behavior.
• Exams: review blueprint settings, source evidence, item-bank quality, item detail, form assembly, publication state, and exam export readiness.
• Accounts / Tenant Management: approve pending tenant users, manage branding, configure Trusted Access, and share tenant entry links.
• Reports > Support: review support-request status and visible resolution notes for the tenant.

Course Studio is the primary authoring workspace once a course exists. It is the right place for content cleanup, structured block editing, media updates, audience visibility, and publication checks.

Where to View

• Course Studio: author/admin view of the source course record.
• LMS: learner catalog, assignment summary, SCORM launch surface, instructor-led schedule visibility, and published exam preview.
• Learn: actual module-delivery experience with tabs, accordions, scenarios, quizzes, and progress.
• Instructor: staff-facing grading surface for presentation submissions.
• LMS Published Exams: preview and export surface for published exams tied to a selected role.
• Reports: usage, traffic, support, enablement, custom-training analytics, and context-capacity surfaces.
• Preferences > Context: source-of-truth view for portfolio files, personal overlays, generated-role memberships, and rendered agent briefs.
• Accounts > Trusted Access Setup: launch endpoint, validation, audit export, and integration snippets for tenant website launch.

If a standalone course was created through MCP, check the final visible location in the shared Individual Courses path after publication.

MCP Collaboration

Wayfinder MCP lets AI agents work as structured collaborators instead of browser drivers. Agents can inspect workflow state, review drafts, update content, and support staged approvals while humans keep publication authority.

What MCP collaboration enables

• Create new role learning paths or standalone individual courses
• Poll generation status and identify approval checkpoints
• Edit learning paths, course outlines, courses, and AI knowledge packs
• Create, review, edit, regenerate, approve, publish, and export exams through MCP
• Retrieve reporting data and manager enablement summaries for analysis or operational follow-up
• Create and manage instructor-led training records and other custom training operations
• Filter training and custom-training reporting by internal, customer, or partner audience when teams need segmented visibility
• Create draft revisions before editing published courses so MCP never mutates the live learner version directly
• Resolve agent context through portfolios, personal overlays, and MCP-bound agent profiles
• Review pending field and section changes before approving them
• Use specialized agents from Engineering, HR, Product, Marketing, and Customer Success to improve content from their domain perspective

Recommended collaboration pattern

1. A human defines the role or course prompt and source material.
2. An AI agent drafts or revises content through MCP tools.
3. Domain agents contribute targeted review comments or edits.
4. A human reviews the changes, approves staged output, and decides what gets published.

Exam collaboration pattern

1. Use list_examable_roles and create_exam to start from a completed role path.
2. Have Engineering or other domain agents refine the blueprint and review flagged items through get_exam, update_exam_blueprint, update_exam_item, and regenerate_exam_item.
3. Use approve_exam_blueprint, approve_exam_item_bank, and approve_exam_form to move the exam forward once the quality bar is met.
4. Publish with publish_exam and hand off export testing through export_exam.

Agent AI Authoring

Agent AI authoring is the MCP-first workflow for customers who want their own connected AI assistant to write or revise learning paths, courses, and LMS-visible draft content. The built-in Wayfinder generation flow still exists, but Agent AI mode gives customers a cleaner “my agent is writing this” path with LMS as the live review surface.

Recommended Agent AI sequence

1. Create the workflow through MCP with create_learning_path(authoring_mode="agent_ai").
2. Use MCP to set or refine the learning path and course outlines.
3. Approve Learning Path and Course Outlines through MCP or LMS review actions.
4. Create or revise courses with create_course, update_course, and the block-level editing tools.
5. Upload assets with upload_media_asset, attach them with set_course_header_image, add_course_block, or update_course_block, and import SCORM with import_scorm_training.
6. Use LMS to follow draft changes, scoped notes, approvals, and publish readiness.
7. Publish only after the human reviewer is satisfied with the draft.

MCP-UI Learner Runtime

MCP-UI lets a compatible assistant, such as Hermes or another MCP client with embedded-resource support, launch a Wayfinder course as a lightweight learner player while Wayfinder remains the system of record for enrollment, content, media, and completion.

Recommended assistant sequence

1. Call list_registered_learning_paths to find the learner’s registered paths, courses, and current progress.
2. When the learner chooses a generated course, call launch_training_ui(role_id=..., course_id=...).
3. When the learner chooses an assigned SCORM package, call launch_training_ui(training_id=...). Wayfinder launches the SCORM package through its hosted player and records SCORM runtime, completion, score, lesson location, and suspend data.
4. When the learner asks how to complete a specific task and a registered course scope is known, call launch_relevant_training_ui(role_id=..., course_id=..., query=...) to open only the matching module content.
5. For task help inside an assigned SCORM package, call launch_relevant_training_ui(training_id=..., query=...). The assistant receives the SCORM player plus package/page fallback context.
6. If a SCORM package needs chat-native delivery or editing, an Editor or Tenant Admin can call convert_scorm_to_native_course(training_id=...). Use the returned role_id and course_id as a native course.
7. If the host assistant renders MCP-UI resources, present the embedded course player directly.
8. If MCP-UI rendering is not available, call get_course and deliver the returned plain text plus course_body.sections one section at a time. The learner should not need to run code, import JSON, or parse tool output manually.
9. For SCORM fallback, use the returned package title, description, detected page list, launch URL, and runtime status. Do not claim SCORM completion unless Wayfinder reports it.
10. Render or link image, audio, video, PDF, and external media from course_body.media_assets, section media, and search result media. Use transcript, caption, summary, or description text as media context when provided.
11. Only call progress tools after the learner completes the required instruction, activity, quiz, reflection, or evidence for that section.
12. After a completion write, call list_registered_learning_paths again when the learner needs confirmation or a resume point.

Connection Guides

Use these setup patterns to connect Codex, OpenClaw, Claude Code, or other MCP clients to Wayfinder through the hosted MCP gateway.

https://wayfinder.robbclan.com/mcp

Useful MCP Tools

Role and Course Tools

• create_learning_path
• get_role_status
• update_learning_path
• approve_learning_path
• update_course_outlines
• approve_course_outlines
• create_course
• import_external_course_as_native
• delete_course
• create_course_draft_revision
• publish_course
• get_course
• update_course
• set_course_header_image
• add_course_block
• update_course_block
• delete_course_block
• reorder_course_blocks
• get_course_pending_reviews
• approve_course_section_review
• approve_course_field_review
• update_ai_knowledge
• restart_generation
• export_course

Learner Runtime Tools

• recommend_learning_for_goal
• search_learning_content
• get_recommended_next_step
• list_registered_learning_paths
• launch_training_ui
• launch_relevant_training_ui
• get_course
• record_course_section_progress
• mark_course_complete

Career and skill recommendation pattern

• When a learner asks for career advancement, job mobility, skill growth, promotion readiness, or help moving into another role, call recommend_learning_for_goal(...) before answering from general model knowledge.
• Use goal, current_role, target_role, skills, and time_horizon when the learner provides them. It is fine to pass only goal when the learner is vague.
• Use search_learning_content(query=...) when the assistant needs a small course excerpt, section title, or snippet to support the answer.
• Search results can include generated course snippets and SCORM package/page snippets. For SCORM results, use the returned training_id with launch_training_ui(training_id=...).
• Use the plain text returned by search_learning_content directly. Do not tell the learner to run code, import JSON data, or load a local file to read the result.
• Use launch_relevant_training_ui(role_id=..., course_id=..., query=...) when the learner is registered for a course and asks how to complete a task that should be taught from a specific module.
• Use get_recommended_next_step(goal=...) when the learner asks what to do next or how to start.
• Present results as recommendations, not assignments, unless they also appear in list_registered_learning_paths().
• Include the returned Wayfinder URL so the learner can open the path, course, live class, or snippet source.

Recommended learner runtime pattern

• Use list_registered_learning_paths() before launch so the assistant only offers registered work as assigned training.
• Use launch_training_ui(role_id=..., course_id=...) for MCP-UI capable hosts.
• Use launch_relevant_training_ui(role_id=..., course_id=..., query=...) when the learner asks for task help and the assistant should render just the most relevant module or modules.
• Use launch_training_ui(training_id=...) for assigned SCORM packages. Use launch_relevant_training_ui(training_id=..., query=...) when the learner asks a task-specific question about a SCORM package.
• Use get_course(role_id=..., course_id=...) as the fallback for assistants that cannot render embedded resources.
• Use record_course_section_progress(...) only after required evidence is complete.
• Use mark_course_complete(...) after all required sections and assessments are complete.

Asset + LMS Authoring Tools

• upload_media_asset
• import_scorm_training
• import_xapi_training
• convert_scorm_to_native_course
• inspect_training_package
• create_training_package_revision
• update_training_package_text
• replace_training_package_media
• update_training_package_structure
• get_training_package_revision
• publish_training_package_revision

External interactive compatibility

• Wayfinder Native: use import_external_course_as_native when the connected agent can emit structured sections and supported block types.
• SCORM Package: use import_scorm_training when the external tool already exports a launchable SCORM zip.
• SCORM-to-Native Conversion: use convert_scorm_to_native_course when a SCORM package should become an editable Wayfinder-native course for MCP/chat delivery. Completion is tracked as Wayfinder-native SCORM-equivalent completion, not as an original SCORM runtime event.
• Sandboxed Interactive Embed: use an interactive_embed block for hosted simulations or interactive mini-apps instead of pasting raw HTML or JavaScript into text blocks.

Exam Tools

• list_examable_roles
• list_exams
• create_exam
• get_exam
• start_exam_generation
• update_exam_blueprint
• update_exam_item
• regenerate_exam_item
• delete_exam_item
• regenerate_exam_item_bank
• assemble_exam_form
• approve_exam_blueprint
• approve_exam_item_bank
• approve_exam_form
• publish_exam
• archive_exam
• export_exam

Reporting + LMS Operations Tools

• list_training_catalog
• create_live_class
• update_training
• archive_training
• assign_training
• get_manager_enablement
• get_custom_training_report
• record_training_completion

Context + Memory Tools

• get_context_snapshot
• list_context_portfolios
• list_context_agent_profiles
• get_agent_onboarding_self_test
• render_agent_brief
• get_context_profile_status
• draft_personal_context_refresh
• list_adaptive_work_style_modes
• get_adaptive_work_style_mode_prompt

Recommended context MCP patterns

• Use list_context_portfolios() first when an agent can operate in more than one portfolio.
• Use list_context_agent_profiles(portfolio_id=...) to discover which agent profiles exist under the selected portfolio.
• Use get_context_snapshot(topic="current_identity") or get_context_snapshot(topic="documents") when you only need one slice instead of the whole context payload.
• For legacy onboarding prompts, use get_agent_onboarding_self_test() followed by render_agent_brief().
• Use get_context_profile_status() at the start of longer collaborations to detect missing, thin, or stale context before the agent makes avoidable assumptions.
• For personal profile upkeep, recommend refreshes when the profile is stale or incomplete, then use draft_personal_context_refresh(...) to prepare a reviewable draft instead of overwriting the published profile.
• Personal context should be treated as a maintained asset. Internal agents may recommend regular refreshes, but publication stays user-controlled.
• Use list_adaptive_work_style_modes() to discover the user’s available support modes and current favorites.
• Use get_adaptive_work_style_mode_prompt(mode_id=...) when you want a ready-to-use scaffold for modes like start_task, clarify_request, or recover_from_overload.

Recommended audience-aware MCP patterns

• list_training_catalog(audience_scope=...) to inspect only internal, customer, or partner training.
• create_live_class(audience_scope=..., path_assignment_mode=..., linked_role_ids=[...]) to target custom training correctly from the start.
• update_training(...) to change audience or learning-path targeting later.
• get_custom_training_report(audience_scope=...) to pull customer-only or partner-only custom-training reporting through MCP.

Recommended Agent AI authoring patterns

• Use create_learning_path(authoring_mode="agent_ai", ...) when the connected assistant should own the writing workflow.
• For media-first edits, call upload_media_asset(...) first, then attach the returned URL with set_course_header_image(...) or a block-edit tool.
• Prefer block-level tools like add_course_block(...) and reorder_course_blocks(...) for precise LMS-safe edits instead of replacing the whole course payload.
• Use create_course_draft_revision(...) before editing published courses so the live learner version stays untouched.
• If an MCP write targets a published course, Wayfinder returns an error telling the agent to create and edit a draft revision instead.
• Use import_scorm_training(...) when the agent needs to add a packaged LMS asset instead of a generated course block.

The exam MCP tool set is designed for collaborative authorship. It works well when domain specialists need to review technical accuracy or distractor quality through an AI agent without spending time in the full UI.

Troubleshooting

Downloads

These downloads are intended for teams connecting external MCP-capable AI agents into Wayfinder. They should stay aligned with the current server-side generation and publishing workflow.