Rename upstream MCP registrations to MCP sources

[c1-squire-dev]

Summary

• use MCP source and MCP sources consistently in customer-facing navigation, labels, and first conceptual references
• avoid ambiguous standalone Source or Sources labels, including the documentation path Integrations > MCP sources and product path AI > MCP Sources
• distinguish Catalog MCP sources from External MCP sources across setup, authentication, discovery, governance, and private bridge guidance
• retain MCP server where it describes an actual protocol server or endpoint, and preserve existing URLs and literal configuration identifiers

Validation

• checked 545 internal links and heading anchors across all changed pages; the one subsequently clarified heading and its self-link were updated together
• validated docs.json and scripts/nav-paths.json with jq
• final diff audit found no standalone capitalized Source/Sources labels or duplicated MCP MCP wording
• ran git diff --check

[mintlify]

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

Project	Status	Preview	Updated
conductorone	🟢 Ready	View Preview	Sep 11, 2026, 10:57 PM

[mindymo]

House style in both the docs and the UI is sentence casing titles and labels, so we need this to be "MCP sources" not "MCP Sources" in both places.