Add Pylon MCP server docs page#417
Closed
socialyadept wants to merge 2 commits into
Closed
Conversation
Documents both ways to govern Pylon: C1 registering Pylon's own hosted MCP server (per-user OAuth via dynamic client registration only), and C1's own MCP server translating the Pylon REST API (bearer token only). Follows the two-tab pattern used for other vendors with a native MCP option. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Align pylon.mdx's section structure with product/admin/mcp-server/notion.mdx's actual shipped convention (## headings inside each Tab) instead of bold pseudo-headings. Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Contributor
Author
|
Superseded by #427 — combining all the native-MCP-tab PRs into a single PR per request. |
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
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.
Summary
Pylon is a customer support / helpdesk platform with no existing MCP setup page. This adds a new page (like other vendors with a native MCP option) covering both ways C1 can govern Pylon access:
mcp.usepylon.com) as a downstream server. Authentication is per-user OAuth with dynamic client registration (DCR) only — Pylon's hosted server doesn't offer a bearer token or API key mode, so there's nothing to create in Pylon first. Listed as plain Pylon in the MCP server catalog.A comparison table above the tabs explains the difference up front (who hosts the server, authentication, access scoping, tool surface, setup effort), and the intro/recommendation prose is explicit about which catalog entry ("Pylon" vs "Pylon API") each option maps to, since the two names are easy to conflate.
Also adds the new page to site navigation in
docs.json, alphabetically between the PagerDuty and Ramp entries.Test plan
/product/admin/mcp-servers#...,/product/admin/enable-ai-access-management#...,/product/admin/audit-ai-tool-usage,/product/admin/tools-and-toolsets) exist onmainTabs/Tab/Steps/Step/Note) are balanceddocs.jsonremains valid JSON after the navigation insert🤖 Generated with Claude Code