Skip to content

Add Pylon MCP server docs page#417

Closed
socialyadept wants to merge 2 commits into
mainfrom
muhammad.kumail/pylon-mcp-page
Closed

Add Pylon MCP server docs page#417
socialyadept wants to merge 2 commits into
mainfrom
muhammad.kumail/pylon-mcp-page

Conversation

@socialyadept

Copy link
Copy Markdown
Contributor

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:

  • Pylon MCP (default tab) — C1 registers Pylon's own hosted MCP server (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.
  • Pylon API — C1's own MCP server that translates Pylon's REST API into tools, using a single bearer token (an API token generated in Pylon). Listed as Pylon API in the 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

  • Verified all external reference links (usepylon.com, docs.usepylon.com, support.usepylon.com) resolve live
  • Verified internal doc links/anchors (/product/admin/mcp-servers#..., /product/admin/enable-ai-access-management#..., /product/admin/audit-ai-tool-usage, /product/admin/tools-and-toolsets) exist on main
  • Checked MDX component tags (Tabs/Tab/Steps/Step/Note) are balanced
  • Validated docs.json remains valid JSON after the navigation insert

🤖 Generated with Claude Code

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>
@mintlify

mintlify Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
conductorone 🟢 Ready View Preview Jul 24, 2026, 10:03 PM

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>

Copy link
Copy Markdown
Contributor Author

Superseded by #427 — combining all the native-MCP-tab PRs into a single PR per request.

@socialyadept
socialyadept deleted the muhammad.kumail/pylon-mcp-page branch July 24, 2026 22:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant