Skip to content

Conversation

@strickvl
Copy link
Contributor

Summary

Updates the MCP documentation to reflect the new MCP Settings page added to both ZenML OSS and Pro dashboards (zenml-dashboard#969, zenml-cloud-ui#1060).

  • Added new "Using the Dashboard Settings Page" section with step-by-step guidance
  • Added comparison table showing differences between Pro (one-click PAT generation) and OSS (service account token paste) workflows
  • Added GIF demonstrating the settings page
  • Added cross-reference from llms-txt.md to the MCP Chat with Server guide

Test plan

  • Verify documentation renders correctly in GitBook
  • Confirm image/GIF displays properly
  • Check all links work correctly

@strickvl strickvl added documentation Improvements or additions to documentation internal To filter out internal PRs and issues x-squad Issues that are being handled by the x-squad labels Dec 17, 2025
@strickvl strickvl requested a review from htahir1 December 17, 2025 06:21
@github-actions
Copy link
Contributor

Documentation Link Check Results

Absolute links check failed
There are broken absolute links in the documentation. See workflow logs for details
Relative links check passed
Last checked: 2025-12-17 06:23:03 UTC

@strickvl strickvl added the no-release-notes Release notes will NOT be attached and used publicly for this PR. label Dec 17, 2025
@strickvl
Copy link
Contributor Author

strickvl commented Dec 17, 2025

Noting for visibility: I also updated the README over on the mcp-zenml repo to reflect some of these same docs changes: https://github.com/zenml-io/mcp-zenml#quick-setup-via-dashboard-recommended

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation internal To filter out internal PRs and issues no-release-notes Release notes will NOT be attached and used publicly for this PR. x-squad Issues that are being handled by the x-squad

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants